Are you tired of looking at metrics and logs after each deployment? Do you learn about failed deployments from unhappy customers? Did you always want to deploy on Friday afternoon and go straight to the pub? Many teams perform “blind” deployments without any real insight into what will be affected by the new application version. Consequently, they don’t have enough data to understand the blast radius of a release and whether to decide if it was successful or not. Even companies that have several metrics in place, don’t always use them in an automated manner. Wouldn’t it be great if you could see user behavior with new features in real time and identify performance bottlenecks before a full release?
In this talk, we will focus on common scenarios regarding Argo Rollouts and observability metrics, we will explain:
- Minimum requirements in terms of tools and metrics/traces/logs
- Well-known observability use cases
- Common automation pitfalls
- RED/USE metrics tradeoffs
