Telemetry
Definition
The signal type that this transformation rule applies to.
traces: Apply transformations to trace data (spans and span events).metrics: Apply transformations to metric data (metrics and data points).logs: Apply transformations to log data (log records).profiles: Apply transformations to profile data.
"traces""metrics""logs""profiles"The OTTL evaluation context that determines which telemetry fields are accessible to the statements. Not all contexts are valid for all signal types:
For traces:
resource: Transform resource-level attributes.scope: Transform instrumentation scope-level attributes.span: Transform individual span properties and attributes.spanevent: Transform individual span event properties and attributes.
For metrics:
resource: Transform resource-level attributes.scope: Transform instrumentation scope-level attributes.metric: Transform metric-level properties (name, description, type).datapoint: Transform individual metric data point attributes.
For logs:
resource: Transform resource-level attributes.scope: Transform instrumentation scope-level attributes.log: Transform individual log record properties (body, severity, attributes).
For profiles:
resource: Transform resource-level attributes.scope: Transform instrumentation scope-level attributes.profile: Transform individual profile properties and attributes.
Contexts never supply access to items lower in the protobuf hierarchy, but always supply access to
items higher in the hierarchy. For example, a datapoint context can access its metric, scope, and
resource, but a metric context cannot access individual data points.
"resource""scope""span""spanevent""metric""datapoint""log""profile"A list of OTTL conditions that act as a global gate for the statements. The conditions are ORed together, meaning only one condition needs to evaluate to true for the statements to be executed.
Used by 1
These schemas and endpoints reference this type directly.