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
Is your feature request related to a problem? Please describe.
Create span during subscription to enable performance monitoring of the processing.
Describe the solution you'd like
In getHandleSubscribePatch start a span when the patched handleSubscribe is invoked and end it when done callback (from handleSubscribe arguments) is called.
Questions pending ?
Should only one span be started for all subscriptions topic ?
Beyond the client connection details, what should be added in the span attributes ?
Should only one span be started for all subscriptions topic ?
Could you explain this? You mean that if a sub contains multiple topics? In that case I would focusing on the time needed to process an entire sub packet independently from the topics
Beyond the client connection details, what should be added in the span attributes ?
Subscription qos too, consider also that 128 is considered an error (failed sub)
Is your feature request related to a problem? Please describe.
Create span during subscription to enable performance monitoring of the processing.
Describe the solution you'd like
In
getHandleSubscribePatch
start a span when the patchedhandleSubscribe
is invoked and end it whendone
callback (fromhandleSubscribe
arguments) is called.Questions pending ?
process
as specified in OpenTelemetry semantic conventions.The text was updated successfully, but these errors were encountered: