HTTPoison instrumentation

Added

• Add HTTPoison instrumentation. HTTP requests made with HTTPoison will appear as request.httpoison events on your performance samples' event timeline.

  HTTPoison does not emit telemetry events, so the instrumentation is opt-in. Use Appsignal.HTTPoison in place of HTTPoison when making requests, or replace use HTTPoison.Base with use Appsignal.HTTPoison.Base for custom client modules. Response types (%HTTPoison.Response{}, %HTTPoison.Error{}, etc.) are unchanged.

Changed

• Bundled certificates have been updated.

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

Fix trace grouping and ignore noisy traces

Fixed

• Fix an issue where certain noisy traces would not be ignored on Next.js and Flask.
• Fix an issue where traces representing requests performed from different HTTP ports on the client's end would be grouped as different traces.

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

More Layout Controls for Dashboards

Your dashboards now bend to your workflow — not the other way around.

• Drag-and-drop widgets

  Reposition any widget by clicking and dragging it wherever makes sense. No grid constraints, no fixed columns — place widgets freely and build a layout that matches how you actually think about your data.

• Resizable widgets

  Expand a chart that deserves more real estate. Shrink the ones that don't. Drag any widget edge to resize it and mix compact summaries with detailed graphs in the same view.

Click Edit dashboard to start reshaping your layout.

Fix error reporting in collector mode

Fixed

• Fix an issue where errors set with the set_error helper would not always be reported as errors in AppSignal when using collector mode.

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

Add `default_tags` configuration option

Added

• Add a default_tags configuration option. Tags set in this configuration option will be set for all transactions.

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

Fix HTTP route events and heartbeat shutdown

Fixed

• Fix 'unknown' events being reported for some HTTP routes.
• Fix an issue where usage of continuous heartbeats would stop an application from winding down unless appsignal.stop() was called.

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

Fix check-ins blocking application shutdown

Fixed

• Fix an issue where using check-ins blocks the application from shutting down.

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

Better Database an HTTP span recognition

Added

• Use db.stored_operation.name as one of the attributes to determine if two spans are the same. When it is present, ignore db.statement and db.query.text for the same purpose.

Changed

• Improve recognition of HTTP client spans. This will help our 'slow requests' feature recognize grouped HTTP client spans and improve our N+1 detection.

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

Require parent spans for database and HTTP

Changed

• Require parent spans on database and outgoing HTTP instrumentations that support it. When a database query is performed using the ioredis, pg, redis or mongoose libraries, or when an outgoing HTTP request is performed using the http module, a span will only be created if a trace has already been started in the current active context, that is, if the span to be created would have a parent.

  This helps prevent database queries and outgoing HTTP requests happening in uninstrumented contexts from counting towards your requests quota.

Fixed

• Add support for Koa v3.

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

Fix install on Ruby 4 and log configure

Added

• Log where Appsignal.configure is called. When a warning is emitted about Appsignal.configure being called from an application where config/appsignal.yml or config/appsignal.rb exist, log the location from which Appsignal.configure was called alongside the location of the configuration file.

Fixed

• Fix the bundle exec appsignal install CLI command on Ruby 4 by removing the dependency on the ostruct gem, which is no longer part of the standard library.

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

Updated Log Query Syntax and Customizable Views

In the Logging Live and Explore views, we have improved the query syntax with support for nested attributes, and simplified attribute definition in queries. Existing saved views and triggers will need to be migrated to the new syntax, contact support@appsignal.com for assistance.

Read more in our Query Syntax documentation.

Log Views are now customizable

Log attributes can be added as additional columns and saved in views. Click Edit table from the options dropdown to add more columns. Click Save view to persist your customized log view.

Heroku Fir support

We've added Heroku Fir support.

By pointing Heroku Fir's telemetry drain to our collector we report the following:

• Host metrics: CPU usage, memory usage and free memory.
• Metrics from add-ons, such as PostgreSQL and Redis. These will be visible in automatically added dashboards.
• Logs from the Heroku router and API.

For more information, see the Heroku Fir sections in our Heroku documentation.

OpenTelemetry performance alerting

AppSignal supports OpenTelemetry trace data. It's now possible to set up performance alerting for traces.

In a trace summary view, click the "Add new" link in the "Triggers" box.

In the opened "New trigger" modal, configure the alerting, select your preferred notifier, and save the trigger.

It is possible to configure alerting on the mean response time of requests, and the 90th and 90th percentile of the response time. Use a warm-up to only be alerted if this continues for as long as the warm-up is configured.

Now, AppSignal will alert you about new slow actions.

Note: This only works for our OpenTelemetry tracing feature.

Vercel drains: Speed insights and traces

AppSignal supports more Vercel drains: Speed Insights and OpenTelemetry traces.

Speed Insights

Vercel Drains provide support for Web Vitals through the Speed Insights drain, like First Contentful Paint and Largest Contentful Paint. These metrics can serve as signals for delivering great user experience on the web. When Speed Insights metrics are detected, we will automatically create a "Web Vitals" dashboard for your application.

Traces

Report traces from Vercel's infrastructure to get more insights into how all parts of your application are performing. This works with our OpenTelemetry tracing feature and will report errors and performance data from your application and Vercel infrastructure (Vercel functions and edge network).

---

For more information, see these documentation pages:

• Vercel Speed Insights
• Traces from Vercel applications

New chart type: Number chart

Added a new chart type for dashboards: the number chart. The number chart displays a number on the dashboard instead of a line graph. Useful when a single value gives enough information at a glance.

The chart supports multiple ways of calculating the metric data for the timeframe selected, such as:

• Maximum value: Show the highest metric value.
• Minimum value: Show the lowest metric value.
• Average value: Show the average of the metric values.
• Total value: Show the combined value of the metric values.
• First value: Show the first metric value.
• Last value: Show the last metric value.

To add a number chart, go to your application in AppSignal, create or open a dashboard, click "Add chart", and select "Number" in the sidebar.

Allow app-level push API keys

Changed

• Allow the use of app-level push API keys. When an app-level push API key is used, the resource attributes for the name and environment should not be specified. These resource attributes are now optional, although the use of one requires the other.

• Make most resource attributes optional. Allow for the resource attributes pertaining the revision, the hostname, the language integration and the application path to not be present. This allows the AppSignal collector to more easily ingest data from arbitrary OpenTelemetry sources.

  Note that usage of these resource attributes is still recommended. Traces sent without these attributes may be tagged with the wrong hostname or revision, or have their error backtraces parsed incorrectly.

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

Disable `ActiveSupport::EventReporter` logs

Changed

• Disable the enable_active_support_event_log_reporter configuration option by default.

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

Ruby gem v4.8.0

Added

• Report events from Rails 8.1's Structured Event Reporting (ActiveSupport::EventReporter) as logs.

Fixed

• Fix ActiveSupport::Notifications event instrumentation on Rails 8.1 when no listeners are registered.

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

Limit required headers for Heroku Telemetry drain

Changed

• Use heroku.release.version resource attribute as a fallback value for revision for Heroku Fir applications.

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

Elixir package v2.16.0

Changed

• Disable the error backend by default

  With new ways of instrumenting errors added, the error backend is unneeded in most setups. Disable it by default to make it opt-in.

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