i would upgrade my Windows Monitoring Infrastructur, with some special Check Commands.
For this, I created a folder in the path where /etc and /var are, where I copied all the checks.
How do you solve this in your monitoring structure? Unfortunately, the checks are not recognised. Icinga report ,Check-name not exist"
I have added the following lines to Constans.conf:
You need to define check commands on the icinga machine as well as every Windows machine. The simplest way to do this is to put those objects into a global group that is defined at every machine.
I have already stored this in my service templates on my master. There, the plug-in directory is specified as /monitoring/checks. I think this is an error in my logic with the agent configuration on the windows host. How did you solve this in your infrastructure or do you happen to have an idea how I can check what is missing at best
unfortunately no. I’m afraid I’ve forgotten something in the agent, but unfortunately I can’t find it. Or I cannot explain why the query does not take place.
Don’t forget, that it’s not a “must” to use the constant PluginDir. You can also write full path names.
We are doing this for self written scripts. Especially if the the person who responsible for the server write his own special check script. He is telling us the path and we create the check command and service check in the director. If this person is doing this, he is also responsible to backup his check. Anway - in case of powershell checks - we offer the person every time, to put these checks into our own powershell module
Check if the global zone is configured at your Windows machines and then do a restart of the icinga agent. Check icinga.log at the Windows machine(s) for any errors or other hints.
You have no connection information in this zones.conf, hence, the agent will not initate a connection to its master. If you have your master configured not to connect to agents, than you will have no connection at all. Hence, nothing to sync.