Distributed tracing for CI pipelines without touching a single workflow file

Description and use

A GitHub organization achieves org‑wide CI tracing without editing workflow files by using a single webhook and OpenTelemetry.

Problem

GitHub Actions workflows lack built‑in distributed tracing, making it hard to diagnose failures across multiple jobs and repositories.

Outcome

All CI jobs across the organization now emit distributed trace data without modifying individual workflow files, enabling faster root‑cause analysis and performance monitoring.

Workflow

• 1. Create an OpenTelemetry Collector deployment in the organization’s infrastructure.
• 2. Configure the collector to receive trace data via a webhook endpoint.
• 3. Add a single GitHub Actions workflow that registers the webhook with the collector for all repositories.
• 4. Enable the OpenTelemetry SDK in the CI jobs by setting environment variables (no workflow file changes).
• 5. Verify trace data appears in the collector’s UI or downstream observability platform.

Evidence

Trace GitHub Actions org-wide with one webhook and OpenTelemetry, without editing workflow files.

Source