Fixed

• Fix an issue with loggers not supporting a formatter on Rails boot. This will prevent the AppSignal logger config from running into an error if the logger configuration is added to config/application.rb or one of the environments in config/environments/.
• Do not log long (error) messages to the internal AppSignal log. If an error like ActionController::BadRequest occurred and the error message contained the entire file upload, this would grow the appsignal.log file quickly if the error happens often. Internal log messages are now truncated by default.

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

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 a log format option for autodetection the log format.
• Add support for native OpenTelemetry spans from @elastic/transport package in Node.js.

Changed

• Detect the log format automatically. We now detect if a log line is in the JSON, Logfmt, or plaintext format. No further config needed when calling our logger, like so:

  JavaScript

  const logger = Appsignal.logger("app");
  logger.info("message");

Fixed

• Fix 'unknown' events being reported for some HTTP routes.

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

Added

• Add the missing icon to the logbook integration create item

Changed

• GitHub integration now fetches all repositories across multiple pages

Fixed

• Fix parsing of OpenTelemetry spans emitted by FastAPI and popular database libraries.

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

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 support for Oban timeout exceptions

Changed

• Detect the log format automatically. We now detect if a log line is in the JSON, Logfmt or plaintext formats. No further config needed when calling our logger, like so:

  Elixir

  Appsignal.Logger.info("group", "message")

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

Added

• Support logging through the external collector experimental feature. When the collector_endpoint configuration option is provided, the OpenTelemetry stack will be automatically configured to instrument logs.

  The logging module will be automatically instrumented, such that log lines emitted through loggers that propagate to the root logger will be automatically sent to AppSignal. To disable this behaviour, add "logging" to the disable_default_instrumentations configuration option list.

• Support usage with external collector. When the collector_endpoint configuration option is provided, instead of booting up the AppSignal agent bundled with the application, the OpenTelemetry stack will be configured to send data to the given collector.

  This is an experimental feature. The following functionality is not currently supported when using the collector:

  • NGINX metrics
  • StatsD metrics
  • Host metrics

  Some configuration options are only supported when using the agent or when using the collector. A warning will be emitted if a configuration option that is only supported by one is set while using the other.

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

Added

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

Fixed

• Handle transactions without errors in CodeOwnership integration. AppSignal will not emit an error log line if a transaction has no error.

  Thanks @fatkodima for your contribution!

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

Changed

• Detect the log format automatically. We now detect if a log line is in the JSON, Logfmt or plaintext formats. No further config needed when calling our logger, like so:

  Ruby

  logger = Appsignal::Logger.new("gruop")
  logger.info("message")

Fixed

• Handle unowned files in CodeOwnership gem integration. AppSignal will not emit an error log line if no Team can be found for a backtrace.

  Thanks @fatkodima for your contribution!

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

Added

• Allow functions as backtrace matchers. Alongside regular expressions, you can also provide custom functions to match and replace paths in the backtrace:

  JavaScript

  const appsignal = new Appsignal({
    // ...
    matchBacktracePaths: [(path) => {
      if (path.indexOf("/bundle/") !== -1) {
        return "bundle.js"
      }
    }]
  })

  The function must take a backtrace line path as an argument. When the function returns a non-empty string, the string will be used as the path for that backtrace line. Otherwise, the path will be left unchanged.

Fixed

• Fix matching on backtrace paths containing spaces.

  When using matchBacktracePaths, when a backtrace line path contains a space, it will now match correctly against the whole path.

View the AppSignal JavaScript javascript v1.6.1 changelog for more information.

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('.)

Fixed

• Fix sample data not being reported for JRuby applications. Data like tags, parameters, session data, etc. would not be set if a transaction was sampled.

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

Added

• Add support for the CodeOwnership gem, which allows engineering teams to declare ownership of specific parts of a codebase.

  When an error is reported, the AppSignal gem will tag the transaction with the owner of the file that caused the error.

  This feature is enabled by default. To disable it, set the instrument_code_ownership configuration option to false.

Changed

• Do not patch Rack::Events when using recent Rack versions. When using versions 3.2.1 and above, which contain a fix for the bug where using Rack::Events breaks requests with streaming bodies, use Rack::Events directly, instead of our patched subclass.

Fixed

• Fix Rails version detection when only one of Rails's gems is present.

  This prevents loading errors when non-Rails code defines a Rails constant without the full Rails framework.

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

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.

  

Fixed

• Report errors in AppSignal for exception events in Next.js render spans.

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

Added

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

  

Added

• Add Sidekiq worker-level job status metric: worker_job_count. This new counter metric's status tag will be processed for each job that's processed and reports another counter with the failure status if the job encountered an error.

Fixed

• Support streaming bodies. AppSignal's Rack instrumentation now supports streaming bodies in responses, such as those produced by Async::Cable. This fixes an issue where AppSignal's Rack instrumentation would cause requests with streaming bodies to crash.

  If you use our Rack instrumentation through a framework that is automatically instrumented by AppSignal, such as Rails, Hanami, Padrino or Sinatra, this fix is applied automatically.

  If your application instruments Rack manually, you must remove the following line from your application's initial setup:

  Ruby

  use Rack::Events, [Appsignal::Rack::EventHandler.new]

  And replace it with the following line:

  Ruby

  use Appsignal::Rack::EventMiddleware

• Avoid instrumenting Rails when AppSignal is not active. If AppSignal is configured to start when the Rails application loads, rather than after it has initialised, only add Rails' instrumentation middlewares if AppSignal was actually started.

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