Hybrid Agent: Spike on Transformation Rules

[kaylareopelle]

OpenTelemetry Semantic Conventions for attributes and span names are different than the standards adopted by New Relic language agents. When the OpenTelemetry Bridge is in use, these attributes and span names should be converted to match New Relic standards.

The full list of transformations is available in the agent spec (internal).

Spike on the best approach to implement this in the Ruby agent.

Here are some example implementations in other languages:

.NET:

• RPC
• HTTP
• Message Queues

Node:

• feat: Updated opentelemetry bridge to rely on configuration based transformation rules node-newrelic#3125
• refactor: Removed instances of url.parse. Streamlined how http instrumentation creates relevant attributes. node-newrelic#3340

[Newrelic-Boomi]

https://new-relic.atlassian.net/browse/NR-471806