Packages

@appsignal/nodejs

3.9.5 · 11 Nov 2026MIT24.2k / weekRepositoryHomepagenpmAtom feed

Your version

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

  1. 3.9.5

    11 Nov 2026
    • Fix a crash when setCustomData, setParams or setSessionData is called with a value that contains a BigInt. BigInt values are now stored as "bigint:<n>", the same format used for metric tags and log attributes.

      (patch 3873a46, 5ec6b95)

  2. 3.9.4

    23 Oct 2026
  3. 3.9.3

    22 Oct 2026
    • Security

      Stop trusting certificates issued under the eMudhra intermediate certificate authorities whose private keys were compromised in October 2026. The bundled CA certificates no longer include the emSign ECC Root CA - G3 root certificate, which those intermediates chain to. (patch 498c087, 0178413, b9cbfeb)

  4. 3.9.2

    14 Oct 2026
  5. 3.9.1

    10 Sep 2026
    • Fix the sanitization of function arguments in SQL statements.

      Before this release, SQL sanitization of function arguments stripped out parts of the SQL statement after the function argument list.

      (patch 3f41a3b)

  6. 3.9.0

    8 Sep 2026
    • Breaking

      Drop support for Node.js 18. The minimum supported version is now Node.js 20.6.0, which is what the bundled OpenTelemetry packages require.

      (minor 3994b08)

    • Report queue events from applications that use BullMQ's own telemetry, which is what BullMQ version 6 and newer offer through the bullmq-otel package. These were previously reported as uncategorised events named after the raw span, because BullMQ describes its spans with its own attributes rather than the OpenTelemetry messaging conventions. They are now named and categorised the same way as events from the @appsignal/opentelemetry-instrumentation-bullmq package.

      (minor 96d9030)

    • Warn when your application loads more than one version of @opentelemetry/api, warning about potential data loss, as older versions fail to send data through global values configured by newer versions. The warning names the versions and where they were loaded from.

      (patch 3994b08)

  7. 3.8.1

    10 Jun 2026
    • Continue reporting non-disk host metrics when a mount is frozen. (patch a4a652d)

    • Fix host-metrics leaking zombie [timeout] processes in Alpine linux containers.

      Before this release AppSignal agent relied on a proper init process that reaps child processes killed by system timeout. Now the agent terminates and reaps unresponsive child processes in host-metrics collection and a subreaper is no longer required.

      (patch 5c334bc)

    • Ensure sendError ends its span even when the callback throws. (patch e9c0209)

  8. 3.8.0

    17 Mar 2026
    • Update OpenTelemetry dependencies to v2. All bundled OpenTelemetry packages have been updated to their OpenTelemetry v2-compatible versions. This resolves compatibility issues when third-party span processors or instrumentations are used alongside AppSignal, which could cause spans to silently drop due to v1/v2 incompatibilities. The @opentelemetry/instrumentation-redis-4 package has been removed. Redis v4 instrumentation is now handled by @opentelemetry/instrumentation-redis, which supports both Redis v3 and v4. (minor efbcc4a)

    • Update Prisma instrumentation to v7. The @prisma/instrumentation package has been updated from v6 to v7. The middleware config option has been removed, as Prisma dropped its middleware API in Prisma v5. Prisma's native tracing is now the only supported instrumentation method. (minor efbcc4a)

    • Bundled certificates have been updated. (patch 498c087)

  9. 3.7.4

    5 Feb 2026
    • Require parent spans on database and outgoing HTTP instrumentations that support it. When a database query is performed using the ioredis, pg, redis or mongoose libraries, or when an outgoing HTTP request is performed using the http module, a span will only be created if a trace has already been started in the current active context, that is, if the span to be created would have a parent.

      This helps prevent database queries and outgoing HTTP requests happening in uninstrumented contexts from counting towards your requests quota.

      (patch 57d3cfb)

    • Add support for Koa v3. (patch 08908f2)

  10. 3.7.3

    22 Oct 2025
    • Handle pino logs without a msg attribute. (patch 13e34b0)

  11. 3.7.2

    15 Oct 2025
    • Add a log format option for autodetection the log format. (patch 48a1bde)

    • Add support for native OpenTelemetry spans from @elastic/transport package in Node.js. (patch 663e5b5)

    • Detect the log format automatically. We now detect if a log line is in the JSON, Logfmt, or plaintext format. No further config needed when calling our logger, like so:

      const logger = Appsignal.logger("app");
      logger.info("message");

      (patch 0ccc052)

  12. 3.7.1

    27 Aug 2025
    • Update the OpenTelemetry dependency to version 1.9 of the OpenTelemetry API. This improves compatibility with instrumentation libraries that depend on this version of the API. (patch 4cc4257)

  13. 3.7.0

    22 Aug 2025
    • Disable the OpenTelemetry trace context propagation across applications. If multiple applications are instrumented with AppSignal for Node.js using OpenTelemetry, the propagation across applications could lead to application data being reported the wrong application in AppSignal. (minor 7fc85b8, 7ddcbec)

  14. 3.6.7

    6 Jun 2025
  15. 3.6.6

    8 May 2025
    • Allow overriding namespaces that are automatically set by the AppSignal agent based on the OpenTelemetry instrumentation that emitted the span, such as the graphql or background namespaces. (patch 4c9aae1)

    • Log a debug message when the reported error is ignored by the ignore_errors config option. (patch 4c9aae1)

    • Update mysql2 and pg instrumentations. This fixes an issue where queries performed using promises with mysql2@3.11.5 are not instrumented, as well as an issue where pg is not instrumented under certain bundlers and runtimes. (patch e2d73ab)

  16. 3.6.5

    5 May 2025
    • Remove redundant cron check-in pairs. When more than one pair of start and finish cron check-in events is reported for the same identifier in the same period, only one of them will be reported to AppSignal. (patch 1cfcc0a)

  17. 3.6.4

    31 Mar 2025
    • Breaking

      Drop support for Node.js 16 (patch 0e1e97f)

    • Add support for OpenTelemetry histograms. (patch 2ff4e94)

    • Add support for Node.js 23 (patch 2bd47b9)

  18. 3.6.3

    14 Mar 2025
    • Improve SQL sanitisation for functions and numbered placeholders. (patch b01e6c6)

  19. 3.6.2

    11 Mar 2025
    • Delay and eventually halt agent reboots by the extension.

      The AppSignal extension is responsible for booting the AppSignal agent. If communication with the agent is lost, the extension is responsible for rebooting it.

      In certain scenarios, such as when several processes with different AppSignal configurations are misconfigured to share the same working directory, the processes' extensions can enter a loop of rebooting and killing each others' agents. These short-lived agents may then attempt to repeatedly send pending payloads to AppSignal in quick succession.

      This change causes the extension to delay each reboot of its agent by one additional second, and to no longer attempt to reboot the agent after the tenth reboot, slowing down and eventually breaking this loop.

      (patch ff392c6)

  20. 3.6.1

    27 Feb 2025
    • Update Prisma instrumentation to version 6.4. This improves compatibility with new Prisma versions. (patch 930b3db, 61316bf)

  21. 3.6.0

    24 Feb 2025
    • Breaking

      Minor - Remove the OpenTelemetry beta feature in favor of the new AppSignal collector. If you are using the AppSignal agent to send OpenTelemetry data in our public beta through the /enriched endpoint on the agent's HTTP server, please migrate to the collector to continue using the beta. The collector has a much better implementation of this feature for the beta.

    • Patch - Update span recognition following the OpenTelemetry Semantic Conventions 1.30 database specification. We now also sanitize SQL queries in the db.query.text attribute and Redis queries in the db.operation.name attribute.

    • Patch - Bump the log message when no span is active and one of our sample data helpers are used like setParams, setSessionData, setCustomData, etc from debug to warning.

  22. 3.5.5

    20 Dec 2024
    • Fix a performance issue when sanitising INSERT INTO ... VALUES queries. (patch 9772e93)

  23. 3.5.4

    22 Nov 2024
    • Allow Pino transport to be used as a transport. Before, our Pino transport could only be used as a destination:

      import pino from "pino";
      import { Appsignal, AppsignalPinoTransport } from "@appsignal/nodejs";
      
      pino(AppsignalPinoTransport({
        client: Appsignal.client,
        group: "pino"
      }));

      This meant it was not possible to log both to our transport and to another destination.

      Now, it is also possible to use it as a Pino transport, with the transport Pino config option or the pino.transport() function:

      import pino from "pino";
      
      pino({
        transport: {
          target: "@appsignal/nodejs/pino",
          options: {
            group: "pino"
          }
        }
      });

      It is no longer necessary to pass the AppSignal client to the Pino transport. AppSignal must be active for the Pino transport to work.

      By enabling its use as a transport, it is now possible to use it alongside other transports:

      pino({
        transport: {
          targets: [
            // Send logs to AppSignal...
            { target: "@appsignal/nodejs/pino" },
            // ... and to standard output!
            { target: "pino/file" }
          ]
        }
      });

      (patch 11b789d)

  24. 3.5.3

    7 Nov 2024
    • Set the app revision config option for Scalingo deploys automatically. If the CONTAINER_VERSION system environment variable is present, it will use used to set the revision config option automatically. Overwrite it's value by configuring the revision config option for your application. (patch 5b90b64)

    • Fix an issue where the extension fails to build on ARM64 Linux. (patch 69fcdcf)

  25. 3.5.2

    4 Nov 2024
    • Patch - Add Fastify v5 compatibility

  26. 3.5.1

    16 Oct 2024
    • Patch - A Pino transport is now available. If Pino is your main logger, you can now use the AppSignal pino transport to send those logs to AppSignal.

      import pino from "pino"
      import { Appsignal, AppsignalPinoTransport } from "@appsignal/nodejs"
      
      const logger = pino(
        AppsignalPinoTransport({
          client: Appsignal.client,
          group: "application",
        })
      )
    • Patch - Change the primary download mirror for integrations.

  27. 3.5.0

    26 Sep 2024
    • Add support for heartbeat check-ins.

      Use the checkIn.heartbeat method to send a single heartbeat check-in event from your application. This can be used, for example, in your application's main loop:

      import { checkIn } from "@appsignal/nodejs"
      
      while (true) {
        checkIn.heartbeat("job_processor")
        await processJob()
      }

      Heartbeats are deduplicated and sent asynchronously, without blocking the current thread. Regardless of how often the .heartbeat method is called, at most one heartbeat with the same identifier will be sent every ten seconds.

      Pass {continuous: true} as the second argument to send heartbeats continuously during the entire lifetime of the current process. This can be used, for example, after your application has finished its boot process:

      import { checkIn } from "@appsignal/nodejs"
      
      function main() {
        checkIn.heartbeat("job_processor", {continuous: true})
        startApp()
      }

      (minor 839073e)

    • Send check-ins concurrently. When calling Appsignal.checkIn.cron, instead of blocking the current process while the check-in events are sent, schedule them to be sent in a separate process. (patch a61d16b)

    • Do not block Node.js shutdown. It is no longer necessary to call Appsignal.stop for the Node.js engine to allow itself to shut down. It should still be called and awaited in production scenarios and at the end of scripts, as it ensures that scheduled check-ins are delivered. (patch 0f438d6)

  28. 3.4.9

    14 Aug 2024
    • Deprecated

      Calls to Appsignal.heartbeat and to the Appsignal.Heartbeat constructor will emit a deprecation warning. (patch fc9abba)

    • Rename heartbeats to cron check-ins. Calls to Appsignal.heartbeat and Appsignal.Heartbeat should be replaced with calls to Appsignal.checkIn.cron and Appsignal.checkIn.Cron, for example:

      // Before
      import { heartbeat } from "@appsignal/nodejs"
      
      heartbeat("do_something", () => {
        do_something()
      })
      
      // After
      import { checkIn } from "@appsignal/nodejs"
      
      checkIn.cron("do_something", () => {
        do_something
      })

      (patch fc9abba)

    • Prevent internal AppSignal requests from being instrumented and appearing in the "Slow API requests" panel. (patch 95bf139)

  29. 3.4.8

    4 Jul 2024
    • Fix different spans of the same category incorrectly being reported with the same body. (patch 100e964)

  30. 3.4.7

    20 Jun 2024
    • Patch - Update OpenTelemetry dependencies.

  31. 3.4.6

    14 Jun 2024
    • Patch - Fix an issue where a later span close time than accurate, and therefore a longer span duration, is reported to AppSignal under certain circumstances.

  32. 3.4.5

    12 Jun 2024
    • Patch - Add BullMQ support through the @appsignal/opentelemetry-instrumentation-bullmq instrumentation. AppSignal will automatically instrument the use of BullMQ in your application.

      Calls to functions that enqueue jobs, such as Queue.add and others, will be instrumented as an event in the event timeline for the performance sample in which it takes place.

      When a BullMQ Worker processes a job, this will result in a performance sample in the background namespace.

    • Patch - Add basic OpenTelemetry messaging support. This adds support for any OpenTelemetry instrumentation that complies with the OpenTelemetry Semantic Conventions specification for messaging.

    • Patch - Rename the hostname tag, which contains the host of the URI that an HTTP request was made against, to request_host.

      This fixes an issue where the hostname tag would later be internally overriden to the hostname of the machine processing the request, but notifications would still be emitted containing the previous hostname value.

  33. 3.4.4

    14 May 2024
    • Patch - Instrument calls to fetch in Node.js. Requests made using Node.js' global fetch, or through the underlying undici library, will be automatically instrumented and shown as events in your performance samples' event timeline.

  34. 3.4.3

    14 May 2024
    • Patch - Instrument calls to fetch in Node.js. Requests made using Node.js' global fetch, or through the underlying undici library, will be automatically instrumented and shown as events in your performance samples' event timeline.

    • Patch - Support Kamal-based deployments. Read the KAMAL_VERSION environment variable, which Kamal exposes within the deployed container, if present, and use it as the application revision if it is not set. This will automatically report deploy markers for applications using Kamal.

    • Patch - ### Improve error reporting during initialisation

      Do not report an error with the extension installation when AppSignal is imported -- instead, report it when attempting to initialise AppSignal. Do not report an error with the extension if AppSignal is not configured to be active.

      When AppSignal does not start due to its configuration (active is set to false, or the push API key is missing) report the specific reason why.

  35. 3.4.2

    7 May 2024
    • Patch - Ignore AMQP spans if they're root spans.

    • Patch - The AMQP protocol is now instrumented when using amqplib. The AppSignal client automatically instruments and creates spans when using amqplib. Packages using amqplib such as Rascal are supported.

    • Patch - Log debug messages when metrics are received for easier debugging.

  36. 3.4.1

    24 Apr 2024
    • Patch - Fix an issue where internal Next.js traces were not correctly ignored in certain circumstances.

  37. 3.4.0

    22 Apr 2024
    • Minor - Heartbeats are currently only available to beta testers. If you are interested in trying it out, send an email to support@appsignal.com!


      Add heartbeats support. You can send heartbeats directly from your code, to track the execution of certain processes:

      import { heartbeat } from "@appsignal/nodejs"
      
      function sendInvoices() {
        // ... your code here ...
        heartbeat("send_invoices")
      }

      You can pass a function to heartbeat, to report to AppSignal both when the process starts, and when it finishes, allowing you to see the duration of the process:

      import { heartbeat } from "@appsignal/nodejs"
      
      function sendInvoices() {
        heartbeat("send_invoices", () => {
          // ... your code here ...
        })
      }

      If an exception is raised within the function, the finish event will not be reported to AppSignal, triggering a notification about the missing heartbeat. The exception will bubble outside of the heartbeat function.

      If the function passed to heartbeat returns a promise, the finish event will be reported to AppSignal if the promise resolves. This means that you can use heartbeats to track the duration of async functions:

      import { heartbeat } from "@appsignal/nodejs"
      
      async function sendInvoices() {
        await heartbeat("send_invoices", async () => {
          // ... your async code here ...
        })
      }

      If the promise is rejected, or if it never resolves, the finish event will not be reported to AppSignal.

    • Patch - Implement the ignoreLogs configuration option, which can also be configured as the APPSIGNAL_IGNORE_LOGS environment variable.

      The value of ignoreLogs is a list (comma-separated, when using the environment variable) of log line messages that should be ignored. For example, the value "start" will cause any message containing the word "start" to be ignored. Any log line message containing a value in ignoreLogs will not be reported to AppSignal.

      The values can use a small subset of regular expression syntax (specifically, ^, $ and .*) to narrow or expand the scope of lines that should be matched.

      For example, the value "^start$" can be used to ignore any message that is exactly the word "start", but not messages that merely contain it, like "Process failed to start". The value "Task .* succeeded" can be used to ignore messages about task success regardless of the specific task name.

    • Patch - Appsignal.stop() now returns a promise. For your application to wait until AppSignal has been gracefully stopped, this promise must be awaited:

      import { Appsignal } from "@appsignal/nodejs"
      
      await Appsignal.stop()
      process.exit(0)

      In older Node.js versions where top-level await is not available, terminate the application when the promise is settled:

      import { Appsignal } from "@appsignal/nodejs"
      
      Appsignal.stop().finally(() => {
        process.exit(0)
      })
  38. 3.3.4

    19 Apr 2024
    • Patch - Fix incorrect HTTP methods like render or getServerSideProps in Next.js 14 performance samples.

  39. 3.3.3

    17 Apr 2024
    • Patch - Fix UNKNOWN method in Next.js 14 performance traces.

  40. 3.3.2

    22 Mar 2024
    • Patch - Implement CPU count configuration option. Use it to override the auto-detected, cgroups-provided number of CPUs that is used to calculate CPU usage percentages.

      To set it, use the cpuCount configuration option, or the APPSIGNAL_CPU_COUNT environment variable.

  41. 3.3.1

    21 Mar 2024
    • Patch - Don’t evaluate environment variable values to read configuration

      In previous versions of the Node.js integration, environment variables were evaluated to read their values. This version instead parses them based on their expected values.

  42. 3.3.0

    12 Mar 2024
    • Minor - Add Node.js Apollo Gateway span mapping. This supports reporting OpenTelemetry Apollo Gateway spans as AppSignal spans, for the Node.js integration.

  43. 3.2.0

    6 Mar 2024
    • Breaking

      Minor - Breaking change: Normalize CPU metrics for cgroups v1 systems. When we can detect how many CPUs are configured in the container's limits, we will normalize the CPU percentages to a maximum of 100%. This is a breaking change. Triggers for CPU percentages that are configured for a CPU percentage higher than 100% will no longer trigger after this update. Please configure triggers to a percentage with a maximum of 100% CPU percentage.

    • Patch - Add histogram support to the OpenTelemetry HTTP server. This allows OpenTelemetry-based instrumentations to report histogram data to AppSignal as distribution metrics.

    • Patch - Support fractional CPUs for cgroups v2 metrics. Previously a CPU count of 0.5 would be interpreted as 1 CPU. Now it will be correctly seen as half a CPU and calculate CPU percentages accordingly.

  44. 3.1.0

    7 Feb 2024
    • Minor - The OpenTelemetry metric exporter is now initialized by default. The integration will send default metrics from the instrumentations, and also allows you to send your custom metrics using OpenTelemetry to AppSignal to build your own dashboards.

    • Patch - Make the debug log message for OpenTelemetry spans from libraries we don't automatically recognize more clear. Mention the span id and the instrumentation library.

    • Patch - Fix an issue where queries containing a MySQL leading type indicator would only be partially sanitised.

  45. 3.0.30

    15 Jan 2024
    • Breaking

      Patch - Remove the appsignal_set_host_gauge and appsignal_set_process_gauge extension functions. These functions were already deprecated and did not report any metrics.

    • Patch - When the AppSignal log level is set to "trace". Additional information from the OpenTelemetry instrumentations is now logged.

    • Patch - Fix disk usage returning a Vec with no entries on Alpine Linux when the df --local command fails.

  46. 3.0.29

    7 Dec 2023
    • Patch - Update OpenTelemetry dependencies. This fixes a known issue with Next.js and webpack compatibility and includes other fixes.

  47. 3.0.28

    6 Dec 2023
    • Patch - Update the diagnose tool URLs printed by the CLI and package to the new location in our documentation.

    • Patch - Fix compatibility issue with Node.js's node-gyp package and Python 3.12.0. Python 3.12.0 removed a package called "distutils", causing the extension to fail to install. Upgrade the node-gyp package with the fix for this issue.

  48. 3.0.27

    6 Dec 2023
    • Patch - Remove route tag from HTTP server spans. Since the span will already have the route attribute as part of its name, the tag is redundant.

    • Patch - Filter more disk mountpoints for disk usage and disk IO stats. This helps reduce noise in the host metrics by focussing on more important mountpoints.

      The following mountpoint are ignored. Any mountpoint containing:

    • Patch - Fix an issue where the method tag extracted from an incoming HTTP request span would be overriden with the method used for an outgoing HTTP request span.

  49. 3.0.26

    21 Nov 2023
    • Patch - Bump agent to eec7f7b

      Updated the probes dependency to 0.5.2. CPU usage is now normalized to the number of CPUs available to the container. This means that a container with 2 CPUs will have its CPU usage reported as 50% when using 1 CPU instead of 100%. This is a breaking change for anyone using the cpu probe.

      If you have CPU triggers set up based on the old behaviour, you might need to update those to these new normalized values to get the same behaviour. Note that this is needed only if the AppSignal integration package you're using includes this change.

  50. 3.0.25

    6 Nov 2023
    • Patch - Add initializeOpentelemetrySdk configuration option. This allows those who would rather take control of how OpenTelemetry is initialised in their application to skip AppSignal's initialization of the OpenTelemetry SDK.

      Additionally, add an opentelemetryInstrumentations method on the client, which returns AppSignal's default OpenTelemetry instrumentations, already configured to work correctly with AppSignal. The provided list of instrumentations will follow the additionalInstrumentations and disableDefaultInstrumentations config options, if those are set.

      This is not the recommended way to use AppSignal for Node.js. Only use this config option and this method if you're really sure that you know what you're doing.

      When initialising OpenTelemetry, it is necessary to add the AppSignal span processor in order for data to be sent to AppSignal. For example, using the OpenTelemetry SDK:

      import { SpanProcessor, Appsignal } from "@appsignal/nodejs";
      // or: const { SpanProcessor, Appsignal } = require("@appsignal/nodejs")
      
      const sdk = new NodeSDK({
        spanProcessor: new SpanProcessor(Appsignal.client)
        instrumentations: Appsignal.client.opentelemetryInstrumentations()
      });
      
      sdk.start()

      The above snippet assumes that the AppSignal client has been initialised beforehand.

      When making use of this config option, the OpenTelemetry instrumentations must be configured in the same way as it is done in the AppSignal integration. In the above snippet, the instrumentations property in the OpenTelemetry SDK is set to the AppSignal client's list of OpenTelemetry instrumentations, which are configured to work correctly with AppSignal.

    • Patch - Add the setSqlBody tracing helper to set the body attribute on a span that contains a SQL query. When using this helper the given SQL query will be sanitized, reducing the chances of sending sensitive data to AppSignal.

      import { setSqlBody } from "@appsignal/nodejs";
      
      // Must be used in an instrumented context -- e.g. an Express route
      setSqlBody("SELECT * FROM users WHERE 'password' = 'secret'");
      // Will be stored as: "SELECT * FROM users WHERE 'password' = ?"

      When the setBody helper is also used, the setSqlBody overwrites the setBody attribute.

      More information about our tracing helpers can be found in our documentation.

    • Patch - Bump agent to b604345.

      Bump agent to 8260fa1.

      More information on AppSignal OpenTelemetry span attributes can be found in our docs.

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.