New chart type: Number chart

Added a new chart type for dashboards: the number chart. The number chart displays a number on the dashboard instead of a line graph. Useful when a single value gives enough information at a glance.

The chart supports multiple ways of calculating the metric data for the timeframe selected, such as:

• Maximum value: Show the highest metric value.
• Minimum value: Show the lowest metric value.
• Average value: Show the average of the metric values.
• Total value: Show the combined value of the metric values.
• First value: Show the first metric value.
• Last value: Show the last metric value.

To add a number chart, go to your application in AppSignal, create or open a dashboard, click "Add chart", and select "Number" in the sidebar.

Allow app-level push API keys

Changed

• Allow the use of app-level push API keys. When an app-level push API key is used, the resource attributes for the name and environment should not be specified. These resource attributes are now optional, although the use of one requires the other.

• Make most resource attributes optional. Allow for the resource attributes pertaining the revision, the hostname, the language integration and the application path to not be present. This allows the AppSignal collector to more easily ingest data from arbitrary OpenTelemetry sources.

  Note that usage of these resource attributes is still recommended. Traces sent without these attributes may be tagged with the wrong hostname or revision, or have their error backtraces parsed incorrectly.

This release can be installed through our collector packages and Docker image.

Disable `ActiveSupport::EventReporter` logs

Changed

• Disable the enable_active_support_event_log_reporter configuration option by default.

View the Ruby gem v4.8.1 changelog for more information.

Ruby gem v4.8.0

Added

• Report events from Rails 8.1's Structured Event Reporting (ActiveSupport::EventReporter) as logs.

Fixed

• Fix ActiveSupport::Notifications event instrumentation on Rails 8.1 when no listeners are registered.

View the Ruby gem v4.8.0 changelog for more information.

Limit required headers for Heroku Telemetry drain

Changed

• Use heroku.release.version resource attribute as a fallback value for revision for Heroku Fir applications.

This release can be installed through our collector packages and Docker image.

Elixir package v2.16.0

Changed

• Disable the error backend by default

  With new ways of instrumenting errors added, the error backend is unneeded in most setups. Disable it by default to make it opt-in.

View the Elixir package v2.16.0 changelog for more information.

Collector v0.9.0

Added

• Support first-party add-on metrics from Heroku Fir generation apps.
• Support Heroku Fir host metrics.

This release can be installed through our collector packages and Docker image.

Fix issue when running on CI

Fixed

• Fix issue when running AppSignal for Phoenix in CI. When the 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.

LiveComponent improvements

Added

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

Disable collector host metrics by default

Changed

• Change the 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.

Markdown support for status pages and MCP updates

Added

• Add support for markdown on the AppSignal status pages. You can now use markdown in the main description, and status updates.

  

• Add get_triggers MCP Tool. This tool exposes all the anomaly detection triggers and is in preparation for the create/update trigger tool.
• Add 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.

Removed

• Remove get_users MCP tool in favor of get_app_resources.
• Remove get_namespaces MCP tool in favor of get_app_resources.

Fix payload authentication issue

Fixed

• Fix an issue where the collector would stop transmitting data after a payload's authentication was rejected.

This release can be installed through our collector packages and Docker image.

Free plan and timezone selection for exported charts

Added

• Add free plan (See our blog post.)
• Add ability to select a timezone when exporting charts to SVG/PNG (defaults to UTC)

Fixed

• Fix bug on the notifiers page to use the correct environment selector in form.

Handle `pino` logs with no message

Fixed

• Handle pino logs without a msg attribute.

View the Node.js package v3.7.3 changelog for more information.

Improvements to our internal logger

Fixed

• Fix an issue with loggers not supporting a formatter on Rails boot. This will prevent the AppSignal logger config from running into an error if the logger configuration is added to config/application.rb or one of the environments in config/environments/.
• Do not log long (error) messages to the internal AppSignal log. If an error like 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.

UI Fixes and Search Improvements

Fixed

• Add a fix for a minor UI bug in the PHP and Go OpenTelemetry app installation flows.
• Ensure that in the UI, we handle the alert openedAt value being null.
• Remove the leading and trailing whitespace when submitting a search query.

Auto detect log format, support ElasticSearch spans

Added

• Add a log format option for autodetection the log format.
• Add support for native OpenTelemetry spans from @elastic/transport package in Node.js.

Changed

• 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:

  Shell

  const logger = Appsignal.logger("app");
  logger.info("message");
  

Fixed

• Fix 'unknown' events being reported for some HTTP routes.

View the Node.js package v3.7.2 changelog for more information.

Logbook Icon Fix and GitHub Integration Pagination

Added

• Add the missing icon to the logbook integration create item

Changed

• GitHub integration now fetches all repositories across multiple pages

Fix OpenTelemetry DB span parsing

Fixed

• Fix parsing of OpenTelemetry spans emitted by FastAPI and popular database libraries.

View the Python package v1.6.1 changelog for more information.

MCP Server v1.0.0

Added

• The first release of the AppSignal MCP Server as a npm package.

View the MCP Server v1.0.0 changelog for more information.