[api-consumption] 📊 GitHub API Consumption Report — 2026-05-03 #29914
Closed
Replies: 2 comments 1 reply
-
|
/q review the prompting of the cache and fix it. This is not the first run, the cache should be present. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
🔧 Pay attention, 007! Q is preparing your gadgets for this discussion comment... |
Beta Was this translation helpful? Give feedback.
-
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #30138. |
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-05-03 · Repository: github/gh-aw · Run: #25277381316
Today at a Glance
🔗 GitHub API Calls Trend (90 days)
This is the first data point in the 90-day history, so a trend line is not yet available. Today's total REST API consumption stands at 10,477 core calls across 60 workflow runs. Future reports will reveal consumption patterns as history accumulates over the coming weeks.
🔗 GitHub API Calls by Workflow Trend (30 days)
With only a single day of history, per-workflow trend lines are not yet available. Today's top API consumer is Safe Output Health Monitor at 1,712 calls, followed by Copilot Session Insights at 1,580 calls. As history builds, we'll be able to identify workflows with consistently high API footprints.
🔗 GitHub REST API Calls Heatmap (90 days)
The heatmap shows today's REST API distribution across the top workflows (fewer than 14 days of history available for a calendar view). Today's activity totalled 10,477 core API calls, with the heaviest consumers being the health monitoring and analytics workflows. Weekly patterns will become visible as tracking continues.
🍩 Top API Burners (24h)
The top 3 workflows account for approximately 43% of total REST API consumption: Safe Output Health Monitor (16.3%), Copilot Session Insights (15.1%), and [aw] Failure Investigator (6h) (12.1%). The concentration in monitoring and investigative workflows suggests these are inherently read-heavy tasks scanning broad repository state.
🔗 GitHub REST API Consumption by Workflow (last 24h)
All workflows are comfortably below the 15,000 calls/hour rate limit — the highest single-run consumer, Safe Output Health Monitor, used only 1,712 calls over ~15 minutes. No immediate optimization pressure, but the Copilot Session Insights and Failure Investigator workflows could benefit from caching repeated API reads if their consumption grows.
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