[api-consumption] π GitHub API Consumption Report β 2026-05-21 #33747
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #33986. |
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-21 Β· Repository: github/gh-aw Β· Run: #26223959308
Today at a Glance
π GitHub API Calls Trend (90 days)
The trend window is still ramping up β only 4 days of history are stored (2026-05-18 through today). Daily REST quota consumption has grown sharply across that span, from ~20K calls on May 18 to 87.5K today. Today is the highest-consumption day on record, surpassing the previous May 20 high (80.1K) by roughly 9%.
π GitHub API Calls by Workflow Trend (30 days)
The top REST consumers over the last 30 days are PR review and CI workflows: Test Quality Sentinel, PR Code Quality Reviewer, Matt Pocock Skills Reviewer, Design Decision Gate, and Smoke CI dominate the chart. These five collectively account for the majority of daily REST consumption and their per-day footprints have all increased from May 18 to May 21.
π GitHub REST API Calls Heatmap (90 days)
Heatmap is in fallback (bar) mode because fewer than 14 days of history are stored β the chart shows today's top API consumers as a stand-in. As the trending dataset grows past two weeks, the calendar heatmap will replace this view automatically.
π© Top API Burners (24h)
The four PR-review workflows (Test Quality Sentinel, PR Code Quality Reviewer, Design Decision Gate, Matt Pocock Skills Reviewer) plus Smoke CI account for roughly 65% of all REST traffic in the last 24h. This is a meaningful concentration β any single one of these going into a tight loop could push the org close to its hourly cap. The remaining workflows in the "other" slice are each below 3K calls.
π GitHub REST API Consumption by Workflow (last 24h)
The leading consumer (Test Quality Sentinel, 14.3K) is comfortably below the 15K hourly REST limit but only because that figure is spread across 20 runs (~720 calls per run). Workflows triggered by PRs scale linearly with PR volume, so optimisation work should target the top 4 (
get/listreductions, response caching, conditional requests) to free headroom for new workflows.Top 10 Workflows by REST API Consumption (last 24h)
Trending Indicators
π¦ Cache Memory Status
/tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonlstart_dateused: -90d (and follow-up windows -7d, -14d, -30d after timeouts)Notes: the
-90dlogs request from the agentic-workflows MCP timed out at 120s; partial data was harvested from incremental windows (-7d, -14d, -30d). The history now spans 2026-05-18 β 2026-05-21.Automatically generated by the api-consumption-report workflow.
Beta Was this translation helpful? Give feedback.
All reactions