Closed KadalurSupreeth closed 1 year ago
Notification is sent only for 'WARN' and 'ERROR' messages, while all messages are saved in the dynamodb table. The default threshold for WARN is 80%. You can lower that in the spoke template parameter and check if the notifications are sent.
You can ignore the warning message, we will clean up the logging to be debug level.
Thanks. This approached worked. Actually, I changed the QMCWPollerQMCWPollerLambda function environment variable for threshold value rather than redeploying the spoke template for testing purpose only. Anyways this worked. Thank you
We have upgraded from limit monitor to quota monitor. Used the hub and spoke model deployment solution using quota-monitor-hub template and its dependencies.
Currently trust advisor is sending notifications. However, service quota check is not sending any notifications. Changed the CW poller event rule scheduler to invoke QMCWPollerQMCWPollerLambda so that I can test the notifications are being sent out. There are valid service quota thresholds for VPC quota limit and Elastic IP limit in monitored account. Still notifications are not received. Verified Hub account DynamoDB tables, they show status as "OK" for these limits.
When checked the logs for QMCWPollerQMCWPollerLambda, I see constant warning messages like mentioned below. Is this anything to worry about?
[WARN] [getMetricData] ValidationError - The values for parameter id in MetricDataQueries are not unique.
Can you please guide me on how to test couple of notification scenarios for Service quota threshold? May be by tweaking spoke Service Quota DynamoDB table values?