@appsignal/opentelemetry-instrumentation-bullmq
0.9.0 · 24 Aug 2026Apache-2.0125.3k / weekRepositoryHomepagenpmAtom feed
Upgrading @appsignal/opentelemetry-instrumentation-bullmq From 0.7.1 to 0.9.0
4 releases in betweenevery note read
Release by release
0.8.0 – 0.9.02 releases, nothing new or fixed in the notes
- New
Add a
useProducerSpanAsConsumerParentconfiguration option that defaults tofalse. When set totrue, instead of establishing a span link from the consumer span to the producer span, the consumer span will be in the same trace, as a child span of the producer span. (patch 5d7ee27)
- New
5 other lines we could not sort, mostly version bumps
- 0.9.0
Declare
@opentelemetry/apias a peer dependency instead of a regular dependency, so that npm installs one copy of it, shared with your application. - 0.9.0
Update the bundled
@opentelemetry/instrumentationand@opentelemetry/semantic-conventionspackages to their current versions. The span attributes this instrumentation emits are unchanged. - 0.8.0
Update OpenTelemetry dependencies to v2. (minor b85d788)
- 0.8.0
Replace the
messaging.bullmq.job.parentOpts.waitChildrenKeyspan attribute withmessaging.bullmq.job.parentOpts.addToWaitingChildren. The old attribute reported an internal Redis key string (bull:<queue>:waiting-children) that bullmq exposed up to version 5.61.2. From 5.62.0, bullmq replaced it with anaddToWaitingChildrenboolean flag. The new attribute normalises both representations into a single boolean:truewhen a flow parent job is waiting for its children to complete. (minor af9eadb) - 0.8.0
Update messaging semantic convention attributes to latest OpenTelemetry Semantic Conventions for Messaging Spans spec.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.