Setting the file. One moment.
Subchapter 7.56
references/support-topics/usage-spike-triage.mdMarkdown1018 BView on GitHub
A single-day or single-SKU spike needs cause before fix. Branches: bot or AI crawler on a cacheable route, viral moment, pricing-model migration, or code regression.
Confirm SKU and day from usage.breakdown.data. Cross-check firewall/bot data, traffic curve, SKU rename timing, and deploy log around the spike day. Spend Management and Alerts are monitoring tools; they do not replace finding the traffic or deploy cause.
Do not propose a code fix until the branch is identified. Do not rate-limit a viral moment or revert a deploy for third-party crawler traffic.
Name SKU, day, value, window mean, branch, and one supporting datum.