You’ve just deployed a change to the service your team owns. Instead of hoping for the best, you want to be able to proactively monitor that service to make sure there’s no degradation in performance, and that no other services are affected. You also want to catch any issues before your customers do. In this Learning Path, you learn how Lightstep Observability can compare performance before and directly after a deploy and then if there is an issue, find the cause quickly.

You’ll learn how to:

  • Create a version attribute in your instrumentation that Lightstep Observability monitors and creates a marker whenever the value changes.
  • View the deployment marker in your service, view performance right after the deploy and compare it to previous deploys to see if there are unexpected issues.
  • When an issue is found, create a comparison time period and view differences in latency, find system attributes that show correlation to that latency, and compare operations’ performance helping you to pinpoint the issue.
  • Confirm your hypothesis