CI/CD Observability SIG Phase 2

November 12, 2025 ยท View on GitHub

CI/CD Project Board

Overview

The initial founding of the CI/CD Observability SIG produced multiple outcomes and improvements in the OpenTelemetry space. To capture a few, the group:

  • Created multiple foundational sets of attributes related to CI/CD in the registry across multiple versions of Semantic Conventions.
  • Added span attribute conventions for CI/CD pipelines.
  • Added metric attribute conventions around CI/CD systems.
  • Created the OTEP for Environment Variable Context Propagation and drove it through approval.
  • Based on the OTEP, updated the specification to include support with supplementary guidance.
  • Wrote a Python draft prototype to implement the specification.
  • Updated and supported the GitHub and GitLab OpenTelemetry Collector components.
  • Delivered multiple talks around the CI/CD SIG.
  • Worked with Jenkins, Team City, and OpenTofu around adoption within those technologies.

There is still a lot of things to accomplish, and as such, we propose implementing phase two of the CI/CD Observability SIG.

Phase Two Goals

This phase targets three core areas for immediate impact:

  1. SDK Environment Variable Context Propagation: Implement the spec across multiple OpenTelemetry languages for first class, native support.
    • Python
    • Go
    • C#
    • Javascript
  2. Enhanced Signal Attribute Conventions: Establish additional attribute conventions for CI/CD-specific trace, metrics, and logs telemetry for the following namespaces and domains:
    • build
    • deployment
    • issues
    • incidents
    • test
    • pipeline
  3. Beta Stabilization: Move core CI/CD semantic conventions and collector implementations from experimental to beta status
  4. Increase Adoption: Work towards getting one or more new technologies adoption of the OpenTelemetry conventions.
  5. Stretch Goal: Figure out how to enable better support for long running traces via Issue #1648.

Phase 2 Staffing & Responsibilities

GC Liaison

  • @maryliag (GC Liaison)

TC Sponsorship

  • @carlosalberto (TC Sponsor)

Phase 2 Team Structure

Project Leadership:

  • @horovits Project Lead (AWS)
  • @adrielp Project Lead (Grainger)

Approvers:

  • @open-telemetry/semconv-cicd-approvers

Project Members:

  • @martincostello (Grafana Labs)
  • @kamphaus
  • @niwoerner (OllyGarden)

Phase 2 Resource Requirements

Critical Needs:

  • SDK maintainer commitment for environment variable context propagation implementation
  • Platform integration testing resources

Success Dependencies:

  • Dedicated engineering time from SDK teams (guesstimated 2-3 months per SDK)
  • Platform vendor collaboration for integration testing
  • Community feedback and early adoption validation

Meeting Times

This SIG will meet weekly on Tuesdays at 07:00 PT.

Phase 2 Timeline

Duration: 6 months (targeting completion by mid-2026)

Note: The timeline is aggressive but achievable with focused scope and dedicated resources and we will continue to be agile/nimble.

Labels

  • cicd