1 個回答
- 最新
- 最多得票
- 最多評論
0
You can use Metrics explorer for this https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Metrics-Explorer.html. Metrics explorer visualizations are dynamic, so if a matching resource is created after you create a metrics explorer widget and add it to a CloudWatch dashboard, the new resource automatically appears in the explorer widget.
已回答 2 年前
相關內容
- 已提問 1 年前
- 已提問 6 個月前
AWS 官方已更新 2 年前- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
Hi Pete, thanks for your reply. It's a good idea to use Metric Explorer with dynamic parameters, but will it be enough? Does this also works for dynamically defined Alarms? Can Metric Explorer define dynamic Alarms for all instances created in the future as well? I think I need to create all the Alarms first before I can use them in the Dashboard (?or not?). I am considering a solution based on CLI commands - e.g. put-metric-alarm, here https://docs.aws.amazon.com/cli/latest/reference/cloudwatch/put-metric-alarm.html. This command would be run (as a shell script) directly on the newly created (Linux) server and creates a new set of Alarms for this new instance. How do you sound this idea? With best regards martin.
P.S. Just to add. This is what the Dashboard of all servers should look like. So far I have prepared it manually, but I would like to automate the change of new records.
https://cloudwatch.amazonaws.com/dashboard.html?dashboard=Servers_Alarms_STATUS&context=eyJSIjoidXMtZWFzdC0xIiwiRCI6ImN3LWRiLTk0NDg5MDE4MjkxNCIsIlUiOiJ1cy1lYXN0LTFfMFR3eXgzczNwIiwiQyI6IjVpNGxydGFrM25sbGphdWJvYzZ1YTZtazFuIiwiSSI6InVzLWVhc3QtMTpiZjRjYzJhNC0yM2I0LTQyZDgtYjg5NC0wNjgzOTFiNjdjZjMiLCJPIjoiYXJuOmF3czppYW06Ojk0NDg5MDE4MjkxNDpyb2xlL3NlcnZpY2Utcm9sZS9DV0RCU2hhcmluZy1QdWJsaWNSZWFkT25seUFjY2Vzcy1BSUY1QjdUWSIsIk0iOiJQdWJsaWMifQ==