Initial Ruby 2.7 support
The Ruby agent has been verified to run with Ruby 2.7.0-preview1.
New API method to add custom attributes to Spans
New API method for adding custom attributes to spans. Previously, custom attributes were only available at the Transaction level. Now, with Span level custom attributes, more granular tagging is possible for easier isolation and review of traces. For more information:
Enables ability to migrate to configurable security policies (CSP) on a per-agent basis for accounts already using high-security mode (HSM).
When both HSM and CSP are enabled for an account, an agent (this version or later) can successfully connect with either
high_security: trueor the appropriate
high_securityhas been added as part of the preconnect payload.
Bugfix for logs-in-context combined with act-fluent-logger-rails
Previously, when using the Ruby agent's logs-in-context logger to link logging data with trace and entity metadata for an improved experience in the UI, customers who were also using the
act-fluent-logger-railsgem would see a
clear_tags!that would interfere with the use of this feature. This error no longer appears, allowing customers to combine the use of logs-in-context with the use of this gem.
Please note that the logs-in-context logger does not support tagged logging; if you are initializing your logger with a
log_tagsargument, your custom tags may not appear on the final version of your logs.
Bugfix for parsing invalid newrelic.yml
Previously, if the newrelic.yml configuration file was invalid, and the agent could not start as a result, the agent would not log any indication of the problem.
This version of the agent will emit a FATAL message to STDOUT when this scenario occurs so that customers can address issues with newrelic.yml that prevent startup.
Configuration options containing the terms "whitelist" and "blacklist" deprecated
The following local configuration settings have been deprecated:
Bugfix for module loading and constant resolution in Rails
Starting in version 6.3, the Ruby agent has caused module loading and constant resolution to sometimes fail, which caused errors in some Rails applications. These errors were generally
NoMethodErrorexceptions or I18n errors
invalid locale. These errors would not appear if the agent was removed from the application's Gemfile. This version of the agent fixes these issues with module loading and constant resolution, so these errors no longer occur.
Bugfix: failed to get urandom
Previous versions of the agent would fail unexpectedly when the Ruby process used every available file descriptor. The failures would include this message:ERROR : RuntimeError: failed to get urandom
This version of the agent uses a different strategy for generating random IDs, and will not fail in the same way when no file descriptors are available.