When you deploy new versions of your services, you always hope for the best but expect the worse. Likely, part of your workflow is to check performance after each deploy. But that means everyone has to remember to do that and then use additional tools to do the monitoring and if there’s an issue, a regression investigation. Switching context like that can be hard. And even then, you may not have enough information to understand what code actually caused that change.

Lightstep can help you by automatically determining if there are changes after a deploy and reporting those changes directly to GitHub so you don’t need to leave your CI/CD workflow. Our Services Change Report GitHub action automatically checks the system health of the current environment once a deploy in GitHub is successful by taking a Snapshot of performance at the time of the deploy and comparing it to the most recent snapshot (or any snapshot you choose) in Lightstep. It let’s you know if there are any latency, error rate, or operation rate issues for each service you’ve configured it to check. It also includes links to downstream dependencies for each service, operations on the service, and traces from the Snapshots, so you can immediately start remediation, right from GitHub.

But this action doesn’t only work in a post-deployment scenario. You can use it anytime you need span data to provide observability information into your committed code. For example, you can configure the action to run whenever a particular label, like bug is added to a GitHub issue. Or, you can configure it to check for violations of your coding best practices!

Check out our new Learning Path for details on how to use our latest action. Services Change Report Learning Path