The following query for the "AutoScaling Groups In-Service Capacity" displays different values depending on different Period chosen. When choosing one day interval from console, the period becomes 5 minutes, which displays a much higher vCPU capacity than actual values.
SEARCH('{AWS/AutoScaling,AutoScalingGroupName} MetricName="GroupInServiceCapacity"', 'Sum', 300)
Removing the period information from the query should fix the issue.
SEARCH('{AWS/AutoScaling,AutoScalingGroupName} MetricName="GroupInServiceCapacity"', 'Maximum')
The goal is to display concurrency at certain time instead of accumulated result over time. Other capacity related widgets havea similar issue in the same dashboard.
Attached are two graphs with different periods (1min and 5 min) during the same time frame of 1 day.
1 minute period
The following query for the "AutoScaling Groups In-Service Capacity" displays different values depending on different Period chosen. When choosing one day interval from console, the period becomes 5 minutes, which displays a much higher vCPU capacity than actual values. SEARCH('{AWS/AutoScaling,AutoScalingGroupName} MetricName="GroupInServiceCapacity"', 'Sum', 300) Removing the period information from the query should fix the issue. SEARCH('{AWS/AutoScaling,AutoScalingGroupName} MetricName="GroupInServiceCapacity"', 'Maximum') The goal is to display concurrency at certain time instead of accumulated result over time. Other capacity related widgets havea similar issue in the same dashboard. Attached are two graphs with different periods (1min and 5 min) during the same time frame of 1 day.
1 minute period