Packages

@appsignal/opentelemetry-instrumentation-bullmq

0.9.0 · 24 Aug 2026Apache-2.0125.3k / weekRepositoryHomepagenpmAtom feed

Your version

0.8.0

12 Mar 2026Where it was published

0.9.0 is the newest release of 0.8.x.

In short

3 changed

Release note

Published on 2026-03-12.

Changed

  • Update OpenTelemetry dependencies to v2. (minor b85d788)

  • Replace the messaging.bullmq.job.parentOpts.waitChildrenKey span attribute with messaging.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 an addToWaitingChildren boolean flag. The new attribute normalises both representations into a single boolean: true when a flow parent job is waiting for its children to complete. (minor af9eadb)

  • Update messaging semantic convention attributes to latest OpenTelemetry Semantic Conventions for Messaging Spans spec.

    The emitted spans now use the following updated attribute names:

    • messaging.destination renamed to messaging.destination.name

    • messaging.operation replaced by messaging.operation.type (enum: send, create, process) and messaging.operation.name (BullMQ-specific method name, e.g. Queue.add, Worker.run)

    • messaging.message_id renamed to messaging.message.id

    • messaging.consumer_id renamed to messaging.client.id

    • messaging.bullmq.job.bulk.count replaced by the standard messaging.batch.message_count

    Span names now follow the {operation.name} {destination} format, e.g. Queue.add myQueue instead of myQueue publish.

    (minor 9d6e51a)

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.