What's changed: New GH-100 Chapter 5 (monitoring usage & activity = analyze audit logs/API usage, SIEM streaming, admin vs Support triage and diagnostics, usage patterns [adoption/activity/underutilized features]; cost & performance optimization = usage reports for metered products [Actions minutes/storage/Packages/Copilot/GHAS], Actions cost optimization [filters/concurrency/caching/matrix/runner], reclaim unused seats, cut waste without lowering quality)
5.2Optimizing Cost and Performance
Understand interpreting usage reports for metered products and strategies for license and resource optimization—from an admin’s view, balancing cost and performance.
An admin’s job is turning data from monitoring (prior section) into cost and performance optimization. GitHub billing has both seats (licenses) and metered (Chapter 2); leaving waste unchecked balloons cost. GH-100 tests interpreting usage reports and optimization strategies.
5.2.1Usage reports for metered products
Common metered products are GitHub Actions minutes and storage, GitHub Packages storage, and Copilot/GHAS seats/usage. Admins interpret usage reports to see which orgs/repos consume the most cost and the trend (rising). For example, surging Actions minutes often stem from inefficient workflows (wasted runs, oversized matrices, no caching), pinpointing what to fix. Reports also support budgeting and chargeback (departmental allocation).
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.