We’ve created a Learning Path to help you understand how to use Codefresh with Lightstep. Codefresh is a great tool for your CI/CD build and deployment pipeline. It’s flexible, fast, and easy to use. But while you may have the act of deploying covered, what happens after a deploy is just as important. Did your app’s performance remain the same? Were any bugs introduced? Instead of gluing yourself to multiple dashboards to “wait and see” and then spend hours trying to find any issues that arise, you can use Lightstep to monitor the deploy for you. And if performance does change, or errors are introduced, Lightstep can help you find those problems quickly.
In this new path, you’ll learn how to:
- Deploy an app using Helm and Codefresh
- Create a
versiontag (known as
attributesin OpenTelemetry) in your instrumentation. Lightstep uses this tag to create a marker to show when deploys take place.
- View the marker in a service involved in the deploy to see performance before and after.
- Create a comparison time period to view differences in latency, find system attributes that show correlation to that latency, and compare operation performance, helping you to pinpoint the issue.
- Confirm your hypothesis.
- Rollback your changes and confirm that issues have been fixed.