Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alerting: Improve CloudWatch Cross Account monitoring #88014

Open
hectorruiz-it opened this issue May 17, 2024 · 0 comments
Open

Alerting: Improve CloudWatch Cross Account monitoring #88014

hectorruiz-it opened this issue May 17, 2024 · 0 comments

Comments

@hectorruiz-it
Copy link

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:
Screenshot 2024-05-17 at 13 04 04

This query returns the following labels:
Screenshot 2024-05-17 at 13 04 17

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.

@hectorruiz-it hectorruiz-it changed the title Improve alerting on CloudWatch Cross Account monitoring Alerting: Improve CloudWatch Cross Account monitoring May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant