Changelog

Updates and product improvements

RSS
App·Nov 12, 2026

Compare an AppSignal dashboard chart with the previous period, day, or week

Comparing an AppSignal dashboard chart in fullscreen mode with an earlier time range now takes only one step. Select Compare next to the time range menu, and pick one of the following options. Each option shows the dates it compares with dotted lines for the comparison.

  • Previous period compares with the same length of time, right before the chart's range.
  • 1D before compares with the same range one day earlier. It shows when the range is shorter than a day.
  • 7D before compares with the same range one week earlier. It shows when the range is shorter than a week.
  • Custom start date lets you pick a day in the calendar and a Start time. When you hover over a day, the calendar outlines the days the comparison covers.
A fullscreen Throughput chart over 48 hours, compared with the 48 hours before. The Compare menu is open and shows Previous period and 7D before, each with its dates, and Custom start date. Dotted lines show the comparison.
Pick an earlier time range to compare with.

Read more about how to use charts and compare time ranges in our AppSignal dashboards documentation.

2 releases·Nov 12, 2026

Integration releases

  • Stop trusting compromised eMudhra certificates in the 3.x seriesRuby 3.13.3

    Ruby 3.13.3

    Added

    Fixed

    • Fix the sanitization of function arguments in SQL statements. Before this release, SQL sanitization of function arguments stripped out parts of the SQL statement after the function argument list.
    • Fix issues in the extension that lead to gaps in data reporting.
    • Improve handling of the extension internal queue when full.

    Security

    • Bump the bundled certificates that the agent uses when it can't open the configured CA file. They no longer include the emSign ECC Root CA - G3 and AAA Certificate Services root certificates, which compromised eMudhra intermediate certificates chain to.
    • Stop trusting certificates issued under the eMudhra intermediate certificate authorities whose private keys were compromised in October 2026. The bundled CA certificates no longer include the emSign ECC Root CA - G3 root certificate, which those intermediates chain to.

    View the Ruby gem v3.13.3 changelog for more information.

  • Node.js package v3.9.5Node.js 3.9.5

    Node.js 3.9.5

    Fixed

    • Fix a crash when setCustomData, setParams or setSessionData is called with a value that contains a BigInt. BigInt values are now stored as "bigint:<n>", the same format used for metric tags and log attributes.

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

App·Nov 11, 2026

Browser breadcrumbs on performance traces now show the same details as on errors

Performance traces now show breadcrumbs from AppSignal for Browser the same way browser errors do. Until now, they showed each breadcrumb's raw message and metadata. Now a network request shows its method, URL, status, and duration in one row. When the browser provides timing details for a request, hover over its duration to see them.

  • Performance traces from the browser show the browser's network requests with their method, URL, status, and duration in the trace's Breadcrumbs section.
  • The back end of a browser trace shows the same browser breadcrumbs, with the same details. This works when a browser request continues into your back end through distributed tracing.
The Breadcrumbs section of a performance trace in AppSignal, listing navigation, network, long task, click, and error breadcrumbs, with the timing details of a network request shown in a tooltip.
Network requests show their method, URL, status, and duration in one row.

Read the browser breadcrumbs docs to learn more. Browser monitoring is part of AppSignal Labs. Tell us what you think in our Discord channel.

Tools·Nov 10, 2026

GraphQL API returns clear errors for trigger tags and chart updates

Creating a trigger with a tag that has no value now returns a validation error. Chart mutations return validation errors instead of server errors for unsupported input. If you manage triggers and dashboards from scripts or AI agents, you now get an error you can act on.

Trigger tags need a value

Until now, AppSignal saved a trigger with a tag that had a key but no value. That one trigger could stop AppSignal from syncing all of the app's settings, including its other triggers.

Now AppSignal rejects the trigger straight away with the error Tags must each have a key and a text value. This also applies to triggers created or updated with AppSignal MCP.

Chart updates say what to fix

  • Updating a chart with the wrong mutation for its type now returns an error that says the chart is a number or timeseries chart, so you know which mutation to use. Until now, it returned a server error that didn't say why.
  • Tags on a timeseries chart go on each metric. The API no longer accepts tags on the chart itself, and sending them returns an error.

Read the GraphQL mutations docs for which mutation to use for each chart type.

App·Nov 10, 2026

Pick a fullscreen chart's time range from presets or a calendar

When you open a chart in fullscreen, the time range menu now has presets, from 1H to 30D, and a calendar. Pick a preset, or pick the start and end dates in the calendar and set the times in the From and To fields. The menu button shows the length of the range, such as 4H, next to its dates, so you can see at a glance how much time the chart covers.

A fullscreen Throughput chart with the time range menu open. The button reads 4H, 10th Nov 09:56 - 10th Nov 13:56. The menu shows presets from 1H to 30D, a calendar for November 2026, and From and To time fields.
Pick a preset, or pick your own dates and times.

Charts also got these updates:

  • Hidden lines stay hidden. The lines you hide on a chart stay hidden after you reload the page, and when you open the chart in fullscreen. AppSignal saves them in your browser, for up to 50 charts.
  • Comparison lines use the chart's y-axis. When you compare a time range with an earlier one, the dotted comparison lines now use the same scale as the chart's y-axis. You can read their values against the axis, like the solid lines.
A fullscreen Throughput chart comparing 10th Nov 13:03 - 14:03 with 9th Nov 09:54 - 10:54. Solid lines show the current range and dotted lines show the comparison, both on the same y-axis. The side panel lists the values of both ranges for web, admin, and background.
Solid lines show the current range, dotted lines show the comparison.

Read the dashboards documentation to learn how to change a chart's time range and compare it with an earlier one.

App·Nov 10, 2026

Follow a GitLab issue's status from the incident

When you send an incident to GitLab, you no longer have to open GitLab to see where the fix stands. The View #123 in GitLab button in the incident's Actions panel now shows the issue's status as a badge, and AppSignal updates it when the issue changes in GitLab.

  • On GitLab Premium and Ultimate, the badge shows the issue's status as GitLab names it, including custom statuses such as In review.
  • On GitLab Free, the badge shows Open or Closed.
  • The incident's logbook records status changes, with who made them in GitLab.
An incident's Actions panel in AppSignal with a View #2 in GitLab button and an In progress status badge
A linked GitLab issue shows its status in the Actions panel.

To turn it on, a Maintainer or Owner of the GitLab project creates or updates the GitLab integration in AppSignal. See the GitLab integration docs for the steps.

This feature is part of AppSignal Labs. Ask Support to turn it on for your organization, and tell us what you think in our Discord channel.

App·Nov 5, 2026

See when a pull request linked to an incident is deployed

A pull request linked to an incident already shows whether it's open, closed, or merged. Now it also shows when your fix is deployed. Once a deploy ships the pull request, its badge in the incident's Actions panel changes from Merged to Live. You no longer have to check your deploys to know whether the fix is out.

  • Hover over the button to see which deploy shipped the pull request, and when.
  • The incident's logbook records the change from merged → deployed.
An incident's Summary tab in AppSignal. The logbook shows AppSignal changed the status of #20 on GitHub from merged to deployed. In the Actions panel, View #20 in GitHub has a Live badge, and a tooltip reads Deployed in 9175503 2 minutes ago.
A linked pull request shows Live once a deploy ships it.

When AppSignal creates a deploy marker for a new deploy, it asks GitHub which commits the deploy added since the previous one. If a linked pull request was merged in one of those commits, it changes to Live.

AppSignal doesn't track every deploy, such as rollbacks or a deploy of more than 1,000 commits. Read the GitHub integration docs for what you need to set up, and the full list of what AppSignal doesn't track.

This feature is part of AppSignal Labs. Tell us what you think in our Discord channel.

App·Nov 5, 2026

Fixes for large traces and dragging dashboard charts

Large traces no longer crash or freeze the trace page

A trace with a span that has a very large number of child spans, or span links, could crash the trace page or freeze its timeline. These traces now load, so you can inspect them like any other trace.

Dashboard charts follow your pointer when you drag or resize them

When you dragged or resized a chart on a dashboard, it lagged behind your pointer. The chart now follows your pointer while you drag or resize it, and still snaps to the grid when you let go.

App·Nov 5, 2026

Add your first logbook note from the Discover page

The Discover AppSignal page has a new side quest: Add your first logbook note. A logbook note stays with an incident or a slow action. The next person who investigates it sees what you found and what you changed, instead of starting over.

Select Learn about the logbook to see where to write a note. AppSignal doesn't check this side quest for you, so select Mark as done once you've added your note.

The Discover AppSignal page with the main quests completed, and the Add your first logbook note side quest open, showing the Learn about the logbook, Maybe later, and Mark as done buttons.
The Add your first logbook note side quest on the Discover AppSignal page.

Read the logbook documentation to learn how notes work.

Tools·Nov 5, 2026

MCP clients that check for a newer protocol version now discover AppSignal MCP tools

MCP clients that first check for a newer MCP protocol version, such as ChatGPT, now fall back to the version AppSignal MCP supports. Until now, these clients could sign in but then failed to discover AppSignal's tools. ChatGPT showed Authentication succeeded, action discovery failed.

If your client showed this error, connect it to AppSignal MCP again. To connect AppSignal MCP in the ChatGPT desktop app, follow the OpenAI Codex setup.

Tools·Nov 4, 2026

AppSignal MCP returns metric time series your AI agent can read more accurately

When your AI agent asks AppSignal MCP for a metric over time, it now gets data it can read more accurately:

  • Missing data no longer shows as zero. Until now, a period without data looked the same as a value of 0. Your agent could tell you a metric dropped to zero when no data arrived at all. Now it can tell the two apart.
  • A summary comes first. Each result starts with the time range and, for each metric, its peak, low, and average, and the periods without data. Your agent can answer from that without going through every value.
  • Values come as a CSV table. A widely used format that agents and your own scripts can read reliably.
  • You can choose the interval. Ask for values per minute, hour, or day.

If your own code reads the output of the get_metrics_timeseries tool, update it, because the format has changed. Read the MCP tool reference for details.

App·Nov 2, 2026

Fixes for the number charts, deploy, host, and pod inspect pages

Deploy pages show the right deploy

The deploy page now shows the deploy whose revision matches exactly. Until now, if a revision was the start of a longer revision, the page could show the deploy of the longer one. If the revision no longer existed, the page crashed. It now shows Deploy marker not found.

Deploy pages for revisions that contain a dot, such as version numbers, also no longer return a not found page when you reload them or open their link directly.

Number charts no longer hide that they show a single value

A number chart shows one value. A wildcard (*) in its metric, such as hostname=*, matches many series: one for each host. The chart could show only one of them, without saying so, so you could mistake one host's value for the total.

The chart editor already blocked wildcards in number charts. Now the GraphQL API, AppSignal MCP, and the AppSignal CLI block them too, when you create or update a number chart. Number charts saved with a wildcard before this fix can still be updated, as long as the update doesn't add a new wildcard. Read the GraphQL dashboard mutations for more.

Host and pod inspect pages list the right hosts and pods

On the Host metrics page, you can select up to four hosts and select Inspect to compare their metrics. When you picked a custom time range there, the charts used your range, but the dropdown for choosing hosts listed hosts from a different time range. So hosts that reported during your range could be missing from it. The dropdown now uses your custom range. The page that compares Kubernetes pods had the same issue, which is now fixed too.

App·Nov 2, 2026

See services from your other apps by name in the error trace map

Now, the service map on an error trace shows the services that took part in that trace, and the calls between them. When one of those services reports to another app in your organization, the map now shows it by name. Until now, it showed as Unknown service.

An error trace service map with five services. The waitlist service, which reports to a separate app, shows by name next to the services of the main app.
A waitlist service from another app shows by name in the error trace map.

You see this on the error trace page and in the browser error side panel.

Tools·Oct 28, 2026

Log severity filters now live in the log query

The GraphQL API no longer accepts a separate severities argument for log views and log triggers. Put the severity in the query instead. Read more about the log query syntax.

This removes:

  • The severities argument from createLogView, updateLogView, createLogTrigger, updateLogTrigger, and LogLineTriggerInput.
  • The severities field from log views and log triggers.

Requests that still send or select severities now fail. AppSignal CLI versions before 2.2.1 do this, so upgrade to 2.2.1 or later. The schema has marked severities as deprecated since October 15.

Your saved log views and triggers keep working without changes. We already added their severities to their queries. On the Logs page and the log triggers page, you can also filter by severity in the query.

Tools·Oct 28, 2026

OAuth tokens only see what you granted

When you sign in with OAuth, you choose one organization and, optionally, the apps the token can reach. If you select no apps, the token reaches all apps in that organization, including apps you add later. So if you add apps often, you don't need to create a new token each time. The GraphQL API now applies that choice in two more places:

  • Incidents and organizations: an OAuth token now only returns those from the organization and apps it was granted for.
  • Apps: an organization's list of apps no longer includes deactivated apps.

The AppSignal CLI uses this API, so it only shows what you granted when you signed in. AppSignal MCP follows the same rules.

Read more about authentication for the CLI or AppSignal MCP.

App·Oct 28, 2026

Jump from a trace to its host metrics and deploy

Two tags on a trace now link to a related page. Select the icon next to the tag to open it:

  • hostname: View host metrics opens that host's metrics around the time of the trace. In apps that report Kubernetes metrics, it is View pod metrics instead.
  • revision: View deploy opens the deploy for that revision.
The Tags list on a trace, with the View host metrics tooltip on the icon next to the hostname tag and the View deploy tooltip on the icon next to the revision tag.
The hostname and revision tags link to host metrics and the deploy.

The links appear on error and performance traces. Read the trace page docs for every tag action.

App·Oct 26, 2026

See which notifiers still need migrating

The External notifications page now marks deprecated notifiers with a Deprecated label. Its tooltip says what to set up instead. The label appears on:

  • Slack notifiers set up before the current Slack app. Select Migrate on the notifier's row to move it to the new Slack app.
  • PagerDuty notifiers. Set up a PagerDuty V2 API notifier instead.
  • MS Teams notifiers. Set up an MS Teams (Workflows) notifier instead.
The notifiers list with three legacy Slack notifiers marked Deprecated, each with a Migrate button next to Manage, below current Slack notifiers without the label

The deprecated PagerDuty and MS Teams notifiers can stop working at any time, so replace them soon. The Add new notifier list no longer offers them, so you can't set up a new one by mistake.

Read the Slack migration docs for what changes when you migrate a Slack notifier.

Notifier URLs must now be public. AppSignal only sends notifications to addresses on the public internet. It rejects webhook and other notifier URLs that point to localhost, a private network range, or another internal address. If an existing notifier points to one, AppSignal stops sending to it, and its log shows "Request blocked: URL does not resolve to a public address". Point the notifier at a public URL to start receiving notifications again. Read the webhooks docs for details.

$appsignal install

Make your next crash make sense.

Free for 30 days. No credit card. Two-minute install.