Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add treat missing data options to alarms #11

Open
hyei opened this issue Apr 28, 2021 · 2 comments
Open

Add treat missing data options to alarms #11

hyei opened this issue Apr 28, 2021 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@hyei
Copy link

hyei commented Apr 28, 2021

I'd like to be able to set the treat_missing_data option for the alarms while using this module. For example, I'd like to set it to notBreaching, to avoid instances where no data is captured by AWS or it erroneously marks the the alarm as insufficient data and then reports when it transitions back to OK.

@hyei hyei changed the title Treat missing data optioms Add treat missing data options to alarms Apr 28, 2021
@lorenzoaiello lorenzoaiello added the enhancement New feature or request label Feb 1, 2022
@lorenzoaiello lorenzoaiello self-assigned this Feb 17, 2024
@lorenzoaiello
Copy link
Owner

Hey @hyei ,

I created #26 to address this. Can you take a look and let me know if it addresses your ask?

@hyei
Copy link
Author

hyei commented Mar 11, 2024

Yes, it looks like it will do what I need it to, which is to prevent the alarms created in the module to all complain if I temporarily pause/shutdown the rds instance with the alarms in place. We subscribe to rds events to be notified when the DB/RDS is down and none of the alarms supported in the module replace that, so individual settings for each alarm is not needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants