OpenTelemetry and CI/CD
- Track: Continuous Integration and Continuous Deployment devroom
- Room: D.cicd
- Day: Sunday
- Start: 15:00
- End: 15:35
- Video with Q&A: D.cicd
- Video only: D.cicd
- Chat: Join the conversation!
If you would like to know more about measuring your CI/CD for troubleshooting or improving your CI/CD services this talk can be interesting for you.
CI/CD at large scale, even at small scale, is hard and might affect your team’s mood, frustration with slow builds, or flakiness in your CI/CD. By using OpenTelemetry for each execution, test, deployment that happens in your CI/CD you can answer questions that are not possible at a glance. The main aim is to reduce the time that developers spend checking log errors, pointing them to the root cause of errors. Filter real verifications errors related to the CI/CD service and third-party systems. Debugging an error is as easy as going to the trace related where all the context information is accessible. In this talk, we want to show you what we have done and learned in the last year since we switched to using distributed traces for the CI/CD and implemented some integrations that help us to leverage our CI/CD.
Speakers
Victor Martinez | |
Ivan Fernandez Calvo |
Links
- OpenTelemetry Documentation
- CI/CD Observability
- Ansible - create distributed traces with OpenTelemetry
- Python - pytest-otel plugin for reporting APM traces of tests executed
- Who Observes the Watchers? An Observability Journey
- Observing the CI/CD in Practice
- Video recording(WebM/VP9)
- Video recording(mp4)
- Chat room (web)
- Chat room (app)
- Hallway chat room (web)
- Hallway chat room (app)
- Submit feedback