Packages

@appsignal/opentelemetry-instrumentation-bullmq

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

Your version

7 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.

  1. 0.9.x · latest line
  2. 0.9.0

    24 Aug 2026
    • Declare @opentelemetry/api as a peer dependency instead of a regular dependency, so that npm installs one copy of it, shared with your application.

      Two copies of @opentelemetry/api in the same project can silently stop this instrumentation from reporting anything. The OpenTelemetry API keeps its global tracer provider on a global object, and a copy of the API only reads that global when its version is compatible with the version that wrote it. When the copies do not match, this instrumentation receives a tracer that does nothing, and no error is reported.

      If your project pins @opentelemetry/api to a version outside the range this package supports, npm will now warn you about it at install time rather than installing a second copy.

      (minor ef2b86e)

    • Update the bundled @opentelemetry/instrumentation and @opentelemetry/semantic-conventions packages to their current versions. The span attributes this instrumentation emits are unchanged.

      (minor d0e4815)

  3. 0.8.x
  4. 0.8.0

    12 Mar 2026
    • 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:

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

      (minor 9d6e51a)

  5. 0.7.x
  6. 0.7.3

    8 Oct 2024
    • Add a useProducerSpanAsConsumerParent configuration option that defaults to false. When set to true, 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)

  7. 0.7.2

    1 Oct 2024
    • Fix importing the package as an ESM module. (patch 814d93a)

  8. 0.7.1

    13 Jun 2024
    • Mark BullMQ peer dependency as optional.

    • Do not reexport bullmq types.

  9. 0.6.x
  10. 0.6.0

    10 Jun 2024

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.