Skip to content
This repository has been archived by the owner on May 18, 2021. It is now read-only.

occurrences does not work #165

Open
khuongdp opened this issue Apr 1, 2014 · 7 comments
Open

occurrences does not work #165

khuongdp opened this issue Apr 1, 2014 · 7 comments

Comments

@khuongdp
Copy link

khuongdp commented Apr 1, 2014

Hi

It does not look like the sensu-dashboard is using the occurrences defined in the checks. Is this a bug or by design?

We have some checks that sometimes fail because of network issue. That is why we are using occurrences in our checks. It will give false negative if the sensu-dashboard is not using the occurrences value.

@amdprophet
Copy link
Member

This is by design but I'm open to the idea of changing that. Thoughts @portertech?

@nstielau
Copy link
Contributor

nstielau commented May 7, 2014

Removing checks that are below the occurrences level makes sense to me.
On May 6, 2014 3:23 PM, "Justin Kolberg" [email protected] wrote:

This is by design but I'm open to the idea of changing that. Thoughts
@portertech https://github.com/portertech?


Reply to this email directly or view it on GitHubhttps://github.com//issues/165#issuecomment-42367546
.

@khuongdp
Copy link
Author

khuongdp commented May 9, 2014

+1 for nstielau idea

@portertech
Copy link
Contributor

I like to see all events, even if they are due to a "false positive", as they are still an indication of failure of a service or of how its being monitored.

@portertech
Copy link
Contributor

We really need linkable filters, and expose this functionality as a built-in filter.

@portertech
Copy link
Contributor

Could be enabled by default, so an opt-out.

@amdprophet
Copy link
Member

Abide by occurrences by default & add a filter / option to show everything?

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

No branches or pull requests

4 participants