[api-consumption] π GitHub API Consumption Report β 2026-05-24 #34414
Replies: 1 comment
-
|
π₯ WHOOSH! π¦ΈβοΈ The Smoke Test Agent zooms in! π₯ KABOOM! π¨ ZAP! β All systems nominal, Claude engine humming, MCP servers firing on all cylinders! β‘ π― BAM! Just dropped by to leave my mark β smoke test run Β§26361248966 was here! π POW! πͺ Onward to the next adventure! π Warning Firewall blocked 6 domainsThe following domains were blocked by the firewall during workflow execution:
network:
allowed:
- defaults
- "accounts.google.com"
- "android.clients.google.com"
- "clients2.google.com"
- "contentautofill.googleapis.com"
- "safebrowsingohttpgateway.googleapis.com"
- "www.google.com"See Network Configuration for more information.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
π GitHub API Consumption Report
Report Date: 2026-05-24 Β· Repository: github/gh-aw Β· Run: #26359504053
Today at a Glance
π GitHub API Calls Trend (90 days)
Daily REST API consumption has fluctuated between 22K and 80K calls/day across the seven days of recorded history. The peak landed on 2026-05-20 (80.1K), and today's 22.3K is the lowest day in the window β the 7-day rolling average (orange dashed) sits near 44K, so today is well below trend.
π GitHub API Calls by Workflow Trend (30 days)
Smoke CI is the most consistent baseline consumer (3Kβ9K/day). Matt Pocock Skills Reviewer, Test Quality Sentinel, and PR Code Quality Reviewer all spiked together on 2026-05-20 to 13Kβ16K each β likely a coordinated PR-batch processing day. Consumption has tapered off in the last 48h with every top-5 workflow now well below the 19.4K combined-average reference line.
π GitHub REST API Calls Heatmap (90 days)
History only spans 7 days so the calendar heatmap falls back to a top-workflow bar view for now. The full heatmap will populate automatically once 14+ days of history are accumulated (~1 week from now).
π© Top API Burners (24h)
The top 10 workflows account for ~57% of today's REST API quota (12.7K of 22.3K), with Smoke CI (12.3%) and PR Sous Chef (9.7%) leading. The long-tail "Other" bucket of 79 workflows still consumes 42.9% combined β concentration risk is moderate, not severe.
π GitHub REST API Consumption by Workflow (last 24h)
No single workflow comes close to the 15K/hr hourly rate-limit ceiling β the heaviest consumer (Smoke CI at 2.8K) sits at ~18% of the per-hour limit, spread across 13 runs. PR Sous Chef (2.2K over 11 runs β 196/run) and Multi-Device Docs Tester (938 in a single ~39min run) are the densest per-run consumers worth profiling if optimisation is needed.
Top 10 Workflows by REST API Consumption (last 24h)
Trending Indicators
π¦ Cache Memory Status
/tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonlAutomatically generated by the api-consumption-report workflow.
Beta Was this translation helpful? Give feedback.
All reactions