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.x · latest line
  2. 3.0.24

    20 Oct 2023
    • Patch - Bump agent to e8207c1.

    • Patch - Update Fastify dependency to make it compatible with Fastify 5

  3. 3.0.23

    10 Oct 2023
    • Patch - Update OpenTelemetry dependencies to the latest versions.

  4. 3.0.22

    6 Oct 2023
    • Patch - Report express route parameters. If a route is defined like /user/:id, the id parameter will be reported from now on in the "Parameters" box on AppSignal.com.

  5. 3.0.21

    4 Sep 2023
    • Patch - Improve the behaviour of the GraphQL instrumentation, so that it creates less redundant spans for similar items in a list, and less trivial spans for attribute resolutions.

    • Patch - Fix a misleading platform mismatch error when the AppSignal extension fails to load on musl-based systems.

  6. 3.0.20

    30 Aug 2023
    • Patch - Bump agent to 6133900.

  7. 3.0.19

    25 Aug 2023
    • Patch - Add the hostRole config option. This config option can be set per host to generate some metrics automatically per host and possibly do things like grouping in the future.

  8. 3.0.18

    17 Aug 2023
    • Patch - Bump agent to version d789895.

  9. 3.0.17

    31 Jul 2023
    • Patch - Report total CPU usage host metric for VMs. This change adds another state tag value on the cpu metric called total_usage, which reports the VM's total CPU usage in percentages.

    • Patch - Add the --config flag to diagnose command to specify a custom path for your AppSignal configuration file to be taken into account when running the diagnose of your AppSignal installation.

    • Patch - Bump agent to 6bec691.

  10. 3.0.16

    21 Jul 2023
    • Patch - Allow configuration of the agent's StatsD server port through the statsdPort option.

    • Patch - Use RENDER_GIT_COMMIT environment variable as revision if no revision is specified.

    • Patch - Support Prisma 5

  11. 3.0.15

    26 May 2023
    • Deprecated

      Patch - Add deprecation warning to instrumentationsLoaded helper

    • Patch - The diagnose CLI command now reports on the presence of the appsignal.cjs file.

    • Patch - Load the AppSignal app configuration file when running the diagnose to include the configuration in the diagnose report.

  12. 3.0.14

    2 May 2023
    • Patch - Update agent to version 6f29190.

  13. 3.0.13

    14 Apr 2023
    • Patch - Update OpenTelemetry dependencies to the latest versions, providing many improvements and bug fixes.

  14. 3.0.12

    22 Mar 2023
    • Patch - Fix grouping for Prisma queries.

  15. 3.0.11

    22 Feb 2023
  16. 3.0.10

    14 Feb 2023
    • Patch - Support Winston child logger groups when using the Winston transport

      When using the Winston transport for our logging feature, the child loggers with an assigned group will send the group to AppSignal when logging messages.

  17. 3.0.9

    13 Feb 2023
  18. 3.0.8

    7 Feb 2023
  19. 3.0.7

    1 Feb 2023
    • Breaking

      Patch - Remove fs instrumentation by default. It's causing issues on some installations. It can be manually added as described in our fs module docs.

  20. 3.0.6

    31 Jan 2023
  21. 3.0.5

    24 Jan 2023
    • Patch - Bump agent to 041b9c4.

    • Patch - Update prisma instrumentation package. Fixes installation deprecation warning.

  22. 3.0.4

    20 Jan 2023
    • Patch - Add OpenTelemetry SDK initialization helper function

      The OpenTelemetry instrumentations are loaded async, this is OK when users rely on automatic instrumentations, but for custom instrumentations it might cause spans not to be reported. There's a new helper function that contains the instrumentations registration that can be awaited for resolution before running any custom instrumentations.

  23. 3.0.3

    16 Jan 2023
    • Patch - Track the Operating System release/distro in the diagnose report. This helps us with debugging what exact version of Linux an app is running on, for example.

    • Patch - Report request parameters for restify apps. This is reported automatically. You can disable parameter reporting with the AppSignal sendParams: false configuration option.

    • Patch - Add Winston transport support for the logging feature.

  24. 3.0.2

    22 Dec 2022
    • Patch - Add support for the restify package.

    • Patch - Remove client IP from HTTP traces

  25. 3.0.1

    24 Nov 2022
    • Patch - Support for Fastify request parameters. Request parameters (query, body) are now added to the HTTP spans when using Fastify.

    • Patch - Add Knex.js instrumentation. We will now auto instrument database queries made with Knex.js.

    • Patch - Support log collection from Node.js apps using the new AppSignal Logging feature. Learn more about AppSignal's Logging on our docs.

  26. 3.0.0

    21 Oct 2022
  27. 2.x
  28. 2.4.2

    8 Jun 2022
    • Patch - Do not restore closed spans from within the withSpan helper. If a previously active span gets closed while withSpan has another span as currently active, do not restore the closed span when the callback has finished.

    • Patch - Do not restore root span after withSpan callback has finished. Previously the root span was restored to the original root span before the withSpan helper was called. This has been changed, because the withSpan helper is only about changing the active span, not the root span. If a new root span has been set within a withSpan helper callback, the root span will no longer be restored. We recommend setting a new root span before calling withSpan instead.

      const rootSpan = tracer.rootSpan()
      const span = tracer.createSpan(...)
      tracer.withSpan(span, function(span) {
        tracer.createRootSpan(...)
      });
      // No longer match
      rootSpan != tracer.rootSpan()
    • Patch - Only allow open root spans to be set as root. This avoids closed root spans to be reused in child contexts.

  29. 2.4.1

    7 Jun 2022
    • Patch - Do not instrument HTTP requests to the default socket.io path. This works around an issue where our HTTP instrumentation breaks socket.io's server side, causing the client side to get stuck in a connection loop.

    • Patch - Fix removing event listeners from wrapped event emitters. When using tracer.wrapEmitter to wrap an event emitter, it was not possible to remove any listeners that were added after the event emitter was wrapped.

  30. 2.4.0

    2 Jun 2022
    • Minor - Add OpenTelemetry span processor for the mysql and mysql2 packages. These are experimental integrations and require additional set up to integrate with OpenTelemetry.

    • Patch - Add config options for disabling default instrumentation like HTTP, HTTPS, PostgreSQL (pg package) and Redis (node-redis package).

      The following configuration options have been added:

      By default these configuration options are set to true, which means the instrumentation is active by default. If you want to disable one of these instrumentations, configure it by setting the configuration option to false.

      // appsignal.js
      // Brief example, see our docs for a full example
      
      const appsignal = new Appsignal({
        instrumentRedis: false // Disables the node-redis package instrumentation
      });
    • Patch - Add OpenTelemetry node-redis and ioredis query sanitizers. We recommend using these sanitizers to ensure no sensitive data is sent in query statements. Add the sanitizer to the dbStatementSerializer config as demonstrated below.

      // tracing.js
      // Add the RedisDbStatementSerializer import
      const { RedisDbStatementSerializer } = require("@appsignal/nodejs");
      const { RedisInstrumentation } = require("@opentelemetry/instrumentation-redis");
      const sdk = new opentelemetry.NodeSDK({
        instrumentations: [
          new RedisInstrumentation({
            // Configure the AppSignal RedisDbStatementSerializer to sanitize queries
            dbStatementSerializer: RedisDbStatementSerializer
          })
        ]
      });

      The same can be done for the ioredis instrumentation:

      // tracing.js
      // Add the IORedisDbStatementSerializer import
      const { IORedisDbStatementSerializer } = require('@appsignal/nodejs');
      const { IORedisInstrumentation } = require('@opentelemetry/instrumentation-ioredis');
      const sdk = new opentelemetry.NodeSDK({
        instrumentations: [
          // Add the IORedisInstrumentation
          new IORedisInstrumentation({
            // Configure the AppSignal IORedisDbStatementSerializer to sanitize queries
            dbStatementSerializer: IORedisDbStatementSerializer
          })
        ]
      });
  31. 2.3.6

    11 May 2022
    • Patch - Add the createRootSpan function to the Tracer to allow explicit creation of RootSpans even if another RootSpan already exists and is tracked as the current RootSpan. Make sure to not forget about the previous RootSpan, and close it as well at some point when using this function.

  32. 2.3.5

    29 Apr 2022
    • Patch - Use the Node.js performance module as high-resolution timer for span creation and close times. This provides more accurate times and improves compatibility with other systems in the future.

    • Patch - When instrumenting an outgoing HTTP request, read the host property from the request options if the hostname property is not present. This fixes a bug where outgoing HTTP request hosts would be shown as http://localhost.

    • Patch - Fix error on Microsoft Windows machines on install. The AppSignal extension still won't install on Windows, but now it won't cause an error while checking a development mode condition if it should build the TypeScript package.

  33. 2.3.4

    11 Apr 2022
    • Patch - Update node-gyp to major version 9.0.0. This drops compatibility with Python 2.7 for the extension install, but it makes it compatible with the latest Python 3 version, which should be more accessible to users going forward.

    • Patch - Ensure the root span is preserved across scopes. Due to a bug in the scope management logic, calling tracer.withSpan could cause the root span for a given scope to be forgotten.

  34. 2.3.3

    11 Apr 2022
    • Patch - Log messages are now sent through a new centralized logger that writes to /tmp/appsignal.log by default. A warning is printed to STDERR when the default or provided logPath is not accessible, and the Logger automatically falls back to STDOUT. Use config option log: stdout to log AppSignal messages to STDOUT instead.

    • Patch - Bump agent to v-bbc830a

    • Patch - Bump agent to v-f57e6cb

  35. 2.3.2

    15 Feb 2022
    • Breaking

      Patch - Remove the private function Span.toJSON. This wasn't previously marked as private, but it was.

    • Breaking

      Patch - Do not ship the extension install script test files in the published package. Reduces the package size a tiny bit.

    • Breaking

      Patch - Remove the unused experimental module.

  36. 2.3.1

    26 Jan 2022
    • Patch - The supported Redis version is now locked to 3.x.x. This will prevent app startup failures for users with Redis 4.x.x.

  37. 2.3.0

    20 Jan 2022
    • Patch - Implement unregister method for probes. You can now call the probes.unregister(name) method to unregister a probe by name.

    • Minor - The extension package (@appsignal/nodejs-ext) is no longer a separated dependency. The extension is part of the @appsignal/nodejs package now.

    • Patch - Update install report path location. The "nodejs" package now stores the install report in its own package path, with the rest of the extension files. This makes it easier to access by the diagnose report.

  38. 2.2.10

    10 Jan 2022
    • Patch - Update @appsignal/nodejs-ext dependency to 2.0.7.

  39. 2.2.9

    10 Jan 2022
    • Patch - The sendSessionData config option is now available. When set to false, it prevents the integration from sending session data to AppSignal.

  40. 2.2.8

    4 Jan 2022
    • Patch - The caFilePath config option now works for diagnose script external requests.

    • Patch - Add helper to access the globally stored AppSignal client.

    • Patch - The sendParams config option is now available. When set to false, it prevents the integration from sending request params to AppSignal.

  41. 2.2.7

    9 Dec 2021
    • Patch - Fix debug and transaction_debug_mode log options. If set, previously the log_level would remain "info", since version 2.2.6.

  42. 2.2.6

    8 Dec 2021
    • Deprecated

      Patch - Deprecate "debug" and "transactionDebugMode" config options in favor of the new "logLevel" config option.

    • Patch - Add send_environment_metadata config option to configure the environment metadata collection. For more information, see our environment metadata docs.

    • Patch - Add "logLevel" config option. This new option allows you to select the type of messages AppSignal's logger will log and up. The "debug" option will log all "debug", "info", "warning" and "error" log messages. The default value is: "info"

      The allowed values are:

  43. 2.2.5

    24 Nov 2021
    • Patch - Send the diagnose report with correct query parameters to help link the report to the app and organization on AppSignal.com.

    • Patch - The AppSignal config is not considered valid anymore when the apiKey config option is not set.

    • Patch - Print the extension installation dependencies and flags in the diagnose report output.

  44. 2.2.4

    4 Nov 2021
  45. 2.2.3

    3 Nov 2021
    • Patch - Fix diagnose report recognition when sent to the server. It was sent without an api_key parameter, which resulted in apps not being linked to the parent organization based on the known Push API key.

    • Patch - Transmit the path file modes in the diagnose report as an octal number. Previously it send values like 33188 and now it transmits 100644, which is a bit more human readable.

    • Patch - Update @appsignal/nodejs-ext dependency to 2.0.3.

  46. 2.2.2

    27 Oct 2021
    • Patch - Fix sending the agent diagnose report with all reports. It was sent, but with the wrong key, which made our server side validator report it as missing.

    • Patch - Print agent diagnose report in diagnose CLI output.

    • Patch - Add new config option to enable/disable StatsD server in the AppSignal agent. This new config option is called enableStatsd and is set to false by default. If set to true, the AppSignal agent will start a StatsD server on port 8125 on the host.

  47. 2.2.1

    25 Oct 2021
    • Patch - The diagnose report will report parsing errors on reading or parsing the installation report. Previously, a missing installation report file would crash the diagnose tool.

    • Patch - Print String values in the diagnose report surrounded by quotes. Makes it more clear that it's a String value and not a label we print.

    • Patch - Correct the diagnose host section indenting, it was indented one level too far to the right when printed.

  48. 2.2.0

    13 Oct 2021
    • Minor - Remove interface usage from @appsignal/types

      All Node.js-specific interfaces from the types package are now defined inside the nodejs core package. There's still a dependency from types package for common types as Func, HashMap, and HasMapValue.

      With this change, we keep taking advantage of interfaces, but now they're defined in a place where they're used.

  49. 2.1.1

    11 Oct 2021
    • Patch - Show correct language version in diagnose's extension installation section. It did not show the language version used during install, but the current one used to run the diagnose tool.

    • Patch - Rename the Agent module to Extension to fit better with our naming standards.

    • Patch - Fix diagnose installation status reporting. It previously always reported "success", but will now also print failures.

  50. 2.1.0

    5 Oct 2021
    • Minor - Add rootSpan and setError helpers.

      Errors added to child spans are ignored by the agent. Now the rootSpan is always accessible from the tracer object as well as setError. The setError function allows to track errors on demand and they will be always attached to the main current span, so they don't get ignored by the agent.

    • Patch - Bug fix in custom timestamp calculation

    • Patch - Deprecate the addError function on the Span interface. Instead use the Tracer's setError function to set the error on the root span.

  51. 2.0.0

    19 Aug 2021
    • Major - Drop support for Node.js 10 and 11. These are unmaintained versions of Node.js.

    • Patch - Update @appsignal/nodejs-ext dependency to 2.0.0.

  52. 1.x
  53. 1.3.2

    12 Aug 2021
    • Patch - Update @appsignal/nodejs-ext dependency to 1.2.9.

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.