We’re using Icinga2 with flat file configurations vs the database backend.
We’re in the early testing stages of rolling our Icinga to our Windows servers using the nsclient. Many of these windows servers block ICMP (ping) packets
I have the nsclient working for the most part including monitoring specific windows services, memory/cpu/disk usage and more.
My main problem is that since these systems don’t permit ICMP, Icinga2 shows them as “down”. Is there a way that Icinga can report the status of the system based on whether or not it is able to communicate with the nsclient?
Does anyone have an example of the configuration file(s) to make that work?
Okay, what check are you able to use? I have no idea what connectivity you
have, or what services are expected to be running, which would qualify as
“server is up” in your environment.
You can use any service check command you like for the host check; if it
returns status 0 or 1 (OK or Warning) the host will be regarded as up, and if
it returns 2 or 3 (Critical or Unknown) the host will be regarded as down.
I was thinking something as simple as checking the nscp client version
If Icinga is able to get a response from that, then it’s safe to assume the system is “up”
I’ve looked over that page and attempted to accomplish this, but Icinga continues to report the system as “down” which is why I was hoping for an example functioning code snippet for my configuration.
I have something like that, but it does not appear to have the desired affect, still resulting in the system showing “down”. Running the same command in a separate “service” it seems to return OK.
Really glad your issue got resolved!
Could you please mark the response that contributed most to fixing it as the “solution”?
This way people have an easier time finding out where to look if they have a similar issue and which topics still need answering
Thank you very much and have a lovely weekend!
Feu