-
Notifications
You must be signed in to change notification settings - Fork 13
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
(Acknowledged) Host Down & (Open) Service critical not shown in Main Screen #22
Comments
View from Nagios: SMD connects via "Livestatus socket path" to Check_MK/Nagios (OMD Suite) |
Hello! I'd need to check out if the host status is taken into account for filtering the service, because the filter message tells that is being filtered by the host status. |
Good Morning .-)
I don't know exactly how to interpret your response, sorry :o) If you are interessted we can do a live show/tell session via TeamViewer - Or I can supply more and uncleaned screenshots if you provide me an private contact possibility! Cheers! |
Umm, don't worry, I've checked out the code and the event is not being shown on the main view because the host status, that is if the item state is 1 (or above) or the host state is 1 (or above), the event will be filtered out of the main view:
|
Good morning! :) |
And why that is done so?, because the host check has failed, you don't know exactly if the service is down due to the host issue, so I decided to filter out of the main view to keep it clean in the meantime the host status becomes ok. |
But wouldn't it make sense to show up an down and acknowdledge'd host at least due to that feature: "Critical items: a comma separated list of critical hosts/services that will be always shown (non OK states)." ? With that in place colleagues all around would see immediately that a) is a problem with that host b) some colleague is already working on it P.S.: I have checked "Show scheduled events" and after every logout and relogin from/to the config section, the checkbox is unchecked again |
Sorry, you're right, the item should be shown because it matches a regular expression, but the filtering is getting rid of that. I'll take a look to the config issue too. Kind regards |
Please, let me know if it works fine now. |
Better but not perfect again with the newest patch :-) Now I have "34/52 notices" on the main page, and round about 80% still have "Filter: No Regex Host & No Critical" reason on the main page. Following Level types: Flapping Since levels from 5 Minutes up to 130 Days |
Hello, I've done some tweaks and should be fine (I hope...). Please blank any regex on "Shown hosts REGEX at main view" |
Sorry for the inconvenience, but my testing environment is currently broken so I can't do any test... |
Hmm the newest version of sysMonDash.class.php results in the following behavior: The not wanted Hosts are still there in the main view, but now without the explanation ""Filter: No Regex Host & No Critical" When I remove every regex from "Shown hosts REGEX at main view" and include my VIP Hosts only in the "Critical items", after saving and checking again the config I see: The default value in show hosts "/.*/" is listed again in the field. I also tried to add an ! in front of but the result of showing to much Hosts in the main view is still existing. If I can test more and or If you want to do a TeamViewer Session just let me know! Cheers and THX very much for your motivation! |
You're welcome ;) The current behavior is to show all host and services that have a problem (non OK status), BUT some items will be filtered out when the status isn't so accurate because a dependent host/service or it's acknowledged. The "VIP" hosts/service regex is useful to always show those items regardless other filtering, but if you only need to show some hosts/services, you need to create a "Shown hosts REGEX at main view" regex that matches those items (it could be very hard to maintain...). I've just pushed a revision to not set the default hosts regex |
I exchanged the ConfigData.class.php with the current one, but still got I fully understand the current behavior and due to that I used the "Shown hosts REGEX at main view" since the beginning and it worked fine - Since this -> d7de7d8 ;-) |
In the meantime, you could edit the SMD config file located in Which hosts are currently shown? |
item type="criticalItems"^COMPANYNAME|^..CA|^..SE|!^..LX|ATBA....cut... item> But on the Main View I got f.e. also: CRITICAL 2d 13h 30m 45s DECS..... CRITICAL - Socket timeout after 10 seconds |
Did you tested the regex?, i think that the ^ could be set only once, at the beginning of the pattern and then enclose the words within () and many pipes to catch any word. |
And critical items should be separated by commas, it isn't a regular expression |
I use that exact RegEx Style in my old running version of SMD and its working fine there .-) I've done a little test in the current version: Even with only one Host without any regex stuff, the main view filter doesnt reflect it. I got nearly all host and services Alarms -> 41/70 notices |
…. Related #22 * [MOD] Javascript refactoring.
Please, try out the latest commit, the issues should be already solved. |
We're close, very close :-)
|
Right, critical items are always shown. I'll check out the third point, because I've done some tests and it worked fine. Could you try out with a single item in the pattern? |
I did, but the result was the same! Thanks & Cheers |
Could you send me a single host pattern example? (Real name not needed) |
Just tested it with two example Hosts from "Show More" Page, but they didn't show up on the "Main Page" COMPANY-XY-FOOBAR-Z |
So, you mean that these hosts have been set in the regex pattern and the main screen doesn't show them, right? |
100% ACK |
Umm, what are the state of them? |
BTW: The "-" are part of the host in Nagios (!) |
Ok, I'll take a look to the code, because the tests done yesterday worked fine using even a hostname containing dots and then escaping them in the pattern "\.". Thanks for the feedback! |
Hy, sorry for the late reply, hope your are doing well! I did a test and found a few things:
Cheers! |
Hi!, so sorry about the late reply, I forgot your post. I'll check it out shortly and let you know how to fix it. Cheers! |
Hello (again) :-)
one hosts has an (achknowledged) Alarm in Nagios, and one Check_MK service which has an open critical state.
The Host and Service are only visible in the "Show all" section.
I also tried to add that host in the "Critical Items" List but same behavior.
Is that the normal behavior, maybe due to the ACK of the Alarm? If yes, that would be not that good ;)
Cheers!
The text was updated successfully, but these errors were encountered: