Skip to content

Hybrid Agent: Determine whether we want to include class name in server transaction names #3441

@kaylareopelle

Description

@kaylareopelle

Our current structure for most transaction names using the NewRelic::Agent::Instrumentation::ControllerInstrumentation::TransactionNamer looks like:
Controller/Library/ClassName/method path

The class name is sometimes available in OTel attributes as class.namespace (deprecated) and may eventually be represented in Ruby instrumentation as the stable attribute code.function.name (docs). It is present in some instrumentation available in OTel contrib.

Decide if we want to conditionally include the code.namespace or code.function.name in our OTel sever span/transaction names and, if so, update the NewRelic::Agent::OpenTelemetry::Segments::Server#name_for code to include these attributes when the name is decided.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions