3.4.1

Published on 2024-04-24.

Fixed

• 7e6f79d patch - Fix an issue where internal Next.js traces were not correctly ignored in certain circumstances.

3.4.0

Published on 2024-04-22.

Added

• 81bd0a9 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.

• 9985d08 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.

Changed

• 6224018 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)
  })
  

3.3.4

Published on 2024-04-19.

Fixed

• b344156 patch - Fix incorrect HTTP methods like render or getServerSideProps in Next.js 14 performance samples.

3.3.3

Published on 2024-04-17.

Fixed

• 80c7dbf patch - Fix UNKNOWN method in Next.js 14 performance traces.

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.