Description:

This is a request for a native way to send CircleCI pipeline data directly to OTel endpoints — formatted according to the official OTel CICD and VCS Semantic Conventions — without needing a custom intermediary script.

Current Workaround:

Users need to maintain a script that reads CircleCI environment variables and manually generates OTel-formatted traces before forwarding them to our observability endpoint. This adds maintenance overhead and is fragile.

Desired Behavior:

CircleCI natively populates a structured OTel attribute object from pipeline run data and sends it to a user-configured OTel endpoint.

For example:

{

'cicd.pipeline.run.id': <pipeline_run_id>,

'cicd.pipeline.result': <pipeline_result>,

...

}

Ideally this object would be mutable so teams can add or override attributes before export.

Use Case / Impact:

This would benefit any team using OTel-native observability tools (Honeycomb, Datadog, Grafana, etc.) and eliminate the need for custom trace-generation scripts on top of CircleCI webhooks.