Alerts & monitoring

One scan tells you what is wasteful today. Monitoring is what keeps the answer true next month, because cloud waste is not a one-off cleanup job: an instance spun up for a load test stays up, a volume outlives the instance it belonged to, a log group starts retaining everything forever after someone changes a default. Parsivex re-scans on a schedule and tells you when something new appears, so you are not relying on remembering to check.

These articles cover both halves of that. The scan schedule article explains when recurring scans run and how much control you have over the timing on your plan. The monitoring alerts article covers the notification you get after a re-scan — what counts as new waste worth telling you about, and which channels carry it. Slack setup is covered separately: you create an incoming webhook in your workspace, paste it into Parsivex, and alerts land in the channel your team already watches.

Cost anomaly alerts work on a different signal. Rather than waiting for the next scan, they check each AWS service daily against its recent baseline and flag sudden spikes, which is how you catch a runaway job or a misconfiguration days before it shows up on an invoice. The article below explains the thresholds that separate a real spike from ordinary variation, how alerts are deduplicated so one anomaly does not notify you twice, and how to review and acknowledge them in your alerts inbox.