Ruby agent v10.5.0

v10.5.0

• Feature: Add Dalli 5.0 support and fix meta protocol instrumentation

  The agent now supports Dalli 5.0+, which removed Dalli::Protocol::Binary in favor of the meta protocol exclusively. For Dalli 3.2.0+, pipelined_get instrumentation now correctly targets Dalli::Protocol::Base (where the method is defined) rather than Dalli::Protocol::Binary, fixing a gap where get_multi calls went uninstrumented when using the meta protocol. For Dalli 5.0+, the agent additionally instruments Dalli::Protocol::Meta#read_multi_req, which is invoked by Dalli's single-server get_multi optimization. PR#3541

• Feature: Add active_record_use_table_name configuration option

  A new configuration option, active_record_use_table_name, uses an Active Record model's table name instead of its class name when naming metrics, spans, and transaction trace segments. This can particularly be helpful to reduce cardinality in applications using single-table inheritance. The option defaults to false to preserve existing behavior. PR#3540

• Feature: Partially redact license keys in agent logs

  Previously, the agent would fully redact New Relic license keys in agent logs. Now, the first 10 characters are visible while the rest are replaced with *. This preserves enough to troubleshoot region-related issues without exposing the secret portion of the key. PR#3547

• Bugfix: Fix Semantic Logger instrumentation incompatibility with rails_semantic_logger

  Previously, an ArgumentError would be raised when an exception reached ActionDispatch::DebugExceptions while using rails_semantic_logger. This has been fixed. Thank you to @jdelStrother for reporting this! PR#3548