@appsignal/nodejs
3.9.5 · 11 Nov 2026MIT24.2k / weekRepositoryHomepagenpmAtom feed
133 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 3.x · latest line
3.0.23
10 Oct 2023Patch - Update OpenTelemetry dependencies to the latest versions.
3.0.22
6 Oct 2023Patch - Report express route parameters. If a route is defined like
/user/:id, theidparameter will be reported from now on in the "Parameters" box on AppSignal.com.
3.0.21
4 Sep 2023Patch - 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.
Patch - Fix a misleading platform mismatch error when the AppSignal extension fails to load on musl-based systems.
3.0.20
30 Aug 2023Patch - Bump agent to 6133900.
3.0.19
25 Aug 2023Patch - Add the
hostRoleconfig option. This config option can be set per host to generate some metrics automatically per host and possibly do things like grouping in the future.
3.0.17
31 Jul 2023Patch - Report total CPU usage host metric for VMs. This change adds another
statetag value on thecpumetric calledtotal_usage, which reports the VM's total CPU usage in percentages.Patch - Add the --config flag to diagnose command to specify a custom path for your AppSignal configuration file to be taken into account when running the diagnose of your AppSignal installation.
Patch - Bump agent to 6bec691.
3.0.16
21 Jul 2023Patch - Allow configuration of the agent's StatsD server port through the
statsdPortoption.Patch - Use
RENDER_GIT_COMMITenvironment variable as revision if no revision is specified.Patch - Support Prisma 5
Added
Patch - Allow configuration of the agent's StatsD server port through the
statsdPortoption.Patch - Use
RENDER_GIT_COMMITenvironment variable as revision if no revision is specified.Patch - Support Prisma 5
Patch - Allow configuration of the agent's TCP and UDP servers using the
bindAddressconfig option. This is by default set to127.0.0.1, which only makes it accessible from the same host. If you want it to be accessible from other machines, use0.0.0.0or a specific IP address.
Changed
Patch - Bump agent to fd8ee9e.
Rely on APPSIGNAL_RUNNING_IN_CONTAINER config option value before other environment factors to determine if the app is running in a container.
Fix container detection for hosts running Docker itself.
Add APPSIGNAL_STATSD_PORT config option.
Patch - Bump agent to 32590eb.
Only ignore disk metrics that start with "loop", not all mounted disks that end with a number to report metrics for more disks.
Fixed
Patch - Remove agent download file after extraction. This save a couple megabytes of space that are no longer needed when the agent and extension have been extracted from the downloaded
.tar.gzfile, reducing the overall app size.
3.0.15
26 May 2023- Deprecated
Patch - Add deprecation warning to instrumentationsLoaded helper
Patch - The diagnose CLI command now reports on the presence of the
appsignal.cjsfile.Patch - Load the AppSignal app configuration file when running the diagnose to include the configuration in the diagnose report.
Added
Patch - The diagnose CLI command now reports on the presence of the
appsignal.cjsfile.Patch - Load the AppSignal app configuration file when running the diagnose to include the configuration in the diagnose report.
Changed
Patch - Update bundled trusted root certificates.
Deprecated
- Deprecated
Patch - Add deprecation warning to instrumentationsLoaded helper
3.0.13
14 Apr 2023Patch - Update OpenTelemetry dependencies to the latest versions, providing many improvements and bug fixes.
3.0.12
22 Mar 2023Patch - Fix grouping for Prisma queries.
3.0.10
14 Feb 2023Patch - Support Winston child logger groups when using the Winston transport
When using the Winston transport for our logging feature, the child loggers with an assigned group will send the group to AppSignal when logging messages.
3.0.8
7 Feb 2023Patch - Add NGINX metrics support. See our documentation for details.
3.0.7
1 Feb 2023- Breaking
Patch - Remove fs instrumentation by default. It's causing issues on some installations. It can be manually added as described in our fs module docs.
3.0.4
20 Jan 2023Patch - Add OpenTelemetry SDK initialization helper function
The OpenTelemetry instrumentations are loaded async, this is OK when users rely on automatic instrumentations, but for custom instrumentations it might cause spans not to be reported. There's a new helper function that contains the instrumentations registration that can be awaited for resolution before running any custom instrumentations.
3.0.3
16 Jan 2023Patch - Track the Operating System release/distro in the diagnose report. This helps us with debugging what exact version of Linux an app is running on, for example.
Patch - Report request parameters for restify apps. This is reported automatically. You can disable parameter reporting with the AppSignal
sendParams: falseconfiguration option.Patch - Add Winston transport support for the logging feature.
Added
Patch - Track the Operating System release/distro in the diagnose report. This helps us with debugging what exact version of Linux an app is running on, for example.
Patch - Report request parameters for restify apps. This is reported automatically. You can disable parameter reporting with the AppSignal
sendParams: falseconfiguration option.Patch - Add Winston transport support for the logging feature.
Changed
Patch - Log an error for appsignal.tracer function calls. Inform the user to update instrumentation code to be compatible with the latest version of our package.
Fixed
Patch - Prevent creating fs-only samples by only creating an fs span if there is a parent span present.
3.0.2
22 Dec 2022Patch - Add support for the restify package.
Patch - Remove client IP from HTTP traces
3.0.1
24 Nov 2022Patch - Support for Fastify request parameters. Request parameters (query, body) are now added to the HTTP spans when using Fastify.
Patch - Add Knex.js instrumentation. We will now auto instrument database queries made with Knex.js.
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
21 Oct 2022Contact us for support
Add support for express package
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/nextjsand@appsignal/apollo-servershould 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 for help.
Contact us for 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.
- 2.x
2.4.2
8 Jun 2022Patch - Do not restore closed spans from within the
withSpanhelper. If a previously active span gets closed whilewithSpanhas another span as currently active, do not restore the closed span when the callback has finished.Patch - Do not restore root span after
withSpancallback has finished. Previously the root span was restored to the original root span before thewithSpanhelper was called. This has been changed, because thewithSpanhelper is only about changing the active span, not the root span. If a new root span has been set within awithSpanhelper callback, the root span will no longer be restored. We recommend setting a new root span before callingwithSpaninstead.const rootSpan = tracer.rootSpan() const span = tracer.createSpan(...) tracer.withSpan(span, function(span) { tracer.createRootSpan(...) }); // No longer match rootSpan != tracer.rootSpan()Patch - Only allow open root spans to be set as root. This avoids closed root spans to be reused in child contexts.
Changed
Patch - Do not restore closed spans from within the
withSpanhelper. If a previously active span gets closed whilewithSpanhas another span as currently active, do not restore the closed span when the callback has finished.Patch - Do not restore root span after
withSpancallback has finished. Previously the root span was restored to the original root span before thewithSpanhelper was called. This has been changed, because thewithSpanhelper is only about changing the active span, not the root span. If a new root span has been set within awithSpanhelper callback, the root span will no longer be restored. We recommend setting a new root span before callingwithSpaninstead.const rootSpan = tracer.rootSpan() const span = tracer.createSpan(...) tracer.withSpan(span, function(span) { tracer.createRootSpan(...) }); // No longer match rootSpan != tracer.rootSpan()
Fixed
Patch - Only allow open root spans to be set as root. This avoids closed root spans to be reused in child contexts.
Patch - Don't return closed spans in
withSpanhelper. If a closed span was given to thewitSpanhelper 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 aNoopSpan.Patch - Add
@opentelemetry/sdk-trace-basepackage runtime dependency. Our OpenTelemetry SpanProcessor needs this package at runtime, not just at compile time.
2.4.1
7 Jun 2022Patch - Do not instrument HTTP requests to the default socket.io path. This works around an issue where our HTTP instrumentation breaks socket.io's server side, causing the client side to get stuck in a connection loop.
Patch - Fix removing event listeners from wrapped event emitters. When using
tracer.wrapEmitterto wrap an event emitter, it was not possible to remove any listeners that were added after the event emitter was wrapped.
2.4.0
2 Jun 2022Minor - Add OpenTelemetry span processor for the mysql and mysql2 packages. These are experimental integrations and require additional set up to integrate with OpenTelemetry.
Patch - Add config options for disabling default instrumentation like HTTP, HTTPS, PostgreSQL (pg package) and Redis (node-redis package).
The following configuration options have been added:
By default these configuration options are set to
true, which means the instrumentation is active by default. If you want to disable one of these instrumentations, configure it by setting the configuration option tofalse.// appsignal.js // Brief example, see our docs for a full example const appsignal = new Appsignal({ instrumentRedis: false // Disables the node-redis package instrumentation });Patch - Add OpenTelemetry node-redis and ioredis query sanitizers. We recommend using these sanitizers to ensure no sensitive data is sent in query statements. Add the sanitizer to the
dbStatementSerializerconfig as demonstrated below.// tracing.js // Add the RedisDbStatementSerializer import const { RedisDbStatementSerializer } = require("@appsignal/nodejs"); const { RedisInstrumentation } = require("@opentelemetry/instrumentation-redis"); const sdk = new opentelemetry.NodeSDK({ instrumentations: [ new RedisInstrumentation({ // Configure the AppSignal RedisDbStatementSerializer to sanitize queries dbStatementSerializer: RedisDbStatementSerializer }) ] });The same can be done for the ioredis instrumentation:
// tracing.js // Add the IORedisDbStatementSerializer import const { IORedisDbStatementSerializer } = require('@appsignal/nodejs'); const { IORedisInstrumentation } = require('@opentelemetry/instrumentation-ioredis'); const sdk = new opentelemetry.NodeSDK({ instrumentations: [ // Add the IORedisInstrumentation new IORedisInstrumentation({ // Configure the AppSignal IORedisDbStatementSerializer to sanitize queries dbStatementSerializer: IORedisDbStatementSerializer }) ] });
Added
Minor - Add OpenTelemetry span processor for the mysql and mysql2 packages. These are experimental integrations and require additional set up to integrate with OpenTelemetry.
Patch - Add config options for disabling default instrumentation like HTTP, HTTPS, PostgreSQL (pg package) and Redis (node-redis package).
The following configuration options have been added:
instrumentHttpinstrumentPginstrumentRedis
By default these configuration options are set to
true, which means the instrumentation is active by default. If you want to disable one of these instrumentations, configure it by setting the configuration option tofalse.// appsignal.js // Brief example, see our docs for a full example const appsignal = new Appsignal({ instrumentRedis: false // Disables the node-redis package instrumentation });Patch - Add OpenTelemetry node-redis and ioredis query sanitizers. We recommend using these sanitizers to ensure no sensitive data is sent in query statements. Add the sanitizer to the
dbStatementSerializerconfig as demonstrated below.// tracing.js // Add the RedisDbStatementSerializer import const { RedisDbStatementSerializer } = require("@appsignal/nodejs"); const { RedisInstrumentation } = require("@opentelemetry/instrumentation-redis"); const sdk = new opentelemetry.NodeSDK({ instrumentations: [ new RedisInstrumentation({ // Configure the AppSignal RedisDbStatementSerializer to sanitize queries dbStatementSerializer: RedisDbStatementSerializer }) ] });The same can be done for the ioredis instrumentation:
// tracing.js // Add the IORedisDbStatementSerializer import const { IORedisDbStatementSerializer } = require('@appsignal/nodejs'); const { IORedisInstrumentation } = require('@opentelemetry/instrumentation-ioredis'); const sdk = new opentelemetry.NodeSDK({ instrumentations: [ // Add the IORedisInstrumentation new IORedisInstrumentation({ // Configure the AppSignal IORedisDbStatementSerializer to sanitize queries dbStatementSerializer: IORedisDbStatementSerializer }) ] });
Changed
Patch - Use the OpenTelemetry SpanProcessor interface to build our own SpanProcessor. We previously copied the SpanProcessor code into our package, but instead we now use the OpenTelemetry interface directly. This should make our processor match the expected type better.
Patch - Bump agent to v-0b43802.
Add redis and ioredis OpenTelemetry instrumentation support.
Patch - Bump agent to v-1a8ac46
Support OpenTelemetry root span import.
Support OpenTelemetry HTTP instrumentation.
Support OpenTelemetry Express instrumentation.
Fixed
Patch - Fix the
ScopeManager.active()function returning closed spans.Patch - Do not transfer closed spans for new async contexts in the ScopeManager. Rather than relying on
ScopeManager.active()andScopeManager.root()to make sure the span is not already closed, also make sure it's not closed when transferring spans around between async contexts.
2.3.6
11 May 2022Patch - Add the
createRootSpanfunction to the Tracer to allow explicit creation of RootSpans even if another RootSpan already exists and is tracked as the current RootSpan. Make sure to not forget about the previous RootSpan, and close it as well at some point when using this function.
2.3.5
29 Apr 2022Patch - Use the Node.js performance module as high-resolution timer for span creation and close times. This provides more accurate times and improves compatibility with other systems in the future.
Patch - When instrumenting an outgoing HTTP request, read the
hostproperty from the request options if thehostnameproperty is not present. This fixes a bug where outgoing HTTP request hosts would be shown ashttp://localhost.Patch - Fix error on Microsoft Windows machines on install. The AppSignal extension still won't install on Windows, but now it won't cause an error while checking a development mode condition if it should build the TypeScript package.
2.3.4
11 Apr 2022Patch - Update node-gyp to major version
9.0.0. This drops compatibility with Python 2.7 for the extension install, but it makes it compatible with the latest Python 3 version, which should be more accessible to users going forward.Patch - Ensure the root span is preserved across scopes. Due to a bug in the scope management logic, calling
tracer.withSpancould cause the root span for a given scope to be forgotten.
2.3.3
11 Apr 2022Patch - Log messages are now sent through a new centralized logger that writes to
/tmp/appsignal.logby default. A warning is printed to STDERR when the default or provided logPath is not accessible, and the Logger automatically falls back to STDOUT. Use config optionlog: stdoutto log AppSignal messages to STDOUT instead.Patch - Bump agent to v-bbc830a
Patch - Bump agent to v-f57e6cb
Added
Patch - Log messages are now sent through a new centralized logger that writes to
/tmp/appsignal.logby default. A warning is printed to STDERR when the default or provided logPath is not accessible, and the Logger automatically falls back to STDOUT. Use config optionlog: stdoutto log AppSignal messages to STDOUT instead.
Changed
Patch - Bump agent to v-bbc830a
Support batched statsd messages
Set start times for spans with traceparents
Check duration in transactions for negative and too high values
Patch - Bump agent to v-f57e6cb
Enable process metrics on Heroku and Dokku
Fixed
Patch - Allow nested values in
Span.setSampleData. This change also allows values other than strings, integers and booleans to be passed as values within the sample data objects. Note that not all sample data keys allow nested values to be passed.Patch - Follow redirects when downloading the AppSignal agent. This fixes an issue where the redirect page would be downloaded instead of the agent, causing the agent installation to fail.
Patch - Fix an issue where the AppSignal extension would throw an error when an object containing a non-integer number is sent to it. This would be triggered when calling
setSampleDatawith an object containing a non-integer number, or when the values for a metric's tags are non-integer numbers.
2.3.2
15 Feb 2022- Breaking
Patch - Remove the private function
Span.toJSON. This wasn't previously marked as private, but it was. - Breaking
Patch - Do not ship the extension install script test files in the published package. Reduces the package size a tiny bit.
- Breaking
Patch - Remove the unused experimental module.
Changed
Patch - Update the expected Span type in ScopeManager to
Spanfrom the@appsignal/nodejspackage, rather than theNodeSpanfrom the@appsignal/typespackage. The type definition is the same, but now all Span types used by the Node.js integration are defined in the@appsigna/nodejspackage.Patch - Improve memory usage when extension is not initialized. It will no longer initialize a new empty Tracer object when the extension is not loaded or AppSignal is not active.
Patch - Update @appsignal/types dependency to 3.0.0.
Removed
- Breaking
Patch - Remove the private function
Span.toJSON. This wasn't previously marked as private, but it was. - Breaking
Patch - Do not ship the extension install script test files in the published package. Reduces the package size a tiny bit.
- Breaking
Patch - Remove the unused experimental module.
Fixed
Patch - Show errors in loading the extension when the
@appsignal/nodejsmodule is required.Patch - The minutely probes are now stopped when
Appsignal.stop()is called. This fixes an issue where Jest tests would warn about asynchronous operations that remain pending after the tests.
2.3.1
26 Jan 2022Patch - The supported Redis version is now locked to 3.x.x. This will prevent app startup failures for users with Redis 4.x.x.
2.3.0
20 Jan 2022Patch - Implement unregister method for probes. You can now call the
probes.unregister(name)method to unregister a probe by name.Minor - The extension package (@appsignal/nodejs-ext) is no longer a separated dependency. The extension is part of the @appsignal/nodejs package now.
Patch - Update install report path location. The "nodejs" package now stores the install report in its own package path, with the rest of the extension files. This makes it easier to access by the diagnose report.
Added
Patch - Implement unregister method for probes. You can now call the
probes.unregister(name)method to unregister a probe by name.
Changed
Minor - The extension package (@appsignal/nodejs-ext) is no longer a separated dependency. The extension is part of the @appsignal/nodejs package now.
Patch - Update install report path location. The "nodejs" package now stores the install report in its own package path, with the rest of the extension files. This makes it easier to access by the diagnose report.
Patch - Improve the reporting of extension loading state in the diagnose report. Previously it would only report it as loaded when it was also running.
Patch - Change the way the extension is started. Previously it was started on initialization of the extension class (if the config was active), but now it's started by the client class.
Patch - Remove the
osandcpufields from thepackage.json. This will prevent installations from failing on unlisted CPU architectures and Operating Systems. Our extension installer script will do this check instead. The package should not fail to install when it encounters an unsupported CPU architecture or Operating System.Patch - Update package metadata to specify the package repository.
Fixed
Patch - Add a hostname tag to V8 probe metrics. This fixes an issue where metrics' values would be overriden between different hosts.
Patch - Setting
enableMinutelyProbestofalsenow disables the minutely probes system. Custom probes will not be called when the minutely probes are disabled. In addition, theAPPSIGNAL_ENABLE_MINUTELY_PROBESenvironment variable can now be used to enable or disable the minutely probes.Before this change, setting
enableMinutelyProbestofalsewould not register the default Node.js heap statistics minutely probe, but custom probes would still be called. To opt in for the previous behaviour, disabling only the Node.js heap statistics minutely probe without disabling custom probes, you can use theprobes.unregister()method to unregister the default probe:const probes = appsignal.metrics().probes(); probes.unregister("v8_stats");Patch - Use the APPSIGNAL_ACTIVE environment variable to determine whether AppSignal is active.
Patch - Fix the extension function fallbacks on installation failure. When the extension fails to install and calls are made to the not loaded functions, it will no longer throw an error.
2.2.10
10 Jan 2022Patch - Update @appsignal/nodejs-ext dependency to 2.0.7.
2.2.9
10 Jan 2022Patch - The
sendSessionDataconfig option is now available. When set tofalse, it prevents the integration from sending session data to AppSignal.
2.2.8
4 Jan 2022Patch - The
caFilePathconfig option now works for diagnose script external requests.Patch - Add helper to access the globally stored AppSignal client.
Patch - The
sendParamsconfig option is now available. When set tofalse, it prevents the integration from sending request params to AppSignal.
Added
Patch - The
caFilePathconfig option now works for diagnose script external requests.Patch - Add helper to access the globally stored AppSignal client.
Patch - The
sendParamsconfig option is now available. When set tofalse, it prevents the integration from sending request params to AppSignal.Patch - Handle request errors in the internal HTTP transmitter used by diagnose tool and Push API key validator.
Changed
Patch - The extension is now responsible of determining if the process is running in a container. This check was previously made by the Node.js integration code.
Patch - Update @appsignal/nodejs-ext dependency to 2.0.6.
2.2.7
9 Dec 2021Patch - Fix debug and transaction_debug_mode log options. If set, previously the log_level would remain "info", since version 2.2.6.
2.2.6
8 Dec 2021- Deprecated
Patch - Deprecate "debug" and "transactionDebugMode" config options in favor of the new "logLevel" config option.
Patch - Add
send_environment_metadataconfig option to configure the environment metadata collection. For more information, see our environment metadata docs.Patch - Add "logLevel" config option. This new option allows you to select the type of messages AppSignal's logger will log and up. The "debug" option will log all "debug", "info", "warning" and "error" log messages. The default value is: "info"
The allowed values are:
Added
Patch - Add
send_environment_metadataconfig option to configure the environment metadata collection. For more information, see our environment metadata docs.Patch - Add "logLevel" config option. This new option allows you to select the type of messages AppSignal's logger will log and up. The "debug" option will log all "debug", "info", "warning" and "error" log messages. The default value is: "info"
The allowed values are:
error
warning
info
debug
Changed
Patch - Update @appsignal/nodejs-ext dependency to 2.0.5.
Deprecated
- Deprecated
Patch - Deprecate "debug" and "transactionDebugMode" config options in favor of the new "logLevel" config option.
2.2.5
24 Nov 2021Patch - Send the diagnose report with correct query parameters to help link the report to the app and organization on AppSignal.com.
Patch - The AppSignal config is not considered valid anymore when the apiKey config option is not set.
Patch - Print the extension installation dependencies and flags in the diagnose report output.
Patch - Send the diagnose report with correct query parameters to help link the report to the app and organization on AppSignal.com.
Patch - The AppSignal config is not considered valid anymore when the apiKey config option is not set.
Patch - Print the extension installation dependencies and flags in the diagnose report output.
Patch - Add information about the sources of each configuration value in the output of the diagnose report.
Patch - Include the sources of each configuration value in the diagnose report that is sent to AppSignal.com.
Patch - Standardize diagnose validation failure message. Explain the diagnose request failed and why.
Patch - Diagnose report config opts are now printed in camel case format, matching how the configuration options are provided to the
AppsignalobjectPatch - Print deprecation message when passing a filename to
logPathconfig option. This was already deprecated. Now it also prints a warning message on app start.Patch - The AppSignal client is stored on the global object as to make access easier for AppSignal developers.
Patch - Fix TypeScript compatibility for global object augmentation.
Patch - Add
filterParametersandfilterSessionDataoptions to filter out specific parameter keys or session data keys. Previously only the (undocumented)filterDataKeysconfig option was available to filter out all kinds of sample data.Patch - Rename the
apiKeyoption topushApiKeyto match other AppSignal integrations. IfapiKeyis set it will automatically setpushApiKey. TheapiKeyoption will be removed in the next major version of this package.Patch - Default log output to app STDOUT on Heroku dyno's. This makes the AppSignal logs available in the Heroku app's logs.
Patch - The
requestHeadersconfig option is now available. An allow list that gives the ability to define which request headers you want to be shown in sample detail views. The default is a list of common headers that do not include personal identifiable information. Read more about request headers on our documentation website.Patch - Fix the diagnose's
log_dir_pathpath check. It now always checks the actual log file's parent directory, rather than the configured path. These two values may differ as the package does a permission check to see if thelogPathis writable or not.Patch - Fix writable check for paths in the diagnose report. Previously it only checked if a path was readable, not writable.
Patch - Check if the fallback log directory can be written to and print a warning if no log can be written there.
Patch - The logPath config option only allows writable paths. If the provided path is not writable, it'll automatically change to the Operating System's temporary directory (
/tmp).Patch - Update @appsignal/nodejs-ext dependency to 2.0.4.
2.2.4
4 Nov 2021Patch - All user-configurable options are now printed in the diagnose report.
Check the list of available options.
2.2.3
3 Nov 2021Patch - Fix diagnose report recognition when sent to the server. It was sent without an
api_keyparameter, which resulted in apps not being linked to the parent organization based on the known Push API key.Patch - Transmit the path file modes in the diagnose report as an octal number. Previously it send values like
33188and now it transmits100644, which is a bit more human readable.Patch - Update @appsignal/nodejs-ext dependency to 2.0.3.
2.2.2
27 Oct 2021Patch - Fix sending the agent diagnose report with all reports. It was sent, but with the wrong key, which made our server side validator report it as missing.
Patch - Print agent diagnose report in diagnose CLI output.
Patch - Add new config option to enable/disable StatsD server in the AppSignal agent. This new config option is called
enableStatsdand is set tofalseby default. If set totrue, the AppSignal agent will start a StatsD server on port 8125 on the host.
2.2.1
25 Oct 2021Patch - The diagnose report will report parsing errors on reading or parsing the installation report. Previously, a missing installation report file would crash the diagnose tool.
Patch - Print String values in the diagnose report surrounded by quotes. Makes it more clear that it's a String value and not a label we print.
Patch - Correct the diagnose host section indenting, it was indented one level too far to the right when printed.
2.2.0
13 Oct 2021Minor - Remove interface usage from @appsignal/types
All Node.js-specific interfaces from the types package are now defined inside the nodejs core package. There's still a dependency from types package for common types as Func, HashMap, and HasMapValue.
With this change, we keep taking advantage of interfaces, but now they're defined in a place where they're used.
2.1.1
11 Oct 2021Patch - Show correct language version in diagnose's extension installation section. It did not show the language version used during install, but the current one used to run the diagnose tool.
Patch - Rename the
Agentmodule toExtensionto fit better with our naming standards.Patch - Fix diagnose installation status reporting. It previously always reported "success", but will now also print failures.
Patch - Show correct language version in diagnose's extension installation section. It did not show the language version used during install, but the current one used to run the diagnose tool.
Patch - Rename the
Agentmodule toExtensionto fit better with our naming standards.Patch - Fix diagnose installation status reporting. It previously always reported "success", but will now also print failures.
Patch - Update @appsignal/nodejs-ext dependency to 2.0.2.
2.1.0
5 Oct 2021Minor - Add rootSpan and setError helpers.
Errors added to child spans are ignored by the agent. Now the rootSpan is always accessible from the tracer object as well as setError. The setError function allows to track errors on demand and they will be always attached to the main current span, so they don't get ignored by the agent.
Patch - Bug fix in custom timestamp calculation
Patch - Deprecate the addError function on the Span interface. Instead use the Tracer's
setErrorfunction to set the error on the root span.
Minor - Add rootSpan and setError helpers.
Errors added to child spans are ignored by the agent. Now the rootSpan is always accessible from the tracer object as well as setError. The setError function allows to track errors on demand and they will be always attached to the main current span, so they don't get ignored by the agent.
Patch - Bug fix in custom timestamp calculation
Patch - Deprecate the addError function on the Span interface. Instead use the Tracer's
setErrorfunction to set the error on the root span.Patch - Add sendError helper to Tracer object.
This new helper allows you to track an error separately from any other span inside the current context. Or use it to set up in your own error handling to report errors in a catch-statement if no performance monitoring is needed.
try { // Do complex stuff } catch (error) { appsignal.tracer().sendError(error, span => { span.setName("daily.task"); // Set a recognizable action name span.set("user_id", user_id); // Set custom tags }); }Patch - Update @appsignal/nodejs-ext dependency to 2.0.1.
2.0.0
19 Aug 2021Major - Drop support for Node.js 10 and 11. These are unmaintained versions of Node.js.
Patch - Update @appsignal/nodejs-ext dependency to 2.0.0.
- 1.x
1.3.2
12 Aug 2021Patch - Update @appsignal/nodejs-ext dependency to 1.2.9.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.