Ruby agent release notesRSS

v9.21.0

• Feature: In Serverless APM mode, use event source name as transaction name prefix

  The agent will now use the event source name as a prefix for the transaction name in Serverless APM mode. This will help to better identify the source of the transaction in the New Relic UI. PR#3245

• Bugfix: Revert changed logic for how we track the thread the span starts in

  This change restores the previous behavior of tracking the thread the span starts in, addressing issues that arose from the updated logic. Thank you @david-zw-liu for bringing this to our attention. PR#3248

v9.20.0

• Característica: Agregar ID Docker de ECS para Fargate

  Anteriormente, el agente Ruby no registraba el ID de Docker cuando se ejecutaba en un entorno AWS ECS Fargate. El ID de Docker ahora se registrará correctamente. PR#3172

• Característica: Agregar NewRelic::Helper.version_satisfied?

  El agente tiene un nuevo método auxiliar para simplificar la comparación de versiones. NewRelic::Helper.version_satisfied? acepta tres argumentos: un número de versión del lado izquierdo, el operador de comparación como una cadena y un número de versión del lado derecho. Nuestro agradecimiento a @kekke-n por esta contribución. PR#3182

• Característica: Agregue el atributo code.stacktrace en los intervalos de almacenamiento de datos cuando la duración excede el umbral configurado

  El agente ahora agregará el atributo code.stacktrace a los intervalos de almacenamiento de datos cuando la duración exceda el umbral configurado. El umbral se configura mediante la opción de configuración transaction_tracer.stack_trace_threshold. PR#3220

• Característica: consolidar valores constantes "desconocidos"

  Todas las referencias a los distintos estilos de capitalización para "Desconocido" se consolidaron en dos constantes: NewRelic::UNKNOWN y NewRelic::UNKNOWN_LOWER. ¡Gracias, @tsubasa1122, por tu contribución! PR#3185

• Corrección de errores: Se corrigen los enlaces de origen de Brewfile

  Anteriormente, los enlaces del README del multiverso al Brewfile estaban rotos. ¡Nuestro agradecimiento a @emmanuel-ferdman por enviar un PR para solucionarlos! PR#3191

• Corrección de errores: Se corrige el error al usar HTTPX 1.5.0

  El agente encontró anteriormente un error al usar la nueva versión HTTPX 1.5.0. Esto se debió a un cambio en la forma en que HTTPX almacena la respuesta. El agente se actualizó para manejar este cambio correctamente y ya no encuentra un error al usar HTTPX 1.5.0. PR#3203

• Corrección de errores: Correcciones de errores y mejoras en los registros del agente de nivel de depuración

  Mejora la información registrada en el nivel de depuración por el agente cuando el agente lee una fuente de configuración. PR#3221

• Corrección de errores: Se solucionó el riesgo de falsificación del lado del servidor para el script de flujo de trabajo de Slack.

  Internamente, realizamos un seguimiento de las gemas que se lanzan mediante un flujo de trabajo de acciones de GitHub que publica actualizaciones en Slack. [@odaysec] identificó una forma en la que podríamos reducir el riesgo de falsificación del lado del servidor para este flujo de trabajo. ¡Gracias! PR#3184

• Corrección de errores: Reemplazar las llamadas JSON.load con JSON.parse

  En general, JSON.parse se considera más seguro que JSON.load. ¡Gracias, @odaysec, por informarnos sobre esto! PR#3183 PR#3230

v9.19.0

• Característica: Agregar ID de hilo como atributo a todos los intervalos

  El agente ahora registrará el ID del hilo como un atributo en cada lapso. PR#3122

• Característica: Agregar soporte para W3C TraceContext traza Flag

  Anteriormente, el agente no empleaba el campo de bandera traza del encabezado traceparent para tomar decisiones de ejemplificación. Esto podría generar una trama fragmentada en la UI. Si bien el comportamiento predeterminado permanece sin cambios, se introdujeron dos nuevas opciones de configuración, distributed_tracing.sampler.remote_parent_sampled y distributed_tracing.sampler.remote_parent_not_sampled, para permitir un mayor control sobre la forma en que se toman las decisiones de ejemplificación. PR#3135

