A CNCF page has published a guide to tracing CI pipelines without changing workflow files. It proposes collecting GitHub Actions run events at the organization level instead of changing every workflow file.

For this, an OpenTelemetry Collector, a service that receives and exports telemetry, can use the GitHub receiver component. That component receives GitHub Actions events through a webhook and converts them into traces.

GitHub receiver is still alpha for metrics and traces, meaning its configuration may change.

Claim check:

  • A CNCF page has published a guide to tracing CI pipelines without changing workflow files. (confirmed by the publication itself: evidence; «Distributed tracing for CI pipelines without touching a single workflow file»)
  • The guide proposes collecting GitHub Actions run events at the organization level instead of changing every workflow file. (confirmed by the publication itself: evidence; «You don’t need to ask each repo to report on itself. You just need to listen to what GitHub is already telling you, at the org level, once.»)
  • An OpenTelemetry Collector can use the GitHub receiver component. (confirmed by the publication itself: evidence; «An OpenTelemetry Collector with the githubreceiver component sits behind a single org-level GitHub webhook»)
  • GitHub receiver receives GitHub Actions events through a webhook and converts them into traces. (confirmed by the primary source: evidence; «Receives GitHub Actions events by serving a webhook endpoint, converting those events into traces.»)
  • GitHub receiver is alpha for metrics and traces, so its configuration may change. (confirmed by the publication itself: evidence; «it’s a contrib component still at alpha stability, so the config surface can shift.»)

Publications:

Primary sources:

score 65.8 · kind guide · revision 1 · stories st-1h8lcck