Find out why a release has no metrics
After a production release, Jaah measures the project's error rate and latency for a short window and compares them with the time before. A release's Metrics tab shows the result. When it shows no numbers, the tab says why in one line, and the reason tells you whether to wait or to change something. How the window works is in How Production QA works.
Before you start: the release run pages are part of Production QA, a plan feature. While your plan does not include it, opening the page of a release shows Not on your plan.
Who can do this: anyone who can view the project.
- Open the release's page. Release runs lists every way in, from the project's pipeline on the Tasks page or from an incident.
- Select the Metrics tab.
- Read the line the tab shows instead of numbers:
- Pending — measured and a time: the window is still open. Come back after that time; the page refreshes every 15 seconds.
- Pending alone: the window has not been set yet, so its end time is not known. Come back later.
- Not measured: and a reason: the window will not run for this release. Go on to the next step.
- If the reason is not a production release, select Overview and check Environment. Only a release to production is measured. A run to a test environment is never measured, and nothing needs fixing.
- If the reason is no monitor with metrics on this project, no monitoring source reports error rate or latency for the project, so Jaah has nothing to compare. A monitoring automation such as the one in Record monitoring alerts as incidents records alerts, but its metrics source can't be set from the automation's page, so ask an engineer to connect one.
- If the tab shows an Error rate or p95 latency section, read its Result, which reads
Not measured: when that metric has no numbers, or its Note when only one side has a value:
- no requests in the post-deploy window or no requests in the baseline window: your monitoring reported no requests in that window, so there is no error rate to compare, such as on a quiet service.
- no latency in the post-deploy window or no latency in the baseline window: your monitoring reported latency for only one of the two windows.
- no data in the window: Jaah recorded no reason for this metric.
- For any other reason, read it as written: it is the note Jaah recorded when it tried to measure.
A release with no metrics can still break production. Check its Probes tab, and its incidents, as in Check whether a release broke production.
Related
- Release runs: every field on the Metrics tab.
- Respond to a regression: when the metrics show a breach.
- Turn on Production QA for a project: connect releases and set the regression limits.