[api-consumption] 📊 GitHub API Consumption Report — 2026-04-27 #28822
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by GitHub API Consumption Report Agent. A newer discussion is available at Discussion #29006. |
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-27 · Repository: github/gh-aw · Run: §25025367546
Today at a Glance
🔗 GitHub API Calls Trend (90 days)
This is the first recorded data point for this report — 23,457 REST API calls were consumed today across 34 workflow runs. The trend chart will show meaningful patterns after multiple days of data collection. Today's baseline will serve as the reference point for future trend analysis.
🔗 GitHub API Calls by Workflow Trend (30 days)
With only one day of history, per-workflow trend lines aren't yet available — the chart shows today's top consumers as a bar chart instead. The Daily Compiler Quality Check (7,232 calls), Agentic Workflow Audit Agent (5,867 calls), and Go Logger Enhancement (5,013 calls) are the dominant consumers, together accounting for ~77% of total REST API quota. These patterns will become clearer as history accumulates.
🔗 GitHub REST API Calls Heatmap (90 days)
The calendar heatmap requires at least 14 days of history to be meaningful — today's fallback bar chart confirms the Compiler Quality Check, Audit Agent, and Logger Enhancement as the primary REST API consumers. Weekly and daily patterns will emerge in the heatmap after sufficient data is collected.
🍩 Top API Burners (24h)
Three workflows dominate the 24-hour API footprint: Daily Compiler Quality Check (30.8%), Agentic Workflow Audit Agent (25.0%), and Go Logger Enhancement (21.4%), collectively consuming 77.2% of all REST API quota. This high concentration in three single-run workflows suggests that bursty, deep-analysis tasks drive the majority of API consumption. Monitoring these three workflows for optimization opportunities would yield the greatest quota savings.
🔗 GitHub REST API Consumption by Workflow (last 24h)
The top REST API consumer today is Daily Compiler Quality Check at 7,232 calls — well below the 15,000/hour limit on its own, suggesting no immediate rate-limiting risk. The Agentic Workflow Audit Agent at 5,867 calls and Go Logger Enhancement at 5,013 calls are both single-run, long-running workflows; caching or pagination optimizations in these could meaningfully reduce quota consumption.
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