npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@mzahor-test-org/instrumentation-amqplib

v0.27.0

Published

OpenTelemetry automatic instrumentation for the `amqplib` package

Downloads

4

Readme

OpenTelemetry Amqplib (RabbitMQ) Instrumentation for Node.js

NPM Published Version Apache License

This module provides automatic instrumentation for amqplib (RabbitMQ)

For automatic instrumentation see the @opentelemetry/sdk-trace-node package.

Compatible with OpenTelemetry JS API and SDK 1.0+.

Installation

npm install --save @opentelemetry/instrumentation-amqplib

Supported Versions

  • >=0.5.5

Usage

OpenTelemetry amqplib Instrumentation allows the user to automatically collect trace data and export them to the backend of choice, to give observability to distributed systems when working with amqplib (RabbitMQ).

To load a specific plugin, specify it in the registerInstrumentations's configuration:

const { NodeTracerProvider } = require('@opentelemetry/sdk-trace-node');
const { AmqplibInstrumentation } = require('@opentelemetry/instrumentation-amqplib');
const { registerInstrumentations } = require('@opentelemetry/instrumentation');

const provider = new NodeTracerProvider();
provider.register();

registerInstrumentations({
  instrumentations: [
    new AmqplibInstrumentation({
      // publishHook: (span: Span, publishInfo: PublishInfo) => { },
      // publishConfirmHook: (span: Span, publishConfirmedInto: PublishConfirmedInfo) => { },
      // consumeHook: (span: Span, consumeInfo: ConsumeInfo) => { },
      // consumeEndHook: (span: Span, consumeEndInfo: ConsumeEndInfo) => { },
    }),
  ],
})

amqplib Instrumentation Options

amqplib instrumentation has few options available to choose from. You can set the following:

| Options | Type | Description | | --------------------------------- | ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | | publishHook | AmqplibPublishCustomAttributeFunction | hook for adding custom attributes before publish message is sent. | | publishConfirmHook | AmqplibPublishConfirmCustomAttributeFunction | hook for adding custom attributes after publish message is confirmed by the broker. | | consumeHook | AmqplibConsumerCustomAttributeFunction | hook for adding custom attributes before consumer message is processed. | | consumeEndHook | AmqplibConsumerEndCustomAttributeFunction | hook for adding custom attributes after consumer message is acked to server. | | consumeTimeoutMs | number | read Consume Timeout below |

Consume Timeout

When user is setting up consume callback, it is user's responsibility to call ack/nack etc on the msg to resolve it in the server. If user is not calling the ack, the message will stay in the queue until channel is closed, or until server timeout expires (if configured).

While we wait for the ack, a reference to the message is stored in plugin, which will never be garbage collected. To prevent memory leak, plugin has it's own configuration of timeout, which will close the span if user did not call ack after this timeout.

If timeout is not big enough, span might be closed with 'InstrumentationTimeout', and then received valid ack from the user later which will not be instrumented.

Default is 1 minute

Migration From opentelemetry-instrumentation-amqplib

This instrumentation was originally published under the name "opentelemetry-instrumentation-amqplib" in this repo. Few breaking changes were made during porting to the contrib repo to align with conventions:

Hook Info

The instrumentation's config publishHook, publishConfirmHook, consumeHook and consumeEndHook functions signature changed, so the second function parameter is info object, containing the relevant hook data.

moduleVersionAttributeName config option

The moduleVersionAttributeName config option is removed. To add the amqplib package version to spans, use the moduleVersion attribute in hook info for publishHook and consumeHook functions.

Useful links

License

Apache 2.0 - See LICENSE for more information.