The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
After the addition of CloudWatch Cross Account Monitoring you can configure a single datasource to monitor multiple accounts and regions. On dashboards, we can configure variables that query Accounts and Regions. The issue comes when you try to configure alerts. You can't identify from which which account or region an alert is firing, just the dimensions.
For example this query return desired capacity of each ASG:
This query returns the following labels:
With that information we can't identify from which account and region is the resource firing. We would need to manually identify it causing a lot of overhead.
What would you like to be added:
An AccountId label (or any other way that enables us to include the accountid on the alert message).
A region label (or any other way that enables us to include the aws region on the alert message).
Who is this feature for?
This feature is for those who want to have better observability and alerting their cloud resources on multi accounts monitoring setups.
Why is this needed:
After the addition of CloudWatch Cross Account Monitoring you can configure a single datasource to monitor multiple accounts and regions. On dashboards, we can configure variables that query Accounts and Regions. The issue comes when you try to configure alerts. You can't identify from which which account or region an alert is firing, just the dimensions.
For example this query return desired capacity of each ASG:
This query returns the following labels:
With that information we can't identify from which account and region is the resource firing. We would need to manually identify it causing a lot of overhead.
What would you like to be added:
Who is this feature for?
This feature is for those who want to have better observability and alerting their cloud resources on multi accounts monitoring setups.