You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We cannot store the message with an Observation into database since that one is not Serializable and it cannot be.
We have to revise the logic of the propagation to something like MessageSenderContext and MessageReceiverContext on respective sides of the MessageChannel implementation.
The sender part is already supported as is when we enable an Observation on the channel.
The receiver side is missed so far.
We definitely have to start a new observation on the receiver side since it can be not only in a different thread, but fully different application instance.
And sender observation will be closed any way when that thread finishes its work after storing message into DB.
The text was updated successfully, but these errors were encountered:
Fixes: #9001
The `ObservationPropagationChannelInterceptor` does not propagate an observation properly.
And it fully cannot when the message channel is persistent.
* Deprecate `ObservationPropagationChannelInterceptor` in favor of enabled observation on the channel
and target `MessageHandler` which is a consumer of this channel.
* Remove tests with an `ObservationPropagationChannelInterceptor`
* Mention a correct behavior in the `metrics.adoc` and `ObservationPropagationChannelInterceptor` Javadocs
Fixes: #9001
The `ObservationPropagationChannelInterceptor` does not propagate an observation properly.
And it fully cannot when the message channel is persistent.
* Deprecate `ObservationPropagationChannelInterceptor` in favor of enabled observation on the channel
and target `MessageHandler` which is a consumer of this channel.
* Remove tests with an `ObservationPropagationChannelInterceptor`
* Mention a correct behavior in the `metrics.adoc` and `ObservationPropagationChannelInterceptor` Javadocs
See more info in: micrometer-metrics/tracing#612.
We cannot store the message with an
Observation
into database since that one is notSerializable
and it cannot be.We have to revise the logic of the propagation to something like
MessageSenderContext
andMessageReceiverContext
on respective sides of theMessageChannel
implementation.The sender part is already supported as is when we enable an
Observation
on the channel.The receiver side is missed so far.
We definitely have to start a new observation on the receiver side since it can be not only in a different thread, but fully different application instance.
And sender observation will be closed any way when that thread finishes its work after storing message into DB.
The text was updated successfully, but these errors were encountered: