Cloud Alarms Checker
This project is created to identify whether alarms and their corresponding actions are associated to the cloud resources or not.
For example, In case of AWS, this project is helpful in dentifying whether a SQS queue associates with any cloudwatch alarm or not. If it is associated then it is also checked whether any SNS topic is attached with some endpoint to it or not.
- Helps in identifying the resources not having alarms.
- Can check for any number of region by simply changing in inputs file.
- Easy to read google sheet is provided as an output, which can be sent out to via slack( or any channel with minimal code chnages)
- Proper templating is provided to add any new resource
- It is independent of cloud, and easily a new cloud resources can be introduced.
As a result of these scripts, a well classified tabular sheet is obtained containing all the information
- Region of the resource where it is present
- Name of the resource
- Creation time of the resource
- Buisness, Service and Subserice name of the org, of which it is a part
- If alarms are not present then a proper Description like
No Alarms are Present
- If alarms are present and no notification endpoint is provided, then proper description like
No Notification channel is attached to alarm
Also, to exempt any resource to be checked, it is suggested to attach a specific tags to them.
For example, "Monitor" : False
tag can be used and defined inside ../inputs/*yml to let the script know that any resource with this tag are exempted.
-
To know more about the architechture, refer Architecture.md
-
To know more about on how to use the script, refer How_To_Use.md
-
To know more about on how to deploy the scripts in production environment, refer Deployment.md
To Contribute in the project, refer
To know more about the policies, refer to Code_of_Conduct.md
Developed by MoEngage Team
For any queries plaese opensource@moenagage.com