Learning Path

Use the Services Change Report action to bring observability into GitHub

Use the Lightstep Services Change Report to bring observability data into your CI/CD workflow without having to leave GitHub.

Total time:
Robin Whitmore
Updated Dec 8, 2020
Start

Introduction

Use the Lightstep Services Change Report in your GitHub Action workflow to automatically compare performance of your system before and after a deployment, whenever a GitHub issue is labeled as a bug, and to report on best practice violations.

1
5 mins

Step 1: Create a deployment marker

Register an OpenTelemetry attribute used to mark deployments in Lightstep Observability.

2
5 mins

Step 2: Add the Services Change Report action to your workflow

Add the Lightstep Services Change Report action to your GitHub workflow to take a Snapshot of performance immediately after a deploy and compare it to performance from an earlier point in time.

3
2 mins

Step 3: Use the Services Change Report action in GitHub issues

Use the Lightstep Services Change Report action to take a Snapshot when a specific label is applied to a GitHub issue.

4
5 mins

Step 4: Use the Services Change Report action to report violations

You can use the Services Change Report action to look for and report on violations in committed code.

5
3 mins

Step 5: Integrate Rollbar and PagerDuty with the Services Change Report action

Optionally add Rollbar and PagerDuty to the Lightstep Services Change Report Action.

End

Finished!

End of Learning Path