Deploys
Deploy reports
Comparison windows, metrics, and verdicts for deploy reports.
kogut writes a report 70 min after each deploy, comparing the hour before with minutes 10 to 70 after. When the tracker sends the app version, the web metrics compare the previous version with the deployed one instead.
Reports appear on the service timeline, in incident timelines that include them, in the
daily summary count, and through the deploy_report and timeline
MCP tools. They do not go to notification channels.
Metrics
A metric missing on either side is omitted. Metrics below the minimum are marked “not enough data”.
| Metric | Source | Minimum on each side |
|---|---|---|
| Failed check runs as a share of judged runs | Service checks, excluding heartbeats | 1 judged run |
| Response time p50 and p95 | Service checks | 20 measured runs |
| JavaScript errors per page view | Service sites | 1 page view |
| LCP, INP, CLS, FCP, and TTFB p75 per site | Service sites | 200 page views across the service |
| Mean CPU and memory per host | Service hosts | 10 minutes of agent data |
Each metric says what it compared: window for the hour before against minutes 10 to 70
after, version for the previous app version against the deployed one.
Reports also list up to 20 JavaScript error groups per site first seen within 70 min after the deploy, with their counts. These groups do not affect the verdict.
Verdicts
A metric changes only when the difference exceeds 10% of its previous value. Any non-zero value counts as a relative change from zero. Failed check and JavaScript error rates also require a two-proportion test at 95% confidence.
| Verdict | Meaning |
|---|---|
worse | At least one metric worsened. The timeline event is a warning. |
better | No metric worsened and at least one improved. |
no notable change | No metric improved or worsened, including when data is insufficient. |
inconclusive | Another deploy of the same service occurred within the following 70 min, and no metric compared app versions. |
After such a second deploy, only the metrics compared by app version decide the verdict, since the windows mix both deploys. The later deploy gets its own report. After a restart, kogut schedules missing reports for deploys from the last 3 h.
By app version
With data-version on the tracking
script, a deploy whose version visitors run gets its JavaScript errors per page view and
Web Vitals compared by version:
- the deployed version: its events from the deploy to 70 min after;
- the previous version: the version with the most page views in the hour before the deploy, with its events from that hour to 70 min after.
The minimums above apply to each version. Visitors whose browser still runs the previous
build count towards the previous version. The report is titled with both versions, such as
Deploy report for api 1.4.2 vs 1.4.1, and lists them in versions.
Without page views of either version, the web metrics compare the windows. Failed checks, response times, CPU and memory always compare the windows.
Deploys from container images
A deploy noticed from a new container image gets no report when CI announced the same service within 10 min of it.