Artem Bilan

I see in your logs: ``` "thread_name":"noBeanNameSet-C-1" ``` That means that this `KafkaMessageListenerContainer` is created manually and not managed by Spring `ApplicationContext`. Is that expected in your logic? Usually we...

Sure thing, @chickenchickenlove ! It is hard to judge what is going on since no one has shared reproducible sample so far. But I’ll be happy to look into your...

Sounds good , @chickenchickenlove ! Closing in favor of that one in Apache Kafka. Thank you for you great contributions!

According to the `#xpath()` SpEL function we don't need anything else: ``` ```

That's correct, @mhalbritter . The feature was introduced and I tried to incorporate it into Spring Boot. But in the end we decided with @philwebb to revert it in favor...

Thank you for the request! If you have anything in mind how that supposed to be implemented on the `RetryTemplate`, I'll be happy to review. Although from our experience an...

Looks like this project has some idea how to implement it: https://github.com/findinpath/spring-retry-metrics. I still think that this can be implemented as an injectable `RetryListener`. The auto-configuration for this feature is...

I wonder if `@Timed` feature from Micrometer does that trick already alongside with the `@Retryable`: https://docs.micrometer.io/micrometer/reference/concepts/timers.html#_the_timed_annotation. However I agree that it won't collect the number of attempts...

I thought about an Observation API, but that then rejected that idea. There is no reason to include such an internal (retry) logic of the service into a trace. There...

So, I decided to implement something myself: https://github.com/spring-projects/spring-retry/pull/459. I'm not totally sure that it supposed to be like that in the `Timer` part, but at least we have something to...