Fix compatibility with http.rb v6

Changed

• Bundled certificates have been updated.

Fixed

• Fix compatibility with http (http.rb) gem version 6.0.0 and higher.

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

Fix exit with parent on macOS

Fixed

• Fix an issue where the child process was not terminated on macOS when the parent process was killed by an uncatchable signal, such as SIGSTOP or SIGKILL.

View the appsignal-wrap v0.3.2 changelog for more information.

Update OpenTelemetry dependencies to v2

Changed

• Update OpenTelemetry dependencies to v2. All bundled OpenTelemetry packages have been updated to their OpenTelemetry v2-compatible versions. This resolves compatibility issues when third-party span processors or instrumentations are used alongside AppSignal, which could cause spans to silently drop due to v1/v2 incompatibilities. The @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.
• Update Prisma instrumentation to v7. The @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.
• Bundled certificates have been updated.
• Update BullMQ OpenTelemetry extractor to support new messaging semantic conventions.
• Use system-specific operation name in messaging span names.

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

Open backtrace lines in your local editor

Once configured, open any app code line from an exception backtrace directly in your local editor.

Before setup, the option is available in the extras menu, accessible via the there dots icon.

Set your preferred editor once per app under App Settings → Editor preferences. Each developer on your team can configure their own editor independently.

Supported editors: VS Code, Cursor, Windsurf, Zed, RubyMine, and Sublime Text.

Public MCP Endpoint

Connect AI agents to your AppSignal monitoring data — no Docker container required.

Our MCP server is now available as a hosted endpoint at https://appsignal.com/api/mcp. To generate a token: click your profile, go to Account Settings, then navigate to MCP Tokens. Point your agent at the endpoint, and you're ready to go.

Once connected, your AI agent gets access to 18 tools across five areas:

• Error incidents — list, search, and bulk-update exceptions; assign team members and add investigation notes.
• Anomaly detection — browse open alerts and review trigger configurations for any metric.
• Metrics — discover available metrics, query timeseries data, and get aggregated values with tag filtering.
• Dashboards — create dashboards and add or update chart visuals from your editor.
• App discovery — find apps, environments, namespaces, users, and notifiers.

Works with Claude, Cursor, Windsurf, Zed, VS Code and any agent that supports the MCP protocol.

For setup instructions, see the MCP documentation. Read the full blog post for more details.

HTTPoison instrumentation

Added

• Add HTTPoison instrumentation. HTTP requests made with HTTPoison will appear as request.httpoison events on your performance samples' event timeline.

  HTTPoison does not emit telemetry events, so the instrumentation is opt-in. Use Appsignal.HTTPoison in place of HTTPoison when making requests, or replace use HTTPoison.Base with use Appsignal.HTTPoison.Base for custom client modules. Response types (%HTTPoison.Response{}, %HTTPoison.Error{}, etc.) are unchanged.

Changed

• Bundled certificates have been updated.

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

Fix trace grouping and ignore noisy traces

Fixed

• Fix an issue where certain noisy traces would not be ignored on Next.js and Flask.
• Fix an issue where traces representing requests performed from different HTTP ports on the client's end would be grouped as different traces.

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

More Layout Controls for Dashboards

Your dashboards now bend to your workflow — not the other way around.

• Drag-and-drop widgets

  Reposition any widget by clicking and dragging it wherever makes sense. No grid constraints, no fixed columns — place widgets freely and build a layout that matches how you actually think about your data.

• Resizable widgets

  Expand a chart that deserves more real estate. Shrink the ones that don't. Drag any widget edge to resize it and mix compact summaries with detailed graphs in the same view.

Click Edit dashboard to start reshaping your layout.

Amazon CloudWatch metrics via Amazon Data Firehose

You can now store Amazon CloudWatch metrics in AppSignal through Amazon Data Firehose.

Monitor your most critical AWS services directly from your AppSignal dashboards:

• RDS — track database connections, read/write latency and CPU utilization
• S3 — monitor bucket size, request counts and error rates
• EC2 — observe instance CPU, network traffic and disk I/O
• Lambda — keep an eye on invocations, duration and throttles
• SQS — watch queue depth, message age and processing rates
• And more!

