[api-consumption] 📊 GitHub API Consumption Report — 2026-05-02 #29758
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #29914. |
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-02 · Repository: github/gh-aw · Run: #25250442273
Today at a Glance
🔗 GitHub API Calls Trend (90 days)
This is the first data point recorded for this metric — the 90-day trend chart shows today's baseline of 4,035 REST API calls. As more data accumulates, this chart will reveal daily consumption patterns, peak usage days, and any spikes requiring attention. Today's consumption is well within safe limits (hourly cap: 15,000).
🔗 GitHub API Calls by Workflow Trend (30 days)
With only one day of history, workflow-level trend lines will populate on subsequent runs. Today's top consumer is Daily Documentation Updater (714 calls), closely followed by Smoke Codex (700 calls across 2 runs) and Test Quality Sentinel (546 calls). These three workflows account for roughly 49% of all REST API consumption.
🔗 GitHub REST API Calls Heatmap (90 days)
Insufficient historical data for a full heatmap (requires ≥14 days). The chart shows today's top workflow API consumption as a bar chart instead. Daily, weekly, and monthly activity patterns will become visible as the cache memory accumulates over time. Today is 2026-05-02 (Friday).
🍩 Top API Burners (24h)
Consumption is moderately distributed with no single workflow dominating heavily. Daily Documentation Updater leads with 17.7% of total calls, followed by Smoke Codex (17.3%) and Test Quality Sentinel (13.5%). The top 5 workflows collectively account for ~64% of all REST API consumption, leaving the remaining ~36% spread across 9 other workflows — a reasonably healthy distribution with no concentration risk at this scale.
🔗 GitHub REST API Consumption by Workflow (last 24h)
All workflows are well below the 15k/hour limit — the highest single-workflow consumer (Daily Documentation Updater at 714) is just ~4.8% of the hourly cap. Smoke Codex and Smoke Claude show the highest per-run API usage among smoke tests, suggesting those environments make more GitHub API calls during testing. No immediate optimisation is required, but monitoring Daily Documentation Updater and smoke test workflows over time is advisable.
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