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.

Sign up for GitHub

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

Jump to bottom

Suspend Alerts #29

Open
jMyles opened this issue Apr 8, 2012 · 1 comment
Open

Suspend Alerts #29

jMyles opened this issue Apr 8, 2012 · 1 comment
Assignees
@KPrasch
Labels
Idea Ops

Comments

@jMyles
Copy link
Member

jMyles commented Apr 8, 2012

A flag file, located somewhere on the production server, titled "suspend_alerts" is normally set to 0. If set to 1, alerts are no longer sent out. We might consider having "suspend_error_alerts," "suspend_heartbeat_alerts," and "suspend_all_alerts" and having the heartbeat one also reside on the heartbeat server.

At midnight every night, the flags are set back to 0.

Just an idea.
@ghost ghost assigned J-Cruz and KPrasch Apr 23, 2012
@jMyles
Copy link
Member Author

jMyles commented Apr 23, 2012

Obviously this is a big idea / issue. It needs some social underpinning in order to be fully realized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@KPrasch KPrasch

Labels
Idea Ops
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jMyles @KPrasch @J-Cruz