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.
N/A
Describe the solution you'd like
Use OpenTelemetry's semantic conventions for messaging. This ensures consistency with other messaging systems, and (more importantly) enables UI/UX features in tooling such as Datadog (as captured below).
I think the important here is that bullmq-otel adheres to Otel conventions, but having a generic naming of attributes that is not tied specifically to Otel in BullMQ as we want our telemetry interface to be generic and not hard tied to Otel.
Is your feature request related to a problem? Please describe.
N/A
Describe the solution you'd like
Use OpenTelemetry's semantic conventions for messaging. This ensures consistency with other messaging systems, and (more importantly) enables UI/UX features in tooling such as Datadog (as captured below).
Describe alternatives you've considered
I am sticking with https://github.com/appsignal/opentelemetry-instrumentation-bullmq for now since using bullmq-otel would require me to update queries and charts. That library follows semantic conventions: https://github.com/appsignal/opentelemetry-instrumentation-bullmq/blob/main/src/attributes.ts.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: