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.

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.

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.

Added

• Add the missing icon to the logbook integration create item

Changed

• GitHub integration now fetches all repositories across multiple pages

Added

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

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

Added

• Add MCP tools for programmatic dashboard management; Support creating dashboards, adding visuals, and updating chart configurations.

Added

• Users can now copy the sample backtrace line with a click of a button. (This feature was requested in our Discord channel).

  

Fixed

• Fixed search functionality for queries containing special characters (like BSON::ObjectId('.)

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.