Feature request; new "informational" state
Hi Checkmk (community),
I would like to raise a feature request for checkmk.
We are looking for a new “informational” state which should be below critical, unknown\unreachable, warning and ok, and then “informational”.
Currently, we have warnings which are being ignored because it really isn’t a real warning (for us).
For example “uptime since last reboot”.
We configured rules where we want to reboot hosts every 30 days, but sometimes it isn’t possible, or it should be an informational message for the feature.
Beside above reason it can be used for much more.
Ideally it should be the color gray, but that is already in use for the state pending.
Maybe white or something like blue should be a great one.
Thanks in advance.
Comments: 17
-
10 Nov, '22
Robert SanderYou cannot add a new state. This would be an incompatible change as nothing in the Nagios monitoring world is able to handle it.
-
07 Dec, '22
JosefMaybe just use this state in BI - that should not affect the core. Or you can select a "rewrite" option in a rule that warning in shown as info in the gui.
-
09 Dec, '22
Robin GierseWhy would you not just use the WARN state for this? That state says "Something needs attention", which is in my understanding exactly what you are looking for.
Maybe I am missing your point, but I feel like the possibilities are there, if used correctly. Maybe you can clarify why existing options do not work for you.
Apart from that, Robert Sander raised a critical technical problem with this request, which is unlikely to be solved easily. -
09 Dec, '22
Marcel Arentz AdminIf something is not a real WARN, it should be handled and there are already several mechanics to handle such cases. If it is a real WARN, and you're not able to handle it at the moment, you may acknowledge the WARN or add a downtime to the particular service. I don't see the benefit of a new state that cannot be handled already in Checkmk. Maybe you can give us some more insights.
-
29 Dec, '22
Paulo Adriano MergedThat state will could be used is some cases:
- Virtual machines: When using a small amount of memory and CPU for a long time it would generate a recommendation that indicates that a downgrade could be performed. I will request that feature.
- CheckMK Discovery: If it identifies a new service that can be added to the host it could generate a recommendation whick looks better than the actual warning alarm. -
29 Dec, '22
Thomas Lippert Admin"Include a new state called Recommendation or Informational" (suggested by Paulo Adriano on 2022-12-29), including upvotes (1) and comments (0), was merged into this suggestion.
-
10 Jan, '23
JeroenSorry for the late response, i didn't check if there were any comments on my request and it is also my first request made.
Maybe the name recommendation is a better name dan informational.
But what I can see the use in, for this state, is the uptime service.
Normally we reboot windows servers every month but sometimes we can't for some reason.
At the moment we have rules which show warnings above 30 days uptime which is actually correct because we want to reboot the server.
But it isn't a real warning because there are no real problems that can occour when the uptime is higher then we normally want.
So therefor i think its better to have a informational or recommendation state.
Also you can create a fake check result with the new state for future plans, like a to-do list.
Services and\or hosts in downtime are not visible unless you check for them manually. -
23 Aug, '23
Felix MergedNew check state INFO for alerts that aren't indicating issues but are relevant in monitoring anyways (like the APT plugin).
-
24 Aug, '23
Niklas Pulina Admin"INFO check state" (suggested by Felix on 2023-08-23), including upvotes (1) and comments (0), was merged into this suggestion.
-
18 Oct, '23
Martin Hirschvogel AdminThere are many options how to deal with such a requirement already in Checkmk. Introducing a new state will rather lead to more problems down the road.
Some of the options have already been discussed in this thread. If you need further ideas, please ask the Checkmk community on forum.checkmk.com
Changing it to not planned. Sorry! -
09 Nov, '23
Michael Kissel MergedWe would like to have a new INFO State as Service State.
Sometimes it's better to have a state with just INFO than WARN - mainly on Open Dashboards etc.
We use lots of local scripts - sometimes just to know which users are logged in on certain systems. This is just for information. In those cases we like to have an INFO instead of WARN.
I think, this is easy to implement for local scripts and would be very nice.
Sometimes in daily business info is better than WARN ;-) . -
13 Nov, '23
Niklas Pulina Admin"New INFO State as a Service State" (suggested by Michael Kissel on 2023-11-09), including upvotes (1) and comments (0), was merged into this suggestion.
-
13 Nov, '23
Niklas Pulina AdminHi Michael Kissel, thanks a lot for posting your idea.
As a similar suggestion already existed, I merged yours into the existing one.
However, I would like to ask for your understanding that we are not planning to implement this additional state for the reasons discussed above. Thank you! -
26 Feb
Marcel Arentz Admin"New INFO State as a Service State" (suggested by <Hidden> on 2024-02-23), including upvotes (1) and comments (0), was merged into this suggestion.
-
26 Feb
Marcel Arentz AdminHi Michael,
You already suggested that before. I allowed myself to add it again to the existing one.
There is no mechanism in Checkmk that would allow to implement such a feature without being inconsistent and confusing: What's the difference between OK and INFO? Currently, Checkmk is not a "Best practice" tool. All entries in the OK state are "informational". With matching on the output, you are already able to filter for these entries (in dashboards, views, notifications, etc.) -
27 Feb
Michael KisselHi, sorry for my second post.... but never got a message or answer. And i had no link and nothing to find it again. So i wasn't aware if i ever posted it.