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

cmd/bosun: adding "unknownIsNormal" flag to alerts to convert unknown events into normal ones. #1620

Merged
merged 1 commit into from
Feb 24, 2016

Conversation

captncraig
Copy link
Contributor

Simply replaces the event status in run history. Should help with things like #1160 where sparse data is expected.

It will end up creating a normal event for all alert keys every 2 check cycles once they disappear. Not sure how to prevent that. Maybe it would be better to suppress unknown generation at all for these alerts, but then they are unclosable, so never-mind.

@@ -253,6 +253,7 @@ type Alert struct {
Unknown time.Duration
MaxLogFrequency time.Duration
IgnoreUnknown bool
UnkownsNormal bool
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unknown

@captncraig captncraig force-pushed the unkownToNormal branch 2 times, most recently from e6a2325 to 65a77a3 Compare February 24, 2016 20:49
@kylebrandt
Copy link
Member

LGTM

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

Successfully merging this pull request may close these issues.

2 participants