CI environment variable was present, AppSignal for Phoenix would break during installation unless a separate environment variable was also present.View the Elixir for Phoenix package v2.8.1 changelog for more information.
Report LiveComponent traces and events separately from LiveView traces and events.
Traces in AppSignal representing updates and event handlers in components will no longer be represented as calls to the view in which the component is mounted, and their events will be part of the live_component group.
This makes it possible to obtain performance measurements for each component individually, instead of grouped by the view that mounts the component.
Group samples for calls to handle_event/3 in LiveView and LiveComponent by the event that is being handled.
View the Elixir for Phoenix package v2.8.0 changelog for more information.
enable_host_metrics configuration option default from true to false. Host metrics are now disabled by default and must be explicitly enabled in the configuration.This release can be installed through our collector packages and Docker image.
get_triggers MCP Tool. This tool exposes all the anomaly detection triggers and is in preparation for the create/update trigger tool.get_app_resources MCP Tool. This tool exposes multiple application resources such as users, namespaces, and dashboards. It will be the home of application resources that do not need any additional filtering.get_users MCP tool in favor of get_app_resources.get_namespaces MCP tool in favor of get_app_resources.This release can be installed through our collector packages and Docker image.
pino logs without a msg attribute.View the Node.js package v3.7.3 changelog for more information.
config/application.rb or one of the environments in config/environments/.ActionController::BadRequest occurred and the error message contained the entire file upload, this would grow the appsignal.log file quickly if the error happens often. Internal log messages are now truncated by default.View the Ruby gem v4.7.5 changelog for more information.
openedAt value being null.@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.
FastAPI and popular database libraries.View the Python package v1.6.1 changelog for more information.
View the MCP Server v1.0.0 changelog for more information.
Detect the log format automatically. We now detect if a log line is in the JSON, Logfmt or plaintext formats. No further config needed when calling our logger, like so:
Appsignal.Logger.info("group", "message")
View the Elixir package v2.15.11 changelog for more information.
Support logging through the external collector experimental feature. When the collector_endpoint configuration option is provided, the OpenTelemetry stack will be automatically configured to instrument logs.
The logging module will be automatically instrumented, such that log lines emitted through loggers that propagate to the root logger will be automatically sent to AppSignal. To disable this behaviour, add "logging" to the disable_default_instrumentations configuration option list.
Support usage with external collector. When the collector_endpoint configuration option is provided, instead of booting up the AppSignal agent bundled with the application, the OpenTelemetry stack will be configured to send data to the given collector.
This is an experimental feature. The following functionality is not currently supported when using the collector:
Some configuration options are only supported when using the agent or when using the collector. A warning will be emitted if a configuration option that is only supported by one is set while using the other.
View the Python package v1.6.0 changelog for more information.
Handle transactions without errors in CodeOwnership integration. AppSignal will not emit an error log line if a transaction has no error.
Thanks @fatkodima for your contribution!
View the Ruby gem v4.7.4 changelog for more information.
Detect the log format automatically. We now detect if a log line is in the JSON, Logfmt or plaintext formats. No further config needed when calling our logger, like so:
logger = Appsignal::Logger.new("gruop") logger.info("message")
Handle unowned files in CodeOwnership gem integration. AppSignal will not emit an error log line if no Team can be found for a backtrace.
Thanks @fatkodima for your contribution!
View the Ruby gem v4.7.3 changelog for more information.
Allow functions as backtrace matchers. Alongside regular expressions, you can also provide custom functions to match and replace paths in the backtrace:
const appsignal = new Appsignal({ // ... matchBacktracePaths: [ (path) => { if (path.indexOf("/bundle/") !== -1) { return "bundle.js"; } }, ], });
The function must take a backtrace line path as an argument. When the function returns a non-empty string, the string will be used as the path for that backtrace line. Otherwise, the path will be left unchanged.
Fix matching on backtrace paths containing spaces.
When using matchBacktracePaths, when a backtrace line path contains a space, it will now match correctly against the whole path.
View the AppSignal JavaScript javascript v1.6.1 changelog for more information.
Users can now copy the sample backtrace line with a click of a button. (This feature was requested in our Discord channel).
BSON::ObjectId('.)AppSignal offers a 30-day free trial, no credit card is required. All features are available in all plans. Start monitoring your application in just a few clicks!