3.0.1

Added

• 0353a5f patch - Support for Fastify request parameters. Request parameters (query, body) are now added to the HTTP spans when using Fastify.
• c1354f0 patch - Add Knex.js instrumentation. We will now auto instrument database queries made with Knex.js.
• 2e11cb2 patch - Support log collection from Node.js apps using the new AppSignal Logging feature. Learn more about AppSignal's Logging on our docs.

3.0.0-beta.7

Added

• e01b1d3 patch - Add MongoDB instrumentation
• b21d2cc patch - Instrument outgoing HTTP requests

3.0.0-beta.6

Changed

• fcdaac2 patch - Bump agent version to support fs instrumentation

3.0.0-beta.5

Added

• cee020f patch - Add fs module support

Fixed

• ec9aa36 patch - Only set the params on Koa router layer, instead of on all layers.

3.0.0-beta.4

Added

• 470c129 patch - Add Fastify support
• bcf182b patch - Add OpenTelemetry SpanKind as a magic attribute
• daeeaac patch - Add Mongoose support

3.0.0-beta.3

Added

• c07b3a4 patch - Add support for Nest.js
• 8128eb9 patch - Update the AppSignal agent version to add Nest.js support.

Fixed

• 8128eb9 patch - Update the AppSignal agent version to fix an issue with the HTTP proxy where the proxy port would always be set to 8080.

3.0.0

Welcome to AppSignal for Node.js version 3.0.0.!

In this release, we have switched to using OpenTelemetry internally for tracing. (We do not yet support OpenTelemetry for metrics and logging, but do continue to support metrics through our own metrics system.) The AppSignal instrumentation packages @appsignal/express, @appsignal/koa, @appsignal/nextjs and @appsignal/apollo-server should no longer be used. Some official OpenTelemetry instrumentation packages are bundled with our package as dependencies and instrumented automatically. Other supported instrumentation packages can be added and configured manually.

We strongly recommend following the [migration guide] while upgrading. Instrumentation from package version 2 is not compatible with version 3. Custom instrumentation will need to be set up using OpenTelemetry instrumentation.

If you run into any issues upgrading to this new version, please contact us at [support@appsignal.com][support] for help.

• [Version 3 migration guide][migration guide]
• [Contact us for support][support]

Added

• Add support for express package
• Add support for graphql package
• Add support for ioredis package
• Add support for Fastify
• Add support for Knex.js
• Add support for koa package
• Add support for mysql package
• Add support for mysql2 package
• Add support for MongoDB
• Add support for Mongoose
• Add support for Nest.js
• Add support for Next.js
• Add support for pg package
• Add support for prisma package
• Add support for redis package
• Add support for redis package version 4
• Add support for the fs module
• Instrument outgoing HTTP requests

Changed

• Use OpenTelemetry for tracing instrumentation of libraries and Node.js modules.
• Remove dependency on @appsignal/* instrumentation packages.

3.0.0-beta.2

Changed

• 23192ef patch - Bump agent to v-de2dd6e.

  • Remove fallback for unknown span body. The notice about a missing extractor is now a trace level log.
  • Filter root span attributes that are set as tags, params, headers, etc.
  • Filter more root span attributes that can contain PII information.
  • Improve http extractor span name to use http.route attribute to always build the incident action name. This should avoid new incidents with HTTP POST-like naming.

3.0.0-beta.1

Added

• ded7a82 major - Add OpenTelemetry support to the AppSignal Node.js integration. This new major release uses OpenTelemetry to support tracing instrumentation. The old @appsignal/<package name> instrumentation packages are not compatible. Please remove them before upgrading.

Changed

• d452b46 patch - Support OpenTelemetry root spans in SpanProcessor. This change makes AppSignal instrumentation (like Express/Koa.js/Next.js) no longer a requirement. In fact you will need to use the OpenTelemetry instrumentation for those libraries from now on.

• 60428c8 patch - Bump agent to v-d573c9b

  • Display unsupported OpenTelemetry spans in limited form.
  • Clean up payload storage before sending. Should fix issues with locally queued payloads blocking data from being sent.
  • Add appsignal_create_opentelemetry_span function to create spans for further modification, rather than only import them.

• a1d947c patch - Remove the mysql2 package peer dependency. It's not only present as a development dependency for the package.

• 54491fa patch - Bump agent to 06391fb

  • Accept "warning" value for the log_level config option.
  • Add aarch64 Linux musl build. Doesn't work for Node.js package.
  • Improve debug logging from the extension.
  • Fix high CPU issue for appsignal-agent when nothing could be read from the socket.

Removed

• 2b95a68 major - Remove debug config option. This has been replaced with logLevel set to debug.
• 13bc306 major - Remove the apiKey config option. This has been renamed to pushApiKey.

Fixed

• d452b46 patch - Improve the error message on extension load failure. The error message will now print more details about the installed and expected architecture when they mismatch. This is most common on apps mounted on a container after first being installed on the host with a different architecture than the container.
• fa13d19 patch - Accept uppercase input in diagnose tool send report prompt. When prompted to send the report when the diagnose tool, it will now also accept uppercase values like "Y" and "N".

2.4.2

Changed

• b7382d7 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.

• 7a7bc9b 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()
  

Fixed

• 8a32a21 patch - Only allow open root spans to be set as root. This avoids closed root spans to be reused in child contexts.
• 4b74e2f patch - Don't return closed spans in withSpan helper. If a closed span was given to the witSpan helper it would temporarily overwrite the context with a closed span that cannot be modified. Instead it will return the current active span, if any. If no span was active it will return a NoopSpan.
• 1731c8e patch - Add @opentelemetry/sdk-trace-base package runtime dependency. Our OpenTelemetry SpanProcessor needs this package at runtime, not just at compile time.