When CloudWatch metrics are detected, we automatically create dashboards for your AWS services.

Setup only takes two steps: create a Firehose stream pointed at AppSignal and connect it to a CloudWatch metric stream. See our CloudWatch metrics documentation to get started.

Fix error reporting in collector mode

Fixed

• Fix an issue where errors set with the set_error helper would not always be reported as errors in AppSignal when using collector mode.

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

Add `default_tags` configuration option

Added

• Add a default_tags configuration option. Tags set in this configuration option will be set for all transactions.

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

Fix HTTP route events and heartbeat shutdown

Fixed

• Fix 'unknown' events being reported for some HTTP routes.
• Fix an issue where usage of continuous heartbeats would stop an application from winding down unless appsignal.stop() was called.

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

Fix check-ins blocking application shutdown

Fixed

• Fix an issue where using check-ins blocks the application from shutting down.

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

Better Database and HTTP span recognition

Added

• Use db.stored_operation.name as one of the attributes to determine if two spans are the same. When it is present, ignore db.statement and db.query.text for the same purpose.

Changed

• Improve recognition of HTTP client spans. This will help our 'slow requests' feature recognize grouped HTTP client spans and improve our N+1 detection.

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

Require parent spans for database and HTTP

Changed

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

Fixed

• Add support for Koa v3.

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

Fix install on Ruby 4 and log configure

Added

• Log where Appsignal.configure is called. When a warning is emitted about Appsignal.configure being called from an application where config/appsignal.yml or config/appsignal.rb exist, log the location from which Appsignal.configure was called alongside the location of the configuration file.

Fixed

• Fix the bundle exec appsignal install CLI command on Ruby 4 by removing the dependency on the ostruct gem, which is no longer part of the standard library.

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

Updated Log Query Syntax and Customizable Views

In the Logging Live and Explore views, we have improved the query syntax with support for nested attributes, and simplified attribute definition in queries. Existing saved views and triggers will need to be migrated to the new syntax, contact support@appsignal.com for assistance.

Read more in our Query Syntax documentation.

Log Views are now customizable

Log attributes can be added as additional columns and saved in views. Click Edit table from the options dropdown to add more columns. Click Save view to persist your customized log view.

Heroku Fir support

We've added Heroku Fir support.

By pointing Heroku Fir's telemetry drain to our collector we report the following:

• Host metrics: CPU usage, memory usage and free memory.
• Metrics from add-ons, such as PostgreSQL and Redis. These will be visible in automatically added dashboards.
• Logs from the Heroku router and API.

For more information, see the Heroku Fir sections in our Heroku documentation.

OpenTelemetry performance alerting

AppSignal supports OpenTelemetry trace data. It's now possible to set up performance alerting for traces.

In a trace summary view, click the "Add new" link in the "Triggers" box.

In the opened "New trigger" modal, configure the alerting, select your preferred notifier, and save the trigger.

It is possible to configure alerting on the mean response time of requests, and the 90th and 90th percentile of the response time. Use a warm-up to only be alerted if this continues for as long as the warm-up is configured.

Now, AppSignal will alert you about new slow actions.

Note: This only works for our OpenTelemetry tracing feature.

Vercel drains: Speed insights and traces

AppSignal supports more Vercel drains: Speed Insights and OpenTelemetry traces.

Speed Insights

Vercel Drains provide support for Web Vitals through the Speed Insights drain, like First Contentful Paint and Largest Contentful Paint. These metrics can serve as signals for delivering great user experience on the web. When Speed Insights metrics are detected, we will automatically create a "Web Vitals" dashboard for your application.

Traces

Report traces from Vercel's infrastructure to get more insights into how all parts of your application are performing. This works with our OpenTelemetry tracing feature and will report errors and performance data from your application and Vercel infrastructure (Vercel functions and edge network).

---

For more information, see these documentation pages:

• Vercel Speed Insights
• Traces from Vercel applications