You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've discovered that router is being scaled up via a LatencyNotificationAlarm rather than a LatencyScalingAlarm. We should stop using the LatencyNotificationAlarm for this and add a LatencyScalingAlarm instead.
Background
There are usually two latency alarms for each frontend stack:
LatencyNotificationAlarm - for sending alerts to the team.
LatencyScalingAlarm - for activating scaling policies.
We've discovered that router is being scaled up via a
LatencyNotificationAlarm
rather than aLatencyScalingAlarm
. We should stop using theLatencyNotificationAlarm
for this and add aLatencyScalingAlarm
instead.Background
There are usually two latency alarms for each frontend stack:
LatencyNotificationAlarm
- for sending alerts to the team.LatencyScalingAlarm
- for activating scaling policies.For more context @JamieB-gu and @ioannakok can help.
The text was updated successfully, but these errors were encountered: