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

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-06-04 · Repository: github/gh-aw · Run: #26949404310

---

Today at a Glance

Metric	Value
🤖 Total Runs	127 (112 ✅ / 13 ❌)
🎯 Success Rate	89.6%
🔗 GitHub REST API Calls	76,247 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	64 (issues + PRs + comments + discussions created by safe-output tools)
⏱ Avg Duration	514s (p95: 1160s)

i️ Today's window is a partial day (UTC) covering the 127 most recent runs returned before the log-collection timeout.

---

🔗 GitHub API Calls Trend (90 days)

Daily REST API consumption has been volatile across the 17-day window, swinging between ~17k and a peak of 118,077 calls on 2026-05-27. The 7-day rolling average has cooled to ~43k/day, and today's 76,247 sits above that mean but well short of the late-May spike. No sustained upward drift is visible — the series is spiky rather than trending.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

Smoke CI is the most consistent heavy consumer day over day, reflecting its high run frequency (push-triggered CI). Daily report-style workflows (spellcheck, blog writer, A/B advisor) appear in bursts tied to their scheduled cadence rather than as steady baselines. Most other workflows contribute small, intermittent quota draws.

---

🔗 GitHub REST API Calls Heatmap (90 days)

The heatmap shows consumption concentrated on weekdays, with the standout being the 2026-05-27 cell driving the darkest band. Weekend cells are markedly lighter, consistent with fewer push/PR events triggering CI and review workflows. No anomalous off-hours cluster stands out beyond the single late-May spike.

---

🍩 Top API Burners (24h)

Smoke CI alone accounts for 25.0% of today's REST API quota, and the top three workflows together make up 39.3% — a moderate concentration. The long tail of smaller workflows each contributes only single-digit-percent shares, so optimisation effort is best aimed at the top handful.

---

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

The top consumer today is Smoke CI at 19,045 calls across 13 runs. No single run approached the 15,000/hr core limit — the dashed reference line reflects the hourly cap, while the bars are full-day totals, so per-workflow daily sums above 15k (Smoke CI) are expected and not a throttling risk. Smoke CI's per-run footprint (~1,465 calls/run) is the clearest optimisation target given its frequency.

---

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

Workflow	REST API Calls	Runs	Avg Duration
Smoke CI	19,045	13	172s
PR Description Updater	6,410	4	374s
Daily AstroStyleLite Markdown Spellcheck	4,546	3	440s
Daily Agent of the Day Blog Writer	4,333	3	424s
GPL Dependency Cleaner (gpclean)	3,698	1	277s
AI Moderator	2,579	3	1244s
PR Sous Chef	2,451	7	544s
Daily A/B Testing Advisor	2,333	2	542s
Agent Persona Explorer	2,192	1	478s
Contribution Check	1,676	3	539s

---

Trending Indicators

• 7-day API trend: ↓ -14.8% vs. previous 7 days
• 30-day API trend: → (insufficient data) vs. prior 30 days
• GitHub REST API call rate: 43,021 calls/day over last 7 days (hourly limit: 15,000)

---

📦 Cache Memory Status

• Location: /tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl
• Cache restored from previous run: yes (16 entries)
• Collection mode: backfill (start_date=-90d requested; the 120s log-bridge cap returned the 127 most recent runs, all dated 2026-06-04, so no older gaps were backfilled)
• Logs start_date used: -90d
• Data points stored: 17
• Earliest entry: 2026-05-18
• Retention policy: 90 days

---

Automatically generated by the api-consumption-report workflow.

Generated by 📊 GitHub API Consumption Report Agent · opus48 13.8M · ◷

• expires on Jun 7, 2026, 11:56 AM UTC

[github-actions[bot]]

This discussion has been marked as outdated by GitHub API Consumption Report Agent.

A newer discussion is available at Discussion #37105.