[api-consumption] 📊 GitHub API Consumption Report — 2026-04-23 #28183
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #28370. |
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-04-23 · Repository: github/gh-aw · Run: #24864171904
Today at a Glance
🔗 GitHub API Calls Trend (90 days)
This is the first data point recorded for this metric (day 1 of history). Today's total of 7,870 core API calls establishes the baseline for future trend analysis. No rolling average is available yet; subsequent daily runs will reveal whether consumption trends up or down from this starting point.
🔗 GitHub API Calls by Workflow Trend (30 days)
With only one day of history available, this chart reflects today's single data point per workflow. Smoke CI dominates with 2,492 core calls across 11 runs, while Copilot CLI Deep Research Agent is the second-largest consumer at 1,487 calls in a single run. As history accumulates, this chart will highlight which workflows are consistently heavy consumers vs. occasional spikes.
🔗 GitHub REST API Calls Heatmap (90 days)
The heatmap is displayed as a fallback bar chart (top workflows by REST API consumption) because fewer than 14 history data points exist. Once 14+ days of history accumulate, a full calendar heatmap will render to show weekly patterns and busy days. Today shows Smoke CI leading consumption with 2,492 calls, well distributed across 11 CI runs throughout the day.
🍩 Top API Burners (24h)
Smoke CI alone consumes 31.7% of today's total REST API quota (2,492 of 7,870 calls), driven by its high run frequency (11 runs). The top 3 workflows — Smoke CI, Copilot CLI Deep Research Agent, and Test Quality Sentinel — together account for 62% of all API consumption. This concentration in CI/quality workflows is expected but worth monitoring as the workflow portfolio grows.
🔗 GitHub REST API Consumption by Workflow (last 24h)
All workflows are well below the 15,000/hr REST API limit — the highest single consumer today (Smoke CI at 2,492 calls) is only 16.6% of the hourly cap. The Smoke CI workflow's frequent runs make it the top API consumer despite relatively modest per-run consumption (~227 calls/run). The Daily Code Metrics and Trend Tracking Agent stands out with the highest per-run duration (1,469s avg) suggesting potential optimization opportunities there.
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