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.
Tracing visualization tools need to know when they are dealing with async messaging scenarios.
Describe the solution you'd like
EventHub spans kinds were not correct in the previous guidance. They should be changed to
Message: 'producer' kind for OpenTelemtery (was 'internal'). OpenCensus does not support 'producer' - 'internal' should still be used there
Send: 'client' kind (was 'producer')
Processing: 'consumer' kind (was 'server'), OpenCensus should continue using 'server'
Note: As discussed offline, opencensus support may be dropped at this point.
This complies with OpenTelemetry semantics and helps backend tools understand they are dealing with async message processing and visualize it accordingly.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
Description Added
Expected solution specified
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Tracing visualization tools need to know when they are dealing with async messaging scenarios.
Describe the solution you'd like
EventHub spans kinds were not correct in the previous guidance. They should be changed to
Note: As discussed offline, opencensus support may be dropped at this point.
This complies with OpenTelemetry semantics and helps backend tools understand they are dealing with async message processing and visualize it accordingly.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
The text was updated successfully, but these errors were encountered: