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.
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:
logger = Appsignal::Logger.new("gruop") logger.info("message")
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.
Allow functions as backtrace matchers. Alongside regular expressions, you can also provide custom functions to match and replace paths in the backtrace:
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.
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.
Users can now copy the sample backtrace line with a click of a button. (This feature was requested in our Discord channel).
BSON::ObjectId('.)View the Ruby gem v4.7.2 changelog for more information.
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.
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.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.
get_incident tool now supports both exception and anomaly incidents
This release can be installed through our collector packages and Docker image.
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.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:
use Rack::Events, [Appsignal::Rack::EventHandler.new]
And replace it with the following line:
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.
IN and NOT IN in the logs search dropdown.escape key trying to close the log query help tool doesn't clear the query anymore.View the Node.js package v3.7.1 changelog for more information.
min, max or sum values. Use the exemplars provided alongside the histogram to improve the accuracy of the histogram.Access-Control-Allow-Origin header value can be configured in the collector with the cors_origin config option or APPSIGNAL_CORS_ORIGIN environment variable.appsignal.config.request_headers and appsignal.config.response_headers configuration options can still be used for additional header filtering if needed. Consult your application's language OpenTelemetry SDK for the configuration option to record request and response headers.telemetry.sdk.language resource attribute if set. This attribute is set by the OpenTelemetry SDK for some languages, like Go, Java and PHP.
If your application's OpenTelemetry SDK sets the telemetry.sdk.language resource attribute, you will not need to set the appsignal.config.language_integration attribute.
If the appsignal.config.language_integration attribute is set, it will take precedence over the telemetry.sdk.language resource attribute.This release can be installed through our collector packages and Docker image.
View the Node.js package v3.7.0 changelog for more information.
create_incident_note tool for the MCP server. This allows AI Agents to comment on incidents.
update_incident MCP Tool now accepts severity as an argument (and sets the severity accordingly).
0. It should be green, as it has done it's job successfully.
AppSignal offers a 30-day free trial, no credit card is required. All features are available in all plans. Start monitoring your application in just a few clicks!
