@appsignal/nodejs - npm Package Versions

3.3.2

Published on 2024-03-22.

Added

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

3.3.1

Published on 2024-03-21.

Changed

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

3.3.0

Added

• 7846141 minor - Add Node.js Apollo Gateway span mapping. This supports reporting OpenTelemetry Apollo Gateway spans as AppSignal spans, for the Node.js integration.

3.2.0

Published on 2024-03-06.

Added

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

Changed

• 335324a 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.
• 335324a 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.
• f99d4c5 patch - Update bundled trusted root certificates.

Fixed

• e5fa556 patch - Fix (sub)traces not being reported in their entirety when the OpenTelemetry exporter sends one trace in multiple export requests. This would be an issue for long running traces, that are exported in several requests.

3.1.0

Added

• 232ad25 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.

Changed

• 56fae90 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.
• 56fae90 patch - Fix an issue where queries containing a MySQL leading type indicator would only be partially sanitised.

Fixed

• c41d2f1 patch - Fix issue with boolean config options not being set to false properly for the agent configuration.

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.