generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 82
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Version
5.10.4
Steps and/or minimal code example to reproduce
Given two dynamo tables, each with identically named GSIs, adding alarms (such as addReadThrottledEventsCountAlarm
) will create a construct id name collision:
Error: There is already a Construct with name '<globalPrefix>-<GSIName>-Throttled-Events-Warning' in AmazonMonitoringFacade [Monitoring]
This is not fixed by adding a localAlarmNamePrefixOverride.
If I get some time I'll put together a reproduction example.
Expected behavior
I would expect the localAlarmNamePrefixOverride to allow updating the local part of the alarm name (GSI name).
Actual behavior
Value is ignored.
Other details
This occurs because DynamoTableGlobalSecondaryIndexMonitoring calls createAlarmFactory on it's parent scope, MonitoringFacade, instead of on it's own superclass, Monitoring which handles the alarm local name override.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working