Code and configuration changes are some of the most common causes of performance regressions. While viewing a dashboard after a deployment may show that a latency regression occurred, it won’t explain the root cause. You can look through logs, but unless you know the source of the regression, it may take time to find the issue. This is where Lightstep really shines!
For this Learning Path, let’s say you work on an e-commerce site. You’re responsible for the health of the services closest to your customer. You’ll use Lightstep to monitor those services. When a latency regression is noticed, you’ll pinpoint the cause in a service deep in the stack using Lightstep’s RCA tools.
You’ll learn how to:
- View your services and immediately notice a latency regression.
- Compare service and operation performance before and during the regression.
- Use Lightstep’s Correlations and Operation Diagram to pinpoint the origin of the latency.
- Use the Trace view to confirm the regression source.