Centreon: Issue Monitoring a Windows Service with a Specific Template
Hello, I'm currently facing an issue with Centreon while monitoring the services of my Windows virtual machines. When I test the monitoring, Centreon reports that the service is "OK". However, even after stopping the service on my VM, Centreon still shows it as "OK", even though it is actually stopped.
How can I fix this issue?
Thank you in advance for your help.
Page 1 / 1
can somebody help me please when i desactivate the service on my windows VM nothing happen it still says the service is OK but it’s not ? Does somebody already haved this probleme before ? Thank you
hello
there is a problem with windows SNMP and services, it’s a problem with windows and snmp, and the fact that the information about which service is running or not is not refreshed correctly
(windows stopped supporting snmp with windows 2012, I made a few thread here about that)
as an alternative you could try to use the check “process” to see if the process is running (a windows serivce is a process .exe, and in your case it’s not a “svchost.exe”, check if your windows machine has a single process for “vaultsvc”, you can get the process name in the service detail in windows)
the service template is
OS-Windows-SNMP-Processes-Name
here is a thread here where you can see how to setup the check with how to input the correct macro
other alternative, use an agent (nsclient, or wsman), with these you have a reliable way to check windows services by name.
Hi,
SERVICENAME macro is a regexp on the service DISPLAY_NAME not on the SERVICE_NAME.
For example, the DHCP Server service :
sc query :
Centreon service :
Regards
I want to monitor only virtual machines running Windows Server 2019. I have multiple service checks to monitor independently, but they all face the same issue: no reaction, whether the service is stopped or running. I also tested, as you suggested, with the DHCP Server service, but I only get a simple "OK" without any additional information.
The checks I am monitoring:
Is w3logsvc (IIS) running?
Is DNS running?
Is SSOAgentService running ?
Is SQL SERVER running?
Is MSSQL$SQLEXPRESS running ?
Is MANAGEENGINE UEMS - SERVER running?
Is Autodesk 2022 running ?
Is VaultSvc running ?
Is PRINT SPOOLER running?
Is IAS (NPS) running?
It works if you only fill in the macros SERVICE_NAME and CRITICALACTIVE as my first screenshot :
Windows SNMP service only returns services that are automatically started. Manual services are not returned.
No it dont works it says services actives 0 and put it in critical but the service is active so i don’t understand how i can monitor all my windows service i didn’t find a solution who work for the moment.
hello
I gave an answer above, either check the process (.exe) with the snmp check process, or use a non snmp agent like nsclient
checking the processes is limited as you can’t differentiate all the “svchost.exe” which are used for most a lot of system services, but in the list you gave above, most are non-system services and have a dedicated process
snmp and windows services is not working correctly as windows is not updating the information when a service is not running
ok thank you but can you tell me exactly what and where i should put something.
Hi @Maxime3211,
Can you show us the command that appears in the details panel of the monitoring view and its result when you run it as centreon-engine user with --verbose and --debug options added ?
Salut @omercier Alors j’utilise --verbose et j’ai testé pas mal de technique mais aucune de concrète …
Hi @Maxime3211, the goal of my question was to learn what the command actually looked like and what the debug output was, I cannot help you much without it.
I have an intuition though: VaultSvc is not the services Display Name, which is presumably Credential Manager.
As @cb58 told you:
Hi,
SERVICENAME macro is a regexp on the service DISPLAY_NAME not on the SERVICE_NAME.
Hi @omercier i will show you all the config.
i also tested with the template OS-Windows-Process
in service VM
Right click more details
Hi,
As it has been said earlier VaultSvc is not the Display Name of your service.
If you have a Centreon IT license, you may use the Service Discovery feature that will help you configure your monitoring.
If you don’t, then if you have a look at the screenshot you sent, the display name of your service is Gestionnaire d’informations d’identification.
As the single quotes may cause issues in the command line, I suggest you write Gestionnaire d.informations d.identification in the SERVICENAME macro in your configuration, and it should work.