aws_rds_cpuutilization_average > 80Managed databases under pressure.
The CloudWatch average, as a series you can alert on.
CloudWatch, Azure Monitor and Google Cloud metrics arrive through the same agent as everything else. Managed queues, databases and load balancers stop being a separate tab and start being part of the request they slow down.
Included on the free tier: 20,000 active series, 50 GB of logs and 50 GB of traces a month. No card.
What you get
| Source | Series | Status |
|---|---|---|
| aws · eu-west-2 | 18,420 | reporting |
| azure · uksouth | 6,110 | reporting |
| gcp · europe-west2 | 4,980 | reporting |
| hosts · self-hosted | 41,300 | reporting |
How it gets there
The cloud receiver runs on an agent you already have and pulls from the provider API.
Assign the cloud receiver to an agent from the portal.
Grant it read access in the provider account.
Cloud metrics land beside your host metrics.
receivers:
awscloudwatch:
region: eu-west-2
namespaces: [AWS/RDS, AWS/SQS, AWS/ApplicationELB]What you can ask
Examples for the metric names shown. Confirm exported names, labels and collection periods before using them in Insights or alerts.
aws_rds_cpuutilization_average > 80The CloudWatch average, as a series you can alert on.
aws_sqs_approximate_number_of_messages_visible_average > 1000Visible messages climbing means consumers are behind.
aws_applicationelb_httpcode_target_5xx_count_sum > 0For CloudWatch Sum values exported per collection period, not cumulative counters. Returns positive counts from the latest reported period with their original labels. Missing data does not mean zero errors.
Questions
Something not here? Talk to an engineer who works on the platform.
Book thirty minutesNo. The cloud receiver runs on an agent you already have and pulls from the provider API with read access you grant it.
20,000 active series, 50 GB of logs and 50 GB of traces a month, 90-day retention, and the whole of Insights.