Project: OpenTelemetry (Observability and Analysis / Observability)
File: ci-cd.md

The goal of this working group is define the semantic conventions for CI/CD Observability and outline a path forward for the OpenTelemetry community. The goal of this project is to establish standard semantic conventions specification for Continuous Integration (CI) and Continuous Delivery (CD) observability. This will provide a common language and standardized formats for CI/CD observability, enabling the community to observe CI/CD systems. This will broaden the target audience of OpenTelemetry to Release Engineering, Platform Engineering, and DevOps teams, further cementing OpenTelemetry as the industry standard Observability framework. The timing is ripe to start now. The has been open since January of 2023 and with the recent changes to the OTEP process, the KubeCon talk, and vendor acknowledgements, there's momentum available to carry this forward. The industry is heavily looking for solutions and watching the related OTEP with interest. The CI/CD observability working group is planning to deliver the with prototypes in the following areas: Only a few technologies are named here, so this is not all encompassing. As we build out these conventions, specifications, and prototypes we'll want to ensure that Observability is done within: The CI system (SCMs like GitHub/GitLab) The tools used within the CI system (Maven/Go) The CD system (SCMs if handling deploys / Keptn / ArgoCD) Current, non-complete list of Deliverables: Semantic Convention Updates Specification Updates (as applicable) Working prototypes are partially available in these systems, but have been done outside of the context of this semantic conventions. Thus these prototypes would be updated based on semantic conventions defined. A related OTEP that is of great interest to the CI/CD OTEP is that of . This OTEP might be driven through other working groups, and isn't the direct focus of this working group, but is has wide arching impacts to enabling distributed tracing in batch systems. As we work to define semantic conventions for CI/CD observability, this OTEP will without a doubt come into play in some form and thus is being listed as related but not a direct deliverable. The following is a list of prototypes, plugins, components, and CI/CD related tooling that attempt to address CI/CD observability in some form. This is not a complete list but can be used for

| Related Vendor | Prototype | Related Resources | Comments | |-|-|-|| | GitHub | | | * Event logs to traces | | GitHub/GitLab | | | * Delivery metrics by scraping Git vendors | | K8S | | | * Focused on observability in Kubernetes deployments | | Jenkins | | | * Tracing of Jenkins pipelines | | Jenkins | | | * Metrics for Jenkins hosts | | CLI | | | * Tracing through a CLI wrapper | | GitHub | | | * Traces via a GitHub action | | GitHub | | | * Metrics on workflow runs | | GitHub | | | * Traces via GitHub action | | GitLab | | | * Tracing in GitLab pipelines | | pytest | | | * Tracing of Python test | | Maven | | | * Tracing of Maven builds | | Ansible | | | * Tracing in Ansible playbooks | | JUnit | | | * Tracing of JUnit test results | | Eiffel | | | * Event protocol for CI/CD observability and interoperability | | CDEvents | | | * Event protocol for CI/CD observability and interoperability | | Tekton | | | * Tekton Task and Pipeline Tracing | @carlosalberto (TC Sponsor) @jsuereth (TC Sponsor) All stages will require a project lead, domain experts, and engineers at a minimum. @horovits Project Lead (Logz.io) @adrielp (Liatrio) @thisthat (Dynatrace, Keptn) @acramsay (Liatrio) @krzko (ANZ Bank) @Elfo404 (Grafana Labs) @dsotirakis (Grafana Labs) @xibz (Apple) @e-backmark-ericsson (Ericsson) @dnsmichi (GitLab) @kamphaus (Jemmic) @magnusbaeck (Axis Communications) @darren17082 (GitLab) @sguyon (GitLab) @kuisathaverat (Elastic) @mhausenblas (AWS, ADOT) @afrittoli (IBM, Tekton, CDEvents) @pmpaulino (Liatrio) @ericchapman80 (Liatrio) @oleg-nenashev (Gradle, Jenkins) @lucavallin (GitHub) Need more: [x] domain experts [x] engineers [x] TCs [ ] potentially maintainers/approvers in the event that we build language specific prototypes This SIG will begin meeting during the regular Monday Semantic Conventions SIG calls that already exists. This group will start meeting independently in the future as the project progresses. Estimated time-frame: 6-12 Months Q1 Focus Kickoff Strategy Research and discovery OTEP Approval Q2 Focus Semantic Conventions Specifications Prototype Developments Q3 TBD Q4 TBD Note: The working groups intent is to be nimble and able to adjust quickly. cicd