[api-consumption] π GitHub API Consumption Report β 2026-06-15 #39373
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #39546. |
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-06-15 Β· Repository: github/gh-aw Β· Run: #27547247567
Today at a Glance
π GitHub API Calls Trend (90 days)
REST API consumption swings widely day to day, oscillating around a ~50k/day baseline. The standout is Jun 09 (207,880 calls), flagged as a >2Ο anomaly β roughly 4Γ the 30-day rolling average. Today's 2411 calls sit well below the band, marking the quietest day in the recorded window.
π GitHub API Calls by Workflow Trend (30 days)
A handful of workflows dominate quota over the trailing 30 days, with consumption concentrated in scheduled high-frequency jobs (Smoke CI, PR Sous Chef) and periodic heavy analysers. Day-to-day spikes are typically driven by a single workflow having an outsized run rather than broad increases across the fleet.
π GitHub REST API Calls Heatmap (90 days)
The weekday Γ ISO-week heatmap shows consumption is fairly evenly spread across weekdays, with no strong weekend dip β consistent with
schedule-driven automation rather than human activity. The brightest cell aligns with the Jun 09 spike; surrounding cells are comparatively muted.π© Top API Burners (24h)
PR Description Updater alone accounts for 32% (765 calls) of today's REST quota in a single run, followed by AI Moderator (14%, 336 calls across 10 runs). The top 3 workflows consume over half the daily total β a moderate concentration worth watching but not yet a quota risk given the low absolute volume.
π GitHub REST API Consumption by Workflow (last 24h)
The top consumer (PR Description Updater) used 765 core calls in one run; no workflow came close to the 15,000/hr core limit today. The single-run, high-call profile of PR Description Updater is the clearest optimisation candidate β worth checking whether its description-generation loop is making redundant reads.
Top 10 Workflows by REST API Consumption (last 24h)
Trending Indicators
π¦ Cache Memory Status
/tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl-90dbackfill download timed out at the MCP layer; a follow-up-1dcollection completed and captured 108 runs with validrun_summary.jsonfor today.run_summary.json(incomplete artifact download) and were excluded β today's totals may be a slight undercount.Automatically generated by the api-consumption-report workflow.
Beta Was this translation helpful? Give feedback.
All reactions