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

Treat acknowledged services and hosts as OK #69

Open
benschweizer opened this issue Jun 11, 2018 · 4 comments
Open

Treat acknowledged services and hosts as OK #69

benschweizer opened this issue Jun 11, 2018 · 4 comments
Assignees

Comments

@benschweizer
Copy link

For discussion:
If a service is critical, the whole location is marked critical. I think it would be better to filter out acknowledged services and treat them as ok. The effect would be a map with less red flags. What do you think?

@nbuchwitz
Copy link
Owner

I agree that we have to find a solution for this as it was already asked in #66 and #54. Maybe is your suggestion to handle these acknowledged services OK the easiest way for now. I'll think about it.

@nbuchwitz nbuchwitz self-assigned this Jun 12, 2018
@nbuchwitz nbuchwitz changed the title Treat CRITICAL als OK when acknowledged Treat acknowledged services and hosts as OK Jun 12, 2018
@nbuchwitz
Copy link
Owner

Maybe I could add something like a exclamation mark to the symbol to indicate that there is something acknowledged

@nbuchwitz
Copy link
Owner

After thinking and talks to users at OSDC I favor a config option to decide between two solutions:

  • the way it is now (red/orange/whatever icon even if a service is acknowledged)
  • treat handled services as OK and display an exclamation mark as symbol

image

@deikelenboom
Copy link

We are looking for exactly this feature. Currently it is a pain that we have to explain to non-developers that the red icons on the screen are not actually problems...

Is it still being implemented?

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

No branches or pull requests

3 participants