Bugfix for transactions with
Previously, transactions containing
ActionController::Liveresulted in incorrect calculations of capacity analysis as well as error backtraces appearing in agent logs in agent versions 5.4 and later. The agent now correctly calculates capacity for transactions with
Add ability to exclude attributes from span events and transaction segments
Agent versions 5.5 and lower could selectively exclude attributes from page views, error traces, transaction traces, and transaction events. With agent version 5.6 and higher, you can also exclude attributes from span events (via the
span_events.include/excludeoptions) and from transaction segments (via the
As with other attribute destinations, these new options will inherit values from the top-level
attributes.include/excludesettings. See the documentation for more information.
Increasing backoff sequence on failing to connect to New Relic
If the agent cannot reach New Relic, it will now wait for an increasing amount of time after each failed attempt. We are also starting with a shorter delay initially, which will help customer apps bounce back more quickly from transient network errors.
Truncation of long stack traces
Previous versions of the agent would truncate long stack traces to 50 frames. To give customers more flexibility, we have added the
error_collector.max_backtrace_framesconfiguration option. Thanks to Patrick Tulskie for the contribution!
Update link in documentation
The community forum link in
README.mdnow goes to the updated location. Thanks to Sam Killgallon for the contribution!
Active Storage instrumentation
The agent now provides instrumentation for Active Storage, introduced in Rails 5.2. Customers will see Active Storage operations represented as segments within transaction traces.