MCP Server (beta)

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.

Improve logger and ignore Rack connection errors

Fixed

• When an Appsignal::Logger uses .broadcast_to to broadcast messages to other loggers, broadcast those messages even if the log level of those messages is lower than the logger's threshold. This allows other loggers to set their own logging thresholds.

  When the logger is silenced, messages below the silencing threshold are not broadcasted to other loggers.

• When an Appsignal::Logger uses .broadcast_to to broadcast messages to other loggers, broadcast the original message received by the logger, without formatting it or converting it to a string.

• Call the Appsignal::Logger formatter with the original message object given, rather than converting it to a string before calling the formatter.

• When an error is passed to an Appsignal::Logger as the message, format it regardless of the logging level. Previously it would only be formatted when passed to #error.

• Ignore Errno::ECONNRESET errors in the Rack wrapper.

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

Fix non-canonical rendering event paths for events

Changed

• Log the error's backtrace on extension download failure. This will help us debug issues related to downloading the extension.

Fixed

• Fix non-canonical rendering event paths for Capistrano deployments

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

Customize namespaces through Plugs for Absinthe routes

Changed

• Allow for more customization of trace namespaces during the trace's lifetime. Previously, it was not possible to customize the namespace of Absinthe traces before the Absinthe instrumentation had run. This is now possible, as the Absinthe instrumentation will only set the namespace if it has not been set already.

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

Add NGINX port configuration option

Added

• Add nginx_port configuration option. This configuration option can be used to customize the port on which the AppSignal integration exposes the NGINX metrics server.

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

Add NGINX port configuration option

Added

• Add nginxPort configuration option. This configuration option can be used to customize the port on which the AppSignal integration exposes the NGINX metrics server.

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

Add NGINX port configuration option

Added

• Add nginx_port configuration option. This configuration option can be used to customize the port on which the AppSignal integration exposes the NGINX metrics server.

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

Add NGINX port configuration option

Added

• Add nginx_port configuration option. This configuration option can be used to customize the port on which the AppSignal integration exposes the NGINX metrics server.

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

Add NGINX port configuration option

Added

• Add nginx_port configuration option. This configuration option can be used to customize the port on which the AppSignal integration exposes the NGINX metrics server.

This release can be installed through our standalone agent packages and as a Docker image.

Auto-Redirect to Your Last Viewed App!

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.

Ruby gem v4.5.14

Fixed

• Resolve problems with transactions not being properly closed when using libraries that change Fibers during the transactions. Previously, completed transactions would be attempted to be reused when creating a transaction, when the Fiber would be switched during a transaction.
• Fix a config error log message when the config is not active and should not validate the config.

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

Ignore logs and improved trace processing

Added

• Add an ignore_logs config option, which can be set using the appsignal.config.ignore_logs resource attribute. When this resource attribute is set, logs whose message matches any of the values in the ignore_logs list of values will be discarded.

  The values on the ignore_logs configuration option support the ^, $ and .* meta-characters, with their expected meanings in regular expressions. When neither ^ or $ are specified at the beginning or ending of the value respectively, ignore_logs will match a log message if its value is present at any point in the message.

  For example, to ignore logs starting with "success" or containing the word "OK", when setting the resource attributes in a Go application:

  Go

  res := resource.NewWithAttributes(
  	attribute.StringSlice("appsignal.config.ignore_logs", []string{"^success", "OK"}),
  	// And other resource attributes
  )

  The list of patterns can also be provided as a comma-separated string -- this is useful when using the OTEL_RESOURCE_ATTRIBUTES environment variable, such as in a PHP application:

  Shell

  function encode() {
    echo -n "$@" | sed 's/,/%2C/g'
  }
   
  export OTEL_RESOURCE_ATTRIBUTES="\
    appsignal.config.ignore_errors=$(encode "^success,OK"),\
    ..."

Changed

• Improve AppSignal compatibility with traces across multiple services.

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

Collector v0.6.2

Added

• When reporting a boolean resource attribute configuration option, such as send_function_parameters, send_request_payload, send_request_query_parameters and send_request_session_data, allow it to be provided as a string containing the case-insensitive values "true" or "false".

  This makes it possible to set these configuration options using the OTEL_RESOURCE_ATTRIBUTES environment variable.

Changed

• Allow overriding automatically set namespaces. When a namespace is automatically by AppSignal, set it only if a different namespace has not been set in the trace using the appsignal.namespace attribute.
• Improve communication from the collector's exporter server to the client by returning the expected OpenTelemetry export response messages from the collector's HTTP server. This includes updating the tracing, metrics and logs endpoints by returning their respective response messages.

Fixed

• Truncate the keys of attributes and the overall size of the attribute list for spans, events, scopes, resources and links.

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

Improve Oban job result reporting

Changed

• Update the result attribute reported for Oban jobs. Instead of it including the job's whole return value, it only contains the Oban job control value: :ok/:error/:discard/:cancel/:snooze. The reason for a discard, cancel, error or snooze result will be stored in the new result_reason attribute. Any :ok result reasons and unexpected result values are ignored. This is to avoid storing sensitive data in the attributes and to make it easier to filter by job control value in the interface.

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

Report Active Job queue time

Added

• Report the Active Job queue time as the active_job_queue_time metric. This metric can be used to track the queue time per Active Job queue.

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

Fix extension installation issue

Fixed

• Fix the C extension function definitions. On install, the Ruby gem extension would print warnings or fail to compile.

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

Log a debug message when ignoring an error

Changed

• Log a debug message when the reported error is ignored by the ignore_errors config option.

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

Allow overriding namespaces and other improvements

Changed

• Allow overriding namespaces that are automatically set by the AppSignal agent based on the OpenTelemetry instrumentation that emitted the span, such as the graphql or background namespaces.
• Log a debug message when the reported error is ignored by the ignore_errors config option.

Fixed

• Update mysql2 and pg instrumentations. This fixes an issue where queries performed using promises with mysql2@3.11.5 are not instrumented, as well as an issue where pg is not instrumented under certain bundlers and runtimes.

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

Allow overriding namespaces

Changed

• Allow overriding namespaces that are automatically set by the AppSignal agent based on the OpenTelemetry instrumentation that emitted the span, such as the graphql or background namespaces.

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

Log a debug message when ignoring an error

Changed

• Log a debug message when the reported error is ignored by the ignore_errors config option.

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