Vincent Behar - Collecting and visualizing Continuous Delivery Indicators
Playback access may have expired or the stream is unavailable. Reload the page to request fresh access.
Another tab is open for this lesson. You can keep watching here; the newest position wins.
Saved position may be approximate: the browser clock disagreed with the server.
Your free preview has ended
Create a free account to finish this lesson, or subscribe for the full library.
Your viewing record
No viewing recorded yet. Press play; your position is saved about every 10 seconds.
Last viewed . Last position —.
Completion
Based on 0:00 of unique watched video. Repeats and skipped parts do not increase it.
CD platforms are a critical part of the development process, and without it, nothing would go to production.
How can we really know what is happening inside, and measure indicators that we can track and improve to ensure a smooth continuous delivery experience?
Based on our experience at Dailymotion, we'll see why Continuous Delivery Indicators are important, how to define them, and then how to collect and visualize them. We'll share which stability and throughput indicators we are tracking, and why.
We'll see how we implemented the collection and visualization of these indicators using open-source tools such as Golang, PostgreSQL, and Grafana.
We'll highlight the importance of Kubernetes-based CD components, such as Jenkins X, Lighthouse, and Tekton, which heavily rely on Kubernetes CRD and thus provide events for everything happening.
We'll also highlight the importance of Gitops-based workflows, where every operation goes through a VCS such as Git, and thus produces more events.
This in turn makes it easy to get notifications for all actions, making our indicators collection process a simple one.
Comments (0)
Log in to join the discussion.
No comments yet. Be the first to comment.