Ruby agent v10.2.0

v10.2.0

• Feature: Introduce Hybrid Agent for OpenTelemetry Tracing Support

  OpenTelemetry Tracing APIs can now be translated into New Relic telemetry with the New Relic Ruby agent's new Hybrid Agent features. This allows the newrelic_rpm gem to behave similarly to an OpenTelemetry SDK, accepting OpenTelemetry API calls and turning them into New Relic Transactions and Segments with familiar attributes and names.

  The following configuration options relate to Hybrid Agent features:

  Configuration name	Default	Behavior
  opentelemetry.enabled	false	A global configuration option for disabling all OpenTelemetry signals sent through New Relic.
  opentelemetry.traces.enabled	true	Enables the creation of Transaction Trace segments and timeslice metrics from OpenTelemetry Spans
  opentelemetry.traces.include	''	A comma-delimited list of OpenTelemetry Tracers, represented as a string (e.g. "AppTracer1,OpenTelemetry::Instrumentation::Bunny::Instrumentation"), that will have their trace signals sent to New Relic.
  opentelemetry.traces.exclude	''	A comma-delimited list of OpenTelemetry Tracers, represented as a string (e.g. "AppTracer1,OpenTelemetry::Instrumentation::Bunny::Instrumentation"), that will not have their trace signals sent to New Relic. All known tracers for instrumentation that conflicts with New Relic instrumentation are excluded by default.

• Feature: Add configuration option error_collector.backtrace_truncate_location

  A new configuration option has been added, error_collector.backtrace_truncate_location, which allows the user to specify where in the backtrace to truncate when the number of frames exceeds error_collector.max_backtrace_frames. Options are 'top' (removes frames from the beginning), 'middle' (removes frames from the middle, preserving the beginning and end), or 'end' (removes frames from the end). The default is 'middle'. PR#3424

• Feature: Add Logging gem instrumentation

  The agent will now record logs generated by the Logging gem. PR#3420

• Feature: Add configuration option utilization.detect_in_parallel

  A new configuration option has been added, utilization.detect_in_parallel, which controls whether the agent uses threads when detecting cloud vendor information to speed up agent startup. When set to false, vendor detection runs sequentially without creating threads. The default is true. PR#3439