Skip to content

DynamoTableGlobalSecondaryIndexMonitoring ignores localAlarmNamePrefixOverride #628

@haljarrett

Description

@haljarrett

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

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions