[api-consumption] 📊 GitHub API Consumption Report — 2026-04-17 #26957
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #27113. |
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-04-17 · Repository: github/gh-aw · Run: #24591215589
Today at a Glance
🔗 GitHub API Calls Trend (90 days)
This is the first day of tracking, establishing a baseline of 10,713 core API calls across 17 workflow runs. With only one data point, no trend direction can be determined yet — future days will reveal weekly patterns and any consumption growth. The 7-day rolling average will become meaningful as history accumulates over the coming week.
🔗 GitHub API Calls by Workflow Trend (30 days)
On this first tracking day, Test Quality Sentinel (5,392 calls) and Design Decision Gate (4,213 calls) together account for over 89% of total REST API consumption. Both workflows run multiple times per day, making them the dominant API consumers to watch. The 30-day trend chart will mature meaningfully within the next week.
🔗 GitHub REST API Calls Heatmap (90 days)
As this is the inaugural report, the heatmap shows today's per-workflow breakdown (fallback view — full calendar heatmap requires ≥14 days of history). Today's total of 10,713 calls sits comfortably below GitHub's 15,000-call/hour core limit, indicating healthy headroom. Weekly and monthly patterns will emerge once at least two weeks of data are stored.
🍩 Top API Burners (24h)
Test Quality Sentinel (50.3%) and Design Decision Gate (39.3%) dominate today's API footprint, together consuming ~90% of all core quota. The concentration in just two workflows represents a potential risk — if either experiences a run spike, the hourly limit could be approached. The Daily Safe Output Integrator (10.1%) rounds out the top three.
🔗 GitHub REST API Consumption by Workflow (last 24h)
No workflows approached the 15,000-call/hour limit today — the highest single-workflow consumer was Test Quality Sentinel at 5,392 calls across 6 runs (~899 calls/run average). The distribution is healthy, though the concentration in two workflows warrants monitoring as run frequency scales. Consider reviewing whether Test Quality Sentinel can be optimized with caching or conditional API calls to reduce per-run quota consumption.
Top 10 Workflows by REST API Consumption (last 24h)
Trending Indicators
📦 Cache Memory Status
/tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonlReferences:
Automatically generated by the api-consumption-report workflow.
Beta Was this translation helpful? Give feedback.
All reactions