Product Guides
Releases
Use Releases to compare deployments and versions with the timing of latency, errors, logs, traces, alerts, and issues.
Overview
Use Releases to connect behavior changes to deployments and versions. Releases are correlation context; traces, logs, errors, and runtime decide whether the release is actually involved.
Use this page after you know the approximate symptom and need to decide which evidence should come next. Keep the service, environment, and time range consistent as you move from summary pages to request-level detail.
How to read this page
Use release timing as a correlation signal, then confirm with service evidence. Compare before and after windows for the same service and environment. Use deployment or version context in Logs, Traces, Errors, and Issues.
- Timing
- A release is relevant when symptoms start near the deployment window.
- Service and version
- The affected service and version decide which change to inspect.
- Before and after
- Compare the same route, service, and environment before and after the release.
Investigation workflow
Use this sequence when you need to move from a broad symptom to evidence you can share with another teammate.
- 1
Open Releases when a spike appears near deploy time.
- 2
Pick the service and version that line up with the symptom.
- 3
Use service detail, traces, logs, and issues to confirm whether the release changed behavior.
Interpretation note
Do not blame the closest release without request evidence. Do not compare different environments when reviewing a release. Do not ignore partial rollouts or mixed versions when reading traces and logs.