Attributes describe span or resource properties. Events record timestamped occurrences during a span. Use them to add context that helps explain a trace without copying entire payloads into telemetry.

Attributes

Use standard semantic-convention keys for common protocols and technologies. For application-specific values, choose stable names, consistent types, and bounded value sets where possible. Add values needed for sampling when the span is created, because a sampler may decide before later updates occur.

Avoid secrets, credentials, message bodies, personal data, and unbounded identifiers. A unique value on every request can increase storage and query cost and make grouping less useful.

Attribute example from demo test traffic in the OpsRamp portal

Events

Add an event for a notable point inside an operation, such as a retry scheduled, a cache fallback selected, or a checkpoint completed. Give it a concise name and only the attributes needed to interpret it. Use a child span instead when the sub-operation has meaningful duration, its own outcome, or remote work.

This test span shows event attributes displayed with span attributes in OpsRamp Trace Details.

Validate

Inspect representative traces to confirm names, types, timestamps, and values are useful. Check that sensitive fields are absent and that high-volume events do not overwhelm the trace with repetitive detail.