Exception and performance sample detail pages now export as Markdown, alongside the existing JSON download. Open the sample's actions menu and select Download Markdown, or use the copy icon to copy it to your clipboard.
The Markdown is document in sections covering the backtrace, timeline, parameters, attributes, environment, deploy marker, and a context block. Paste it into an AI assistant like Claude or Codex to ask questions about the sample.
The Download JSON row now has the same copy icon, so you can copy either format the same way.
Turn any log source into a stream of metrics — without writing application code or paying to index every line.
Log-based metrics is now in beta, and joins the existing beta and preview features in AppSignal Labs. Define a query against any log source, choose a metric type, and AppSignal extracts the value during ingestion.
Gauge — record the value of an attribute at ingestion (queue depth, connection count).
Measurement — build a histogram of a numeric attribute over time (request duration, payload size, job runtime).
Extraction runs as a log line action, in an order you control. Place it before any filter actions on the same source and you can keep the metric while discarding the underlying log line — handy for high-volume sources you don't need to search line-by-line.
To create one, open the Logs Explorer and select Create a metric — either from the view's ⋮ menu (using the current query) or from a numeric attribute on any log line (using that attribute as the field). Manage your metrics on the new Metrics page under Logging. Any metrics created through the AppSignal MCPmanage_log_line_action tool are visible there too.
A dark theme for the AppSignal UI is now available as part of AppSignal Labs.
Light mode remains the default. To opt in, click your profile picture in the top-right corner and switch the Theme toggle to:
Light — the default
Dark — always-on dark mode
System — follows your OS preference
We're rolling this out gradually as we polish the rough edges, so expect a few screens that aren't quite there yet. Found one that doesn't look right? Tell us — that's the whole point of Labs.
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.
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.
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.
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.
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.
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.
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:
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.
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.
Added a link to the docs in the trace timeline overlay explaining how to add additional instrumentation
Added Anomaly incidents MCP tool
Added a toggle switch to show OpenTelemetry internal attributes
Changed
We've changed the MCP Token UI to better reflect the allowed tools. Instead of sections that can have read/write/delete rights, we're now showing each individual tool with a checkbox for exposure.
