adam/front-integrations
1
0
Fork 0
mirror of https://github.com/Sea-Haven-Industries/front-integrations.git synced 2026-10-03 05:33:11 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix DynamoDB throttle alarm metric: use Read/WriteThrottleEvents

Browse source 
ThrottledRequests and SystemErrors are not emitted at the TableName-only
dimension (only TableName+Operation), so these table-level alarms would sit
permanently in INSUFFICIENT_DATA and never fire. Replace with
ReadThrottleEvents and WriteThrottleEvents, which AWS/DynamoDB emits at the
TableName dimension.
This commit is contained in:
Adam Moussa 2026-06-17 14:22:04 -04:00
parent efa31783e2
commit 026f8580ef
1 changed files with 13 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
template.yaml
View file

@ -174,18 +174,18 @@ Resources:
- !Sub arn:aws:sns:${AWS::Region}:${AWS::AccountId}:site-alerts - !Sub arn:aws:sns:${AWS::Region}:${AWS::AccountId}:site-alerts
# DynamoDB alarms — front-sla-alerts table # DynamoDB alarms — front-sla-alerts table
# ThrottledRequests and SystemErrors are documented at dimensions # ReadThrottleEvents / WriteThrottleEvents are emitted at the TableName
# (TableName, Operation); CloudWatch also publishes the TableName-only # dimension, so these alarms transition normally. (ThrottledRequests and
# aggregate, which is what we alarm on here. Neither has emitted yet # SystemErrors are only emitted at TableName+Operation granularity, never
# (no throttle/5xx events to date), so the dimension was confirmed against # TableName-only, so alarms on them sit permanently in INSUFFICIENT_DATA
# the AWS DynamoDB metrics reference rather than live data. # and never fire — these are the correct table-level throttle signals.)
AlertsTableThrottleAlarm: AlertsTableReadThrottleAlarm:
Type: AWS::CloudWatch::Alarm Type: AWS::CloudWatch::Alarm
Properties: Properties:
AlarmName: front-sla-alerts-throttled-requests AlarmName: front-sla-alerts-read-throttle
AlarmDescription: front-sla-alerts DynamoDB table is throttling requests AlarmDescription: front-sla-alerts DynamoDB table had one or more read throttle events
Namespace: AWS/DynamoDB Namespace: AWS/DynamoDB
MetricName: ThrottledRequests MetricName: ReadThrottleEvents
Dimensions: Dimensions:
- Name: TableName - Name: TableName
Value: !Ref AlertsTable Value: !Ref AlertsTable
@ -198,13 +198,13 @@ Resources:
AlarmActions: AlarmActions:
- !Sub arn:aws:sns:${AWS::Region}:${AWS::AccountId}:site-alerts - !Sub arn:aws:sns:${AWS::Region}:${AWS::AccountId}:site-alerts
AlertsTableSystemErrorsAlarm: AlertsTableWriteThrottleAlarm:
Type: AWS::CloudWatch::Alarm Type: AWS::CloudWatch::Alarm
Properties: Properties:
AlarmName: front-sla-alerts-system-errors AlarmName: front-sla-alerts-write-throttle
AlarmDescription: front-sla-alerts DynamoDB table returned HTTP 500 system errors AlarmDescription: front-sla-alerts DynamoDB table had one or more write throttle events
Namespace: AWS/DynamoDB Namespace: AWS/DynamoDB
MetricName: SystemErrors MetricName: WriteThrottleEvents
Dimensions: Dimensions:
- Name: TableName - Name: TableName
Value: !Ref AlertsTable Value: !Ref AlertsTable