Hello Amazing Community
I have problem while adding windows Host to Icinga
in my Windows Machine , i have open the port 5665 IN and OUT in my LOCAL FIREWALL
second , i have installed the agent , add the signed ticket ( see the capture)
after that , i restarted the service of icinga in windows machine,
in my master node ( which is centos 7 machine)
i have added the configuration file for this machine under /etc/icinga2/zone.d/master.myfile.conf
the disk check for windows under service.conf who is the same position as hosts.conf in /etc/icinga2/zoned.d/master
apply Service for (disk => config in host.vars.disks_windows) {
import "generic-service"
check_command = "disk-windows"
command_endpoint = host.vars.client_endpoint
assign where host.vars.agent_endpoint
vars += config
assign where host.vars.os == "Windows"
}
But i can only view the hostalive check and no disk
I watched many videos on youtube , they just add the windows hostname in the right config file and all the services will be up automaticaly but nothing happend for me
Any advices and what should i do ?
thank you all
Cordially
Any News guys ?
I tried with the same as monitoring disk like centos but for windows-disk
i get the value of partition in linux and not C:/ or D:/
Whaat should i do ?
Okay , Im new in this community and i dont know all what should i do, thanks for the references
But for my issue i edited that and its not working and what i get is the partition of Linux and not the C:/ or other partitions
Try this, cleaned up code. Also, i moved vars.client_endpoint down. So, if your “generic-host” also defines it, it will not get overwritten by “generic-host”
Hello Again , I tried to modify the zone.conf file and i added just the name of the host without FQDN and the result is in the capture
i see here that the value is inversed like the disk F:/ is all free and the warning setting and the critical are inversed
Thanks all for your help , ill try to make the maximum and i’ll go back to you when i resolve the problem
Hello again ,
i have found the solution for this issue,
first, the name of the node client should be the same in the zone.conf file
second , i have add the line to get the right result in the client machine