You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We’ve been talking about the need for a common “language” for reporting and
16
16
observing CI/CD pipelines for years, and finally, we see the first “words” of
17
-
this language entering the “dictionary” of observability—the [OpenTelemetry open
18
-
specification](/docs/specs/otel/). With the recent release of OpenTelemetry’s [Semantic Conventions](/docs/specs/semconv/),
19
-
v1.27.0, you can find
17
+
this language entering the “dictionary” of observability—the
18
+
[OpenTelemetry open specification](/docs/specs/otel/). With the recent release
19
+
of OpenTelemetry’s [Semantic Conventions](/docs/specs/semconv/), v1.27.0, you
20
+
can find
20
21
[designated attributes for reporting CI/CD pipelines](/docs/specs/semconv/attributes-registry/cicd/).
21
22
22
23
This is the result of the hard work of the
@@ -277,7 +278,9 @@ Want to learn more? Want to get involved in shaping CI/CD Observability?
277
278
278
279
We invite developers and practitioners to participate in the discussions,
279
280
contribute ideas, and help shape the future of CI/CD observability and the
280
-
OpenTelemetry semantic conventions. Discussion takes place in the [CNCF Slack](https://slack.cncf.io/)
281
-
workspace under the #cicd-o11y channel, and you can chime in on any of the
282
-
GitHub issues mentioned throughout this article and join
283
-
the CICD SIG [weekly calls](https://calendar.google.com/calendar?cid=Z29vZ2xlLmNvbV9iNzllM2U5MGo3YmJzYTJuMnA1YW41bGY2MEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t) every Thursday at 0600 PT.
281
+
OpenTelemetry semantic conventions. Discussion takes place in the
282
+
[CNCF Slack](https://slack.cncf.io/) workspace under the #cicd-o11y channel, and
283
+
you can chime in on any of the GitHub issues mentioned throughout this article
0 commit comments