• Corrección de errores: incluir request.uri en el evento de transacción de forma predeterminada

  El diccionario de datos New Relic espera que el evento Transaction tenga el atributo request.uri . El agente Ruby ahora cumple esta expectativa. Si desea excluir request.uri del evento de transacción, puede hacerlo configurando transaction_events.attributes.exclude en 'request.uri'. PR#3103

• Corrección de errores: Se corrige el error en la instrumentación de trabajos activos al usar perform_all_later

  Anteriormente, cuando se llamaba al método perform_all_later de Active Job y el agente estaba en ejecución, se generaba un NoMethodError con el mensaje undefined method 'queue_name' for nil. Se corrigió el error y el nombre del segmento reflejará el primer trabajo en la cola. Nuestro agradecimiento a @tan-linx por informarnos sobre esto y brindarnos una solución. PR#3110

v9.18.0

• Feature: Add elasticsearch.capture_cluster_name configuration option

  A new configuration option, elasticsearch.capture_cluster_name, has been added to control capturing Elasticsearch cluster names. Cluster names are captured by default, but can now be disabled as needed. PR#3038

• Feature: Add support for sidekiq-delay_extensions

  Sidekiq delay extensions were removed from Sidekiq in 7.x and are now avaliable through the sidekiq-delay_extensions gem. Thanks to @sobrinho, the agent now has continued support for delay extensions.PR#3056

• Feature: Parallelize calls for vendor metadata

  Previously, the agent would make calls for vendor metadata in a serial fashion. This could lead to a delay in starting the agent. Now, the agent will make these calls in parallel, reducing the time it takes to start the agent. PR#3094

• Bugfix: Prevent a nil segment from causing errors in Net::HTTP instrumentation

  When using JRuby, a race condition can happen that causes the segment creation to fail and return nil. This would cause an error to occur when methods were later called on the nil segment. These methods will no longer be called if the segment is nil, preventing that error from occurring. PR#3046

• Bugfix: JRuby multithreading improvements

  Added some additional nil checks and mutexes to prevent issues when using the agent on JRuby with multiple threads. Thanks to @NC-piercej for bringing this to our attention Issue#3021 PR#3053

• Bugfix: Stop reporting rescued Sidekiq::OverLimit exceptions

  When Sidekiq's concurrent rate limiters encounter an OverLimit exception, Sidekiq typically handles this by re-enqueuing the job. Previously, all occurrences of Sidekiq::OverLimit were logged as errors in New Relic, even when Sidekiq's middleware resolved the exception. New Relic will no longer report errors that are handled by Sidekiq's own middleware. Thanks to @97jaz for reporting this issue. Issue#3037 PR#3047

• Bugfix: Protect against nil agents or health checks

  In some cases the agent or health checks may be nil when they are called. Safe navigation operators have been added for protection on those occasions. PR#3049

• Bugfix: Ignore Solid Queue ThreadError: queue empty error message by default

  When using the solid_queue gem, the agent previously generated excessive warn-level logs when the queue was empty. The agent now ignores queue empty error messages of the ThreadError class by default. This behavior can be adjusted using the error_collector.ignore_messages configuration option. PR#3060

• Bugfix: Refactor URI host handling to accommodate downcasing frozen strings

  When URI host string was frozen, a FrozenError would be raised when the agent attempted to downcase the host as part of its data normalization process. Now, the update is friendly for frozen strings. Thank you @pedrol3001 for your contribution! PR#3097

v9.17.0

• Feature: Support Ruby 3.4.0

  The agent now supports Ruby 3.4.0. We've made incremental changes throughout the preview stage to reach compatibility. This release includes an update to the Thread Profiler for compatibility with Ruby 3.4.0's new backtrace format. Issue#2992 PR#2997

• Feature: Add instrumentation for aws-sdk-firehose

  The agent now has instrumentation for the aws-sdk-firehose gem. PR#2973

• Feature: Kubernetes APM auto-attach - new agent version precedent

  Previously, when a customer installed the Ruby agent via Kubernetes APM auto-attach and also had the Ruby agent listed in their Gemfile, the agent version in Gemfile would take precedence. Now, the agent version installed by auto-attach takes priority. PR#3018

• Feature: Add health checks when the agent runs within Agent Control

  When the agent is started within an Agent Control environment, a health check file will be created at the configured file location for every agent process. By default, this location is: '/newrelic/apm/health'. The health check files will be updated at the configured frequency, which defaults to every five seconds. PR#2995

• Feature: Add Redshift as recognized ActiveRecord adapter

  When the agent does not recognize an ActiveRecord adapter, the host, port, and database name information is not added to the datastore span. Redshift will now be treated like PostgreSQL, and the agent will save the host, port, and database name on the span. PR#3032

• Feature: Add instrumentation for aws-sdk-kinesis

  The agent now has instrumentation for the aws-sdk-kinesis gem. It will record message broker segments for get_records, put_record, and put_records operations. All other operations will record standard segments. PR#2974

• Bugfix: Stop emitting inaccurate debug-level log about deprecated configuration options

  In the previous major release, we dropped support for many disable_library_name configuration options in favor of instrumentation.library_name. Previously, a DEBUG level log warning appeared whenever disable_* options were set to true, even for libraries (e.g. Action Dispatch) without equivalent instrumentation.* options:

>DEBUG : [DEPRECATED] configuration disable_library_name for library_name will be removed in the next major release. Use instrumentation. library_name with one of ["auto", "disabled", "prepend", "chain"]

This inaccurate warning has been removed. If you are disabling instrumentation using instrumentation.library_name: disabled or NEW_RELIC_INSTRUMENTATION_LIBRARY_NAME=disabled, please verify the option exists by consulting our configuration documentation. If the option does not exist, check the 'Disabling' section to see if there is a related option. We apologize for the confusion. PR#3005

• Bugfix: Do not attempt to decorate logs with nil messages

  The agent no longer attempts to add New Relic linking metadata to logs with nil messages. Thank you, @arlando for bringing this to our attention! Issue#2985 PR#2986

• Bugfix: Stop renaming final Grape segment

  Previously, the agent renamed the final segment in Grape transactions to "Middleware/Grape/#{class_name}/call". This was a part of an old instrumentation pattern that is no longer relevant. Many thanks to @seriousdev-gh for bringing this issue to our attention and along with a great reproduction and suggested fix. PR#2987.

v9.16.1

• Bugfix: Added the support for the Trilogy database adapter.

  The agent now fully supports the Trilogy, a client library for MySQL-compatible database servers, and correctly lists MySQL as the corresponding database in the UI. PR#2966.

v9.16.0

Version 9.16.0 introduces the following features and bug fixes:

• Feature: Instrumentation for aws-sdk-lambda

  When the aws-sdk-lambda gem is available and used to invoke remote AWS Lambda functions, the timing and error details of the invocations will be reported to New Relic. PR#2926.

• Feature: Add new configuration options to attach custom tags (labels) to logs

  The Ruby agent now allows you to opt-in to adding your custom tags (labels) to agent-forwarded logs. With custom tags on logs, platform engineers can easily filter, search, and correlate log data for faster and more efficient troubleshooting, improved performance, and optimized resource utilization. PR#2925

• Feature: Update View Component instrumentation+

  The .identifier method will be formally exposed as part of the View Component public API. The agent will now use this method for building metric names when available, ensuring ongoing compatibility with all View Component versions. PR#2956

• Bugfix: Record explain plan traces on Rails 7.2+

  Rails 7.2 removed adapter-specific connection methods (ex. ActiveRecord::Base.postgresql_connection) and replaced them with ActiveRecord::Base.with_connection. Our explain plan feature relies on making a connection to the database to create an explain plan trace. Due to a bug in our tests, we missed this regression. Now, the agent uses the new method to fetch explain plans on Rails 7.2+. Thank you, @gsar and @gstark for bringing this to our attention! Issue#2922 PR#2940