[api-consumption] 📊 GitHub API Consumption Report — 2026-04-19

[github-actions[bot]]

📊 GitHub API Consumption Report

Report Date: 2026-04-19 · Repository: github/gh-aw · Run: #24641811988

---

Today at a Glance

Metric	Value
🤖 Total Runs	30 (28 ✅ / 2 ❌)
🎯 Success Rate	93.3%
🔗 GitHub REST API Calls	20,255 (core quota consumed — includes reads, writes, and all GitHub API operations)
📝 Safe-Output Writes	23 (issues + PRs + comments + discussions created by safe-output tools)
⏱ Avg Duration	345.4s (p95: 876.0s)

---

🔗 GitHub API Calls Trend (90 days)

This is the first recorded data point for the 90-day trend, establishing a baseline of 20,255 core API calls on 2026-04-19. As history accumulates over coming days, trend direction and patterns will become visible. Future reports will overlay a 7-day rolling average to smooth daily variation.

---

🔗 GitHub API Calls by Workflow Trend (30 days)

With only one day of history, per-workflow trend lines are not yet available — the chart shows today's top-5 workflows as a reference baseline. Daily Code Metrics and Trend Tracking Agent dominates with 8,777 calls, followed by Daily Compiler Quality Check (3,531) and Package Specification Librarian (1,544). These three workflows together account for nearly 68% of today's total consumption.

---

🔗 GitHub REST API Calls Heatmap (90 days)

The heatmap currently shows today's top workflows since only one day of history exists. The calendar heatmap visualization will activate once 14+ days of data are accumulated, revealing day-of-week patterns, weekend quietude, and any anomalous high-consumption days.

---

🍩 Top API Burners (24h)

Daily Code Metrics and Trend Tracking Agent alone consumes 43.3% of today's total REST API quota (8,777 of 20,255 calls), representing significant concentration risk. The top three workflows collectively account for ~68% of all API consumption. The remaining 19 workflows share just 32% of quota, suggesting the top consumers warrant closer attention for optimization opportunities.

---

🔗 GitHub REST API Consumption by Workflow (last 24h)

No workflow is approaching the 15,000/hour limit individually — the top consumer (Daily Code Metrics and Trend Tracking Agent) used 8,777 calls total across its full run. However, if multiple heavy workflows run concurrently, the aggregate hourly rate could spike. Consider staggering scheduled runs for Daily Compiler Quality Check and Daily Code Metrics to spread API load across the day.

---

Top 10 Workflows by REST API Consumption (last 24h)

Workflow	REST API Calls	Runs	Avg Duration
Daily Code Metrics and Trend Tracking Agent	8,777	1	949s
Daily Compiler Quality Check	3,531	1	491s
Package Specification Librarian	1,544	1	397s
Copilot CLI Deep Research Agent	1,511	1	611s
Agentic Workflow Audit Agent	1,510	1	639s
Contribution Check	1,496	1	499s
Go Logger Enhancement	909	1	876s
Smoke CI	200	5	128s
Test Quality Sentinel	181	3	310s
Daily OTel Instrumentation Advisor	127	1	369s

---

Trending Indicators

• 7-day API trend: → N/A (first data point — baseline established today)
• 30-day API trend: → N/A (first data point — baseline established today)
• GitHub REST API call rate: ~844 calls/hour over today's 24h window (hourly limit: 15,000)

---

📦 Cache Memory Status

• Location: /tmp/gh-aw/cache-memory/trending/api-consumption/history.jsonl
• Data points stored: 1
• Earliest entry: 2026-04-19
• Retention policy: 90 days

---

Automatically generated by the api-consumption-report workflow.

Generated by GitHub API Consumption Report Agent · ● 364.1K · ◷

• expires on Apr 22, 2026, 11:42 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by GitHub API Consumption Report Agent.

A newer discussion is available at Discussion #27462.