quota-monitor-for-aws
quota-monitor-for-aws copied to clipboard
aws-solutions
Alerting every 30 minutes
Hello, I don't see a way to change the frequency of the alert.
We are getting an alert every 30 minutes. And it's becoming annoying. We place support tickets to request increases, but sometime its takes more than 24 hours for the limit to be increased and in the mean time we keep getting the alerts.
Can we limit the alert to once or twice a day?
Apologies for the delayed response. Do you still have the issue? By default the TA service limit checks are refreshed by cron schedule of 1 per day see here: https://github.com/awslabs/aws-limit-monitor/blob/85a7c6346ab08edd642a2e7e76f212ecf27b012f/deployment/limit-monitor.template#L62
Did you change this to every 30 minutes? It is configurable and you can control this setting at your end by updating the template mappings section.
Please keep in mind, if anyone visits TAconsole the checks get refreshed. This would be in addition to the refresh rate that you set on the solution. To check if it is really the solution triggering those refreshes you can go to CloudWatch console and see if the related cron Event rule was triggered or not. cron event rule
I too have a 30-minute cadence of refreshes happening. I haven't tracked it down yet, but there are other tools, such as cloud custodian, that also perform refreshes in their job, so that could be the source of the extra events.
Which all goes to show this implementation is lacking where the previous (I think version 2?) was better: one email/day, showing all the issues. No time to contribute, so I guess I'm reverting all the way back to V2!
Actually, I'm curious: what is the purpose of writing all the events to DynamoDB? Presumably this would be a means to perform a more robust filtering of event notifications vs. allowing events to just flow through the event bus repeatedly every time they are triggered by a TA refresh. I'm hoping this is in the roadmap!
We have added your request to our solution backlog items and it will be considered in future solution releases. We thank you for your contribution.
Same issue here, oddly it just randomly started happening in the last few days.
I am seeing the same issue and I did not change anything in the templates I downloaded from AWS.
Hopefully it comes out with the release updating from Node.js 8.10.
