[api-consumption] 📊 GitHub API Consumption Report — 2026-08-17 #53354
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #53645. |
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-17 · Repository: github/gh-aw · Run: #32022153663
Today at a Glance
🔗 GitHub API Calls Trend (90 days)
History currently holds only 2 daily data points (2026-08-16 and 2026-08-17), so no real multi-day trend exists yet — the chart is annotated accordingly and rolling averages are suppressed. Total REST calls rose from 112,848 (08-16) to 325,281 (08-17), but that jump likely reflects the 24h collection window overlapping more fully with 08-17 rather than a genuine consumption spike; more days of history are needed before drawing conclusions.
🔗 GitHub API Calls by Workflow Trend (30 days)
With only 2 days on record, per-workflow trend lines are similarly provisional. PR Sous Chef is already the clear leader on both days (32,711 calls / 25 runs on 08-16, growing to 52,550 calls / 50 runs on 08-17), consistent with it being the single largest API consumer overall.
🔗 GitHub REST API Calls Heatmap (90 days)
The heatmap is necessarily sparse (2 of 90 possible days populated) and carries an explicit "limited history" note. No weekly pattern can be inferred yet — this fills in as the cache accumulates daily runs.
🍩 Top API Burners (24h)
PR Sous Chef alone accounts for ~16% of today's 325,281 total REST calls (52,550 calls). The top 10 named workflows together make up ~62% of consumption; the remaining ~38% (122,442 calls) is spread across 128 lower-volume workflows, so concentration risk sits primarily with a handful of high-frequency PR/review agents rather than a single outlier.
🔗 GitHub REST API Consumption by Workflow (last 24h)
PR Sous Chef (52,550 calls / 50 runs) and Ponytail Reviewer (20,688 calls / 14 runs) lead consumption. None of the individually-tracked workflows are close to the 15,000/hr per-workflow rate limit on a per-run basis, but PR Sous Chef's high run frequency (50 runs/day) makes it worth watching if run cadence increases further.
Top 10 Workflows by REST API Consumption (last 24h)
(128 additional workflows, 155 runs, 122,442 combined calls, are grouped into "other" and not itemized here.)
Trending Indicators
📦 Cache Memory Status
/tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonlKnown limitation: This is the first run of this report. The
logsMCP tool's pagination was bounded to 3 total batches (1 initial + 2 continuation calls) per the workflow's retry policy, and the returned runs were concentrated in the most recent ~48 hours rather than spanning the full 90-day backfill window requested. As a result, all "trend" charts and indicators above are based on only 2 daily data points and should be treated as provisional. Subsequent daily runs will accumulate more history automatically, and trends will become meaningful once ~14+ days of data are on record.Automatically generated by the api-consumption-report workflow.
All reactions