You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
⚠️Data quality notice: Log collection this run hit the MCP logs tool's count limit after the allowed 2 continuation pages, so it did not reach the requested 90-day backfill window and left an internal gap. Of 379 downloaded run directories, 300 parsed successfully (79 lacked run_summary.json and were skipped). The collected data covers only 2026-08-19, 2026-08-20, and a 2-run sliver of 2026-08-25 newly, plus two pre-existing cached days (2026-08-22, 2026-08-23) — 2026-08-21 and 2026-08-24 have zero collected runs. All figures below are accurate for the data actually collected, but trends should be read with this gap in mind rather than as a clean continuous series.
Today at a Glance
Metric
Value
🤖 Total Runs (last 24h)
2 (2 ✅ / 0 ❌)
🎯 Success Rate
100.0%
🔗 GitHub REST API Calls
245 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes
1 (issues + PRs + comments + discussions created by safe-output tools)
⏱ Avg Duration
417.0s (p95: 448.5s)
The "last 24h" window contains only 2 runs (up to 10:46 UTC on 2026-08-25), so this snapshot is thin and not representative of a typical day's volume — see the daily trend below for fuller days.
🔗 GitHub API Calls Trend (partial window)
Daily totals swing widely across the 5 collected days — 62,338 (08-19) → 198,537 (08-20) → 88,680 (08-22) → 290,274 (08-23) → 245 (08-25, partial) — but this reflects gaps in collection coverage, not a real usage trend. 2026-08-21 and 2026-08-24 have no data at all, and are shown as breaks in the line rather than interpolated. No reliable trend direction can be claimed from this window.
🔗 GitHub API Calls by Workflow Trend
Across the days with data, PR Sous Chef is consistently the dominant consumer of REST API quota, far ahead of any other workflow. The chart groups the next several workflows individually and buckets the long tail as "Other"; with only 3 non-contiguous days of per-workflow data, this should be treated as directional, not a stable 30-day pattern.
🔗 GitHub REST API Calls Heatmap
Only 20 of 168 day-of-week × hour-of-day buckets have any collected data (rendered distinctly gray vs. the blue scale for real values), concentrated around 2026-08-19/08-20. Within that narrow slice, the heaviest hour recorded ~46,856 calls. No weekly pattern can be inferred from this partial slice.
🍩 Top API Burners (24h)
Based on just 2 runs: PR Sous Chef accounts for ~98% (239 of 245) of last-24h REST API calls, with Daily Documentation Updater making up the remainder (6 calls). This is too small a sample to represent typical concentration risk — treat as anecdotal until a fuller day is captured.
🔗 GitHub REST API Consumption by Workflow (last 24h)
The same two workflows dominate this thin slice; neither is anywhere near the 15,000/hour rate limit individually. No optimisation action is warranted from this sample alone — revisit once a full day of contiguous data is available.
Top 10 Workflows by REST API Consumption (last 24h)
Workflow
REST API Calls
Runs
Avg Duration
PR Sous Chef
239
1
452.0s
Daily Documentation Updater
6
1
382.0s
Trending Indicators
7-day API trend: → insufficient data (history has only 5 non-contiguous days; no full prior-7-day baseline exists yet)
30-day API trend: → insufficient data (same reason — history-tracking only started 2026-08-19)
GitHub REST API call rate: ~128,015 calls/day averaged over the 5 days with data (640,074 total ÷ 5 days) — not a true 7-day rate, since 2 of the last 7 calendar days have zero collected runs (hourly limit: 15,000)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
📊 GitHub API Consumption Report
Report Date: 2026-08-25 · Repository: github/gh-aw · Run: #32839438007
Today at a Glance
The "last 24h" window contains only 2 runs (up to 10:46 UTC on 2026-08-25), so this snapshot is thin and not representative of a typical day's volume — see the daily trend below for fuller days.
🔗 GitHub API Calls Trend (partial window)
Daily totals swing widely across the 5 collected days — 62,338 (08-19) → 198,537 (08-20) → 88,680 (08-22) → 290,274 (08-23) → 245 (08-25, partial) — but this reflects gaps in collection coverage, not a real usage trend. 2026-08-21 and 2026-08-24 have no data at all, and are shown as breaks in the line rather than interpolated. No reliable trend direction can be claimed from this window.
🔗 GitHub API Calls by Workflow Trend
Across the days with data, PR Sous Chef is consistently the dominant consumer of REST API quota, far ahead of any other workflow. The chart groups the next several workflows individually and buckets the long tail as "Other"; with only 3 non-contiguous days of per-workflow data, this should be treated as directional, not a stable 30-day pattern.
🔗 GitHub REST API Calls Heatmap
Only 20 of 168 day-of-week × hour-of-day buckets have any collected data (rendered distinctly gray vs. the blue scale for real values), concentrated around 2026-08-19/08-20. Within that narrow slice, the heaviest hour recorded ~46,856 calls. No weekly pattern can be inferred from this partial slice.
🍩 Top API Burners (24h)
Based on just 2 runs: PR Sous Chef accounts for ~98% (239 of 245) of last-24h REST API calls, with Daily Documentation Updater making up the remainder (6 calls). This is too small a sample to represent typical concentration risk — treat as anecdotal until a fuller day is captured.
🔗 GitHub REST API Consumption by Workflow (last 24h)
The same two workflows dominate this thin slice; neither is anywhere near the 15,000/hour rate limit individually. No optimisation action is warranted from this sample alone — revisit once a full day of contiguous data is available.
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.
All reactions