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
Copy file name to clipboardExpand all lines: README.md
+71Lines changed: 71 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -519,6 +519,77 @@ await QueueManager.init({
519
519
})
520
520
```
521
521
522
+
## OpenTelemetry Instrumentation (experimental)
523
+
524
+
> [!WARNING]
525
+
> The OpenTelemetry instrumentation is experimental and its API may change in future releases.
526
+
527
+
`@boringnode/queue` ships with built-in OpenTelemetry instrumentation that creates **PRODUCER** spans for job dispatch and **CONSUMER** spans for job execution, following [OTel messaging semantic conventions](https://opentelemetry.io/docs/specs/semconv/messaging/messaging-spans/).
The instrumentation patches `QueueManager.init()` to automatically inject its wrappers — no config changes needed in your queue setup.
545
+
546
+
### Span Attributes
547
+
548
+
The instrumentation uses standard [OTel messaging semantic conventions](https://opentelemetry.io/docs/specs/semconv/messaging/messaging-spans/) where they map cleanly, plus a few queue-specific custom attributes.
0 commit comments