[api-consumption] 📊 GitHub API Consumption Report — 2026-06-21

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-06-21 · Repository: github/gh-aw · Run: #27903036501

---

Today at a Glance

Metric	Value
🤖 Total Runs	197 (176 ✅ / 21 ❌)
🎯 Success Rate	89.3%
🔗 GitHub REST API Calls	844 (core quota consumed) — ⚠️ partial: only 74/197 runs reported core_consumed
📝 Safe-Output Writes	unavailable this run (artifacts not downloaded)
⏱ Avg Duration	568s (p95: 1074s)

⚠️ Data-availability note: Today's GitHub REST API total is a measured floor. Only 74 of 197 runs emitted a github_rate_limit_usage.core_consumed value in their logs; the remaining 123 runs reported no API figure and contribute 0 to the total. The prior day (2026-06-20) reported no API data at all. Treat the day-over-day comparison with caution until log emission of core_consumed is consistent again.

---

🔗 GitHub API Calls Trend (90 days)

Daily REST API consumption is highly volatile across the tracked window, swinging from ~2.4k (2026-06-15) to a one-day peak of 574k on 2026-06-17. Today's measured 844 sits at the very bottom of the range, but this is driven by partial log emission rather than a genuine collapse in activity — run volume (197 runs) remains healthy.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

Over the last 30 days the heaviest, most consistent quota consumers are the Smoke CI, PR Sous Chef, and the various reviewer/sentinel workflows (Test Quality Sentinel, Matt Pocock Skills Reviewer, Design Decision Gate). Consumption is concentrated in a handful of high-frequency CI and PR-automation workflows, while the long tail of daily report agents each contribute only single- to double-digit calls.

---

🔗 GitHub REST API Calls Heatmap (90 days)

The heatmap shows consumption clustering on mid-week weekdays, mirroring developer-driven PR and CI activity. The standout cell is the 2026-06-17 anomaly (>2σ above the mean), which dwarfs every other day and stretches the colour scale; weekend cells are comparatively quiet.

---

🍩 Top API Burners (24h)

API consumption today is spread fairly evenly across CI and PR-automation workflows rather than dominated by a single burner. PR Sous Chef (48 calls) and Issue Monster lead, followed closely by Smoke CI and the Smoke Copilot family. No single workflow exceeds a small fraction of the day's modest total, so there is no concentration risk at these volumes.

---

🔗 GitHub REST API Consumption by Workflow (last 24h)

The top consumers — PR Sous Chef, Issue Monster, and Smoke CI — each sit well under 50 reported calls, far below the 15,000/hr core limit. At today's measured volumes there is no rate-limit pressure. The clearest optimisation opportunity is not call reduction but restoring consistent core_consumed emission so consumption can be measured reliably.

---

Top 10 Workflows by REST API Consumption (last 24h)

Workflow	REST API Calls	Runs	Avg Duration
PR Sous Chef	48	16	466s
Issue Monster	43	4	314s
Smoke CI	36	12	238s
Smoke Copilot	27	3	800s
Smoke Copilot - AOAI (apikey)	26	3	900s
Smoke Copilot - AOAI (Entra)	26	3	990s
Contribution Check	25	4	582s
Smoke Codex	23	3	606s
Smoke Gemini	21	3	322s
Smoke Claude	20	3	698s

---

Trending Indicators

• 7-day API trend: ↑ +47.9% vs. previous 7 days (skewed by the 2026-06-17 spike and partial recent data)
• 30-day API trend: → (insufficient data) — fewer than 60 non-null days of history
• GitHub REST API call rate: ~96,628 calls/day mean over last 7 days (hourly limit: 15,000) — note this mean is heavily inflated by the single 574k-call day; the median day is closer to ~7.4k

---

📦 Cache Memory Status

• Location: /tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl
• Cache restored from previous run: yes (32 entries)
• Collection mode: incremental
• Logs start_date used: -1d
• Data points stored: 33
• Earliest entry: 2026-05-18
• Retention policy: 90 days

---

Automatically generated by the api-consumption-report workflow.

Generated by 📊 GitHub API Consumption Report Agent · 214.9 AIC · ⌖ 37.3 AIC · ⊞ 12.1K · ◷

• expires on Jun 24, 2026, 3:55 AM UTC-08:00