workflow:cost-anomaly-alerting-setup
Cost Anomaly Alerting Setup overview
Designs and implements the cost anomaly detection and alerting infrastructure -- defining anomaly detection thresholds using statistical baselines (standard deviation bands, percentage-over-forecast) calibrated per service and team to minimize false positives, configuring multi-tier alert routing with severity levels mapped to cost impact magnitude (informational, warning, critical), establishing escalation rules that auto-notify team leads for moderate anomalies and trigger incident response for critical spend spikes, integrating anomaly alerts with communication channels (Slack, PagerDuty, email) with appropriate context including affected resources, estimated daily run-rate, and suggested investigation steps, creating anomaly investigation runbooks with common root-cause patterns, setting up weekly anomaly review meetings to tune thresholds and close resolved alerts, and building an anomaly historical log for pattern recognition. Produces alerting architecture document, threshold configuration, escalation matrix, and investigation runbooks. Excludes anomaly remediation.
Attributes
Outgoing edges
- domain:finops·DomainFinOps
- domain:operations·DomainOperations
- role:cloud-architect·RoleCloud Architect
- role:platform-engineer·RolePlatform Engineer
- role:engineering-manager·RoleEngineering Manager
- org-unit:finops-team·OrgUnitFinOps Team
- org-unit:platform-team·OrgUnitPlatform Team
- skill-area:observability-pipeline·SkillAreaObservability Pipeline
- skill-area:sli-slo-management·SkillAreaSLI / SLO Management
- responsibility:respond-incidents·ResponsibilityRespond to production incidents
- responsibility:runbook-authoring·ResponsibilityRunbook authoring