Added

• MCP get_incident tool now supports both exception and anomaly incidents

Fixed

• Ensure the graph export popover isn’t cut off when placed at the bottom of the page.

Added

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

  

Added

• Add functionality that allows filtering log triggers by name, source, or creator.

  

Added

• Add 3rd party integration links (e.g. GitHub, Jira) to MCP get_incident tool. The AI Agent can use this to tie incidents to external issues.
• Add uptime monitoring metrics to the MCP metric discovery tool
• Support ANSI colors in Logs page
• Persist the option to hide the logs chart between queries.

Added

• Add examples and “click to apply” functionality for IN and NOT IN in the logs search dropdown.
• Log sources now support automatic format detection. We will attempt to parse the line as JSON, Logfmt, and plain text, extracting attributes on every step.

Changed

• Hitting the escape key trying to close the log query help tool doesn't clear the query anymore.

Added

• Add the create_incident_note tool for the MCP server. This allows AI Agents to comment on incidents.

  

Changed

• The update_incident MCP Tool now accepts severity as an argument (and sets the severity accordingly).

Added

• Add "via" label to logbook items if they were created through a 3rd-party source (e.g. an MCP server)

  

Fixed

• Fix terminated color when exit code of the container is 0. It should be green, as it has done it's job successfully.

  

Added

• Add error causes for OpenTelemetry errors

  

Added

• Allow downloading samples as JSON
• Include Unassigned option in the assignee filter
• Add a callout to the instrumentation docs when the trace timeline has a few items

Fixed

• Fix visual bugs in the integration button dropdown.

Added

• You can now select an assignee on Enter, when there's only one filtered entry, on the incident list and show pages.
• Add a table on the Cluster monitoring node inspect page, showing all the pods related to the selected nodes

Added

• Add the ability to treat missing data point as 0 for performance and error triggers. If you have traffic in bursts (e.g. a Cron job), there's not always enough data to trigger or close an alert. When checking this checkbox, we will simulate the metric, allowing alerts to close.

  

• Add container status, uptime, and restart count in the Kubernetes Pods table
• Add container status and owner reference grouping options in the Kubernetes overview page
• Add uptime and restart count in the Pod overview tooltip

Changed

• Update the order of steps in the OpenTelemetry Java installation flow to improve the installation flow experience.

Added

• Add ability for Ai Agents to discover our metrics on our MCP server. Before this discover_metrics endpoint, we had our get_metric_names endpoint, but it was difficult for agents to determine what metric should be used when.

  With this new discover_metrics endpoint, we provide the Agent with a global overview of metric categories, and when they request more information about a category, we describe the metric names/tags/fields, and when to use them.

  We also take custom metrics and dashboards into account. Providing descriptive names for dashboards/description and charts on your dashboards helps the agent use those metrics.

Changed

• Improve cluster state pop-over. Show state of containers, if there are any.

  

Added

• Add get_metrics_timeseries endpoint to the MCP server. This endpoint exposes timeseries metrics to an AI Agent, enabling queries such as

  Show me the load average for all front-end machines on MyApp/production

  Shell

  Here's a summary of the load averages for the two frontend machines:
  
  1. frontend1:
    - Load average range: 0.83 - 1.6
    - Current load: 0.94
  
  2. frontend2:
    - Load average range: 2.0 - 3.01
    - Current load: 2.18
  
  The frontend-ams1 machine appears to have a significantly higher load compared to frontend1, with load averages consistently above 2.0, while frontend2 stays mostly below 1.5.
  

  We are still working on metric discovery. Right now you have to be quite specific to get the desired metrics.

• Add kubernetes volume metrics to node page.

  

Added

• Add MCP endpoint to list all applications a user has access to.
• Add Kubernetes overview page. This page shows your entire Kubernetes cluster state in one glance.

  

Added

• Add ability to set custom headers for our "Webhook" notifier

Added

• Dedicated MCP authentication tokens. Instead of providing your personal AppSignal API key, that has access to all your organizations and applications, we're moving to a dedicated MCP authentication token.

  This token can be scoped to a specific organization and one or more applications. It also has permissions per "toolset", such as error incidents, metrics, and other sections of AppSignal.

  

  See our documentation for more information on installing the AppSignal MCP Server.

Added

• Debug your exceptions with the help of AI Agents through our AppSignal MCP Server.

  

  The MCP server is currently in beta, and we're focusing on (local) debugging of error incidents at this stage.

  MCP server endpoints available at this moment are:

  • get_namespaces, which can be filtered by app, and returns a list of namespaces to be used with the get_exception_incidents endpoint
  • get_users, which can be filtered by app, and returns a list of users to be used with the update_incident endpoint
  • get_exception_incidents, which can be filtered by app/namespace/status, and returns a list of incidents
  • get_incident returns detailed incident information
  • update_incidents (bulk) updates an incident with the assigned user and state

  See our documentation for more information on installing the AppSignal MCP Server.

Added

Tired of manually navigating to your app after logging in? Enable auto-direct in your user settings to automatically open the last app you viewed. Pick up right where you left off, every time you log in.

Auto-Redirect can be enabled in user settings.

Added

We now detect all Hxx router and Rxx resource errors from Heroku logs by parsing logfmt messages instead of using a single regex pattern.

Added

Users now receive notifications when sending a sample or span with improperly formatted data, such as non-JSON parameters or unsupported keys.