Improving AppSignal, one deploy at a time.
Fix the sanitization of function arguments in SQL statements.
Before this release, SQL sanitization of function arguments stripped out parts of the SQL statement after the function argument list.
View the Node.js package v3.9.1 changelog for more information.
bullmq-otel package. These
were previously reported as uncategorised events named after the raw span,
because BullMQ describes its spans with its own attributes rather than the
OpenTelemetry messaging conventions. They are now named and categorised the same
way as events from the @appsignal/opentelemetry-instrumentation-bullmq package.@opentelemetry/api, warning about potential data loss, as older versions
fail to send data through global values configured by newer versions.
The warning names the versions and where they were loaded from.Update the bundled OpenTelemetry packages to their current versions. This resolves two reported vulnerabilities:
@opentelemetry/propagator-jaeger, which this integration
does not use but did bundle through @opentelemetry/sdk-node.@opentelemetry/core, which applies to the W3C baggage
propagation that this integration does use.Update the agent to handle high traffic apps. On high-traffic apps that would exceed the maximum accepted internal payload size, send data to the Push API more frequently.
Allow any 1.x version of @opentelemetry/api from 1.9.0 onwards. This prevents
an issue where npm installs a second copy of the package for AppSignal alone,
which can stop spans from being reported without any error.
@opentelemetry/instrumentation-mongodb package is version 0.74.0 or newer.
That version renames its spans to follow the stable database semantic
conventions, and events from it were being named unknown.mongodb as a result.queue tag. It was being reported
as the message_destination tag instead.b3 or x-b3-* headers, you can configure that
yourself by passing your own textMapPropagator to the OpenTelemetry SDK.View the Node.js package v3.9.0 changelog for more information.
Continue reporting non-disk host metrics when a mount is frozen.
Fix host-metrics leaking zombie [timeout] processes in Alpine linux containers.
Before this release AppSignal agent relied on a proper init process that reaps child processes killed by system timeout. Now the agent terminates and reaps unresponsive child processes in host-metrics collection and a subreaper is no longer required.
Ensure sendError ends its span even when the callback throws.
View the Node.js package v3.8.1 changelog for more information.
@opentelemetry/instrumentation-redis-4 package has been removed. Redis v4 instrumentation is now handled by @opentelemetry/instrumentation-redis, which supports both Redis v3 and v4.@prisma/instrumentation package has been updated from v6 to v7. The middleware config option has been removed, as Prisma dropped its middleware API in Prisma v5. Prisma's native tracing is now the only supported instrumentation method.View the Node.js package v3.8.0 changelog for more information.
Require parent spans on database and outgoing HTTP instrumentations that support it. When a database query is performed using the ioredis, pg, redis or mongoose libraries, or when an outgoing HTTP request is performed using the http module, a span will only be created if a trace has already been started in the current active context, that is, if the span to be created would have a parent.
This helps prevent database queries and outgoing HTTP requests happening in uninstrumented contexts from counting towards your requests quota.
View the Node.js package v3.7.4 changelog for more information.
pino logs without a msg attribute.View the Node.js package v3.7.3 changelog for more information.
@elastic/transport package in Node.js.Detect the log format automatically. We now detect if a log line is in the JSON, Logfmt, or plaintext format. No further config needed when calling our logger, like so:
const logger = Appsignal.logger("app");
logger.info("message");View the Node.js package v3.7.2 changelog for more information.
View the Node.js package v3.7.1 changelog for more information.
View the Node.js package v3.7.0 changelog for more information.
nginxPort configuration option. This configuration option can be used to customize the port on which the AppSignal integration exposes the NGINX metrics server.View the Node.js package v3.6.7 changelog for more information.
graphql or background namespaces.ignore_errors config option.mysql2 and pg instrumentations. This fixes an issue where queries performed using promises with mysql2@3.11.5 are not instrumented, as well as an issue where pg is not instrumented under certain bundlers and runtimes.View the Node.js package v3.6.6 changelog for more information.
View the Node.js package v3.6.5 changelog for more information.
View the Node.js package v3.6.4 changelog for more information.
View the Node.js package v3.6.3 changelog for more information.
Delay and eventually halt agent reboots by the extension.
The AppSignal extension is responsible for booting the AppSignal agent. If communication with the agent is lost, the extension is responsible for rebooting it.
In certain scenarios, such as when several processes with different AppSignal configurations are misconfigured to share the same working directory, the processes' extensions can enter a loop of rebooting and killing each others' agents. These short-lived agents may then attempt to repeatedly send pending payloads to AppSignal in quick succession.
This change causes the extension to delay each reboot of its agent by one additional second, and to no longer attempt to reboot the agent after the tenth reboot, slowing down and eventually breaking this loop.
View the Node.js package v3.6.2 changelog for more information.
View the Node.js package v3.6.1 changelog for more information.
db.query.text attribute and Redis queries in the db.operation.name attribute.setParams, setSessionData, setCustomData, etc from debug to warning./enriched endpoint on the agent's HTTP server, please migrate to the collector to continue using the beta. The collector has a much better implementation of this feature for the beta.View the Node.js package v3.6.0 changelog for more information.
INSERT INTO ... VALUES queries.View the Node.js package v3.5.5 changelog for more information.
Allow Pino transport to be used as a transport. Before, our Pino transport could only be used as a destination:
import pino from "pino";import pino from "pino";
import { Appsignal, AppsignalPinoTransport } from "@appsignal/nodejs";
pino(
AppsignalPinoTransport({
client: Appsignal.client,
group: "pino",
}),
);This meant it was not possible to log both to our transport and to another destination.
Now, it is also possible to use it as a Pino transport, with the transport Pino config option or the pino.transport() function:
import pino from "pino";
pino({
transport: {
target: "@appsignal/nodejs/pino",
options: {
group: "pino",
},
},
});It is no longer necessary to pass the AppSignal client to the Pino transport. AppSignal must be active for the Pino transport to work.
By enabling its use as a transport, it is now possible to use it alongside other transports:
pino({
transport: {
targets: [
// Send logs to AppSignal...
{ target: "@appsignal/nodejs/pino" },
// ... and to standard output!
{ target: "pino/file" },
],
},
});View the Node.js package v3.5.4 changelog for more information.
CONTAINER_VERSION system environment variable is present, it will use used to set the revision config option automatically. Overwrite it's value by configuring the revision config option for your application.View the Node.js package v3.5.3 changelog for more information.
Free for 30 days. No credit card. Two-minute install.
Need help or have a feature request? Talk to a real engineer. Not a bot, not a ticket queue.
AppSignal is built by a small, dedicated team spread across the world. We love stroopwafels. If you do too, let us know. We might send you some.
