Optimize Your CI/CD Pipeline with Codefresh & Lightstep
by David Klein
How do you know if the changes that you’re making to your microservices are having the desired impact to your end-users? What happens after a deploy? Did your app’s performance remain the same? Were any bugs introduced? Do you need to roll back?
With Codefresh and Lightstep, you’re able to more quickly, more accurately, and more easily ensure that any commit and build results in a better experience for your end-users.
Learn How to Use Codefresh and Lightstep to Monitor and Rollback Deployments
In five simple steps, we’ll show you how to deploy an app using Helm and Codefresh, and automatically what matters most with Lightstep.
- Create a version tag (known as attributes in OpenTelemetry) in your instrumentation.
- 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.
Dive Deep into the Lightstep and Codefresh integration
In this webinar, you’ll learn how Codefresh’s easy deployments and Lightstep’s observability can combine to allow you to ensure that every new deployment is more performant, more stable, and more robust than your last.
You’ll learn how to easily set up continuous delivery of your code with Codefresh, and how to measure the impact of a deployment in Lightstep. In addition, you’ll see how easy it is to detect regressions and roll back to a healthy and stable state using Lightstep’s Service Health for Deployments.