3.0.30

Added

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

Changed

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

Removed

• 6b75b87 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.

Fixed

• c49dbf3 patch - Fix the demo sample recognition. Demo samples didn't show the helpful explanation box in the UI, because the demo_sample tag was set incorrectly as an attribute.

3.0.29

Changed

• ec9c4fb patch - Update OpenTelemetry dependencies. This fixes a known issue with Next.js and webpack compatibility and includes other fixes.

3.0.28

Fixed

• 72e9e73 patch - Update the diagnose tool URLs printed by the CLI and package to the new location in our documentation.
• 96b8545 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.

3.0.27

Changed

• 5c460cc 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.

• 5c460cc 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:

  • /etc/hostname
  • /etc/hosts
  • /etc/resolv.conf
  • /snap/
  • /proc/

Fixed

• 5c460cc 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.
• 5c460cc patch - - Support disk usage reporting (using df) on Alpine Linux. This host metric would report an error on Alpine Linux.
  • When a disk mountpoint has no inodes usage percentage, skip the mountpoint, and report the inodes information successfully for the inodes that do have an inodes usage percentage.
• 7ec2008 patch - Fix missing error metrics for the error rate and error count graphs in some scenarios, like with Koa apps.

3.0.26

Changed

• 89db29f 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.

3.0.25

Added

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

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

Changed

• 33bce2e patch - Bump agent to b604345.

  • Add an exponential backoff to the retry sleep time to bind to the StatsD, NGINX and OpenTelemetry exporter ports. This gives the agent a longer time to connect to the ports if they become available within a 4 minute window.
  • Changes to the agent logger:
    • Logs from the agent and extension now use a more consistent format in logs for spans and transactions.
    • Logs that are for more internal use are moved to the trace log level and logs that are useful for debugging most support issues are moved to the debug log level. It should not be necessary to use log level 'trace' as often anymore. The 'debug' log level should be enough.
  • Add running_in_container to agent diagnose report, to be used primarily by the Python package as a way to detect if an app's host is a container or not.

  Bump agent to 8260fa1.

  • Add appsignal.sql_body magic span attribute for OpenTelemetry spans. When this attribute is detected, we store the value as the span/event body. This span is sanitized beforehand so it doesn't contain any sensitive data and helps to group events in our backend. When used in combination with the appsignal.body attribute, the new appsignal.sql_body attribute is leading.

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

• 285f89e patch - Print more path details in the diagnose CLI output. It will now print details like if a path exists, the ownership of a path and if it's writable or not to help debug issues locally.

• 3204cdd patch - Bump agent to 1dd2a18.

  • When adding an SQL body attribute via the extension, instead of truncating the body first and sanitising it later, sanitise it first and truncate it later. This prevents an issue where queries containing very big values result in truncated sanitisations.

Fixed

• 3367dfe patch - Fix a TypeScript types compatibility error upon app compilation when using the AppSignal Express error handler.

3.0.24

Changed

• 2eb17b0 patch - Bump agent to e8207c1.

  • Add memory_in_percentages and swap_in_percentages host metrics that represents metrics in percentages.
  • Ignore /snap/ disk mountpoints.
  • Fix issue with the open span count in logs being logged as a negative number.
  • Fix agent's TCP server getting stuck when two requests are made within the same fraction of a second.

• 037fcaa patch - Update Fastify dependency to make it compatible with Fastify 5

3.0.23

Changed

• aad5535 patch - Update OpenTelemetry dependencies to the latest versions.

3.0.22

Changed

• 4d96c96 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.

3.0.21

Changed

• 2c91c70 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.

Fixed

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