[api-consumption] 📊 GitHub API Consumption Report — 2026-08-12 #52277
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #52479. |
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-08-12 · Repository: github/gh-aw · Run: #31590064907
Today at a Glance
🔗 GitHub API Calls Trend (90 days)
Only 2 days of history are available so far (2026-08-11 and 2026-08-12), so the "90-day" trend currently shows a steep two-point line rather than a full curve — total REST API consumption dropped from ~193K on 08-11 to ~99K on 08-12 (partial day). The 7-day rolling average line is not yet visible since fewer than 7 data points exist. This chart will fill in as the cache accumulates daily entries.
🔗 GitHub API Calls by Workflow Trend (30 days)
The same 5 workflows — PR Sous Chef, Impeccable Skills Reviewer, Design Decision Gate, Matt Pocock Skills Reviewer, and Ponytail Reviewer — are the top consumers on both collected days, each in the 15–22K range on 08-11 dropping to 5–8K on 08-12 (partial day). No multi-week pattern is visible yet with only 2 data points; this view becomes meaningful once 30 days accumulate.
🔗 GitHub REST API Calls Heatmap (90 days)
Fewer than 14 days of history exist, so this defaults to a fallback bar chart of today's top workflows by REST API consumption. PR Sous Chef leads at 15,490 calls, roughly double the next-highest consumer (Impeccable Skills Reviewer at 7,791). The true calendar heatmap will activate automatically once 14+ daily entries are stored.
🍩 Top API Burners (24h)
The top 10 workflows account for 66.7% of today's REST API consumption, with the remaining ~82 workflows collectively contributing the other 33.3% ("other" = 32,920 calls). PR Sous Chef alone represents 15.7% of total consumption — a notable concentration, though not yet at a level that suggests risk given the repo runs 130+ distinct workflows daily.
🔗 GitHub REST API Consumption by Workflow (last 24h)
PR Sous Chef is the top consumer at 15,490 calls per run-day, still comfortably under the 15,000/hr hourly limit reference line when considered as an hourly rate (its 18 runs each average far less than that ceiling individually). No single workflow run is approaching the hourly cap; the aggregate volume comes from breadth (130+ workflows) rather than any one workflow being a runaway consumer.
Top 10 Workflows by REST API Consumption (last 24h)
Trending Indicators
📦 Cache Memory Status
/tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl-90dCollection limitation: log pagination was capped at 2 additional continuation calls per policy (300 runs total collected, ~522 run directories on disk after dedup). Despite requesting a 90-day window, all collected runs fell within 2026-08-11 to 2026-08-12 because this repository runs a very high volume of scheduled workflows (100+ per day), so 300 most-recent runs only span about 2 days. Two transient TLS/permission errors from the logs MCP tool were encountered and resolved via retry (per the bounded-retry policy) before data was successfully collected. Future runs in incremental mode will extend this history one day at a time.
Automatically generated by the api-consumption-report workflow.
All reactions