Skip to content

A complete AI agency at your fingertips - From frontend wizards to Reddit community ninjas, from whimsy injectors to reality checkers. Each agent is a specialized expert with personality, processes, and proven deliverables.

Shell

Point the DevOps CPU alarm at the actual EC2 metric

Rudy Celeklib02fa83e4c95
diff --git a/engineering/engineering-devops-automator.md b/engineering/engineering-devops-automator.md
index a9e7cac0..e7c6daa1 100644
--- a/engineering/engineering-devops-automator.md
+++ b/engineering/engineering-devops-automator.md
@@ -171,15 +171,23 @@ resource "aws_cloudwatch_metric_alarm" "high_cpu" {
comparison_operator = "GreaterThanThreshold"
evaluation_periods = "2"
metric_name = "CPUUtilization"
- namespace = "AWS/ApplicationELB"
- period = "120"
+ namespace = "AWS/EC2"
+ dimensions = {
+ AutoScalingGroupName = aws_autoscaling_group.app.name
+ }
+ # Matches EC2 basic monitoring's five-minute publication interval.
+ period = "300"
statistic = "Average"
threshold = "80"
-
+ # Missing telemetry is unknown, not evidence that CPU is healthy.
+ treat_missing_data = "missing"
+
alarm_actions = [aws_sns_topic.alerts.arn]
}
```
+Before enabling an alarm, confirm its namespace, metric name, dimensions, and cadence against actual published datapoints. `CPUUtilization` belongs to [AWS/EC2](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/viewing_metrics_with_cloudwatch.html), and `AutoScalingGroupName` selects this application's instances. `AWS/ApplicationELB` publishes load-balancer metrics, not instance CPU. Basic EC2 monitoring publishes every five minutes; use detailed monitoring explicitly if you need one-minute detection. Treat missing data as unknown and monitor telemetry loss separately.
+
### Monitoring and Alerting Configuration
```yaml
# Prometheus Configuration