Problème CMA service monitoring

Run the command without a filter and --debug --verbose to see which names get reported 🤔

Ok i found on the documentation how to test, but for services, there is no mode to test :

Windows Centreon Monitoring Agent | Centreon Documentation

Hi ​@nsetbon,

Have you found a solution? I have the same problem and try to understand the right syntax.

Thanks

Bonjour,
Même problème depuis des semaines peut importe la version. Actuellement en 25.10 (Centreon et agent).
 

Config :
 

Status :

Pourtant il existe :
 

Comment faire ? Est-ce un bug ?

Hello,

Set also a value to the FILTERDISPLAY macro (i set a wildcard, the Name filter will get the service i want)

Keep your filter on FILTERNAME macro

It should works this way

Hello,

​@vcoum I tried your solution, but it still doesn't work.

And same when I’m putting STARTAUTO → true :(

But thanks for your suggestion !

​@sps I tested it with the same service as you (FusionInventory-Agent) and i have the same problem (and none of the regex i used works)

But this is the only service that is not detected (i tried a dozen and they are all correctly detected)

I think that’s a bug for this one

Did it works for you with the other services?

Hello,

Set also a value to the FILTERDISPLAY macro (i set a wildcard, the Name filter will get the service i want)

Keep your filter on FILTERNAME macro

It should works this way

Thanks for your message.
Same problem with :
 

Yes it seems there is some problems in the service enumeration with the Agent

For what i observed, it concerns service with a long execution Path

Do you have the problem with all of your services ? Can you test with a service with a short path? (for example CentreonMonitoringAgent)

Hi ​@vcoum,

I tried with “Dhcp” and it works : 

The service “CentreonMonitoringAgent” also works.

For a single service, it would be nice to have its name in the result as in the NSClient, here I have “all services are running” for 1 service.

Okay so Centreon need to fix this in the agent code

For your result issue, it seems the output message is hardcoded in the agent so we can’t change it 

Maybe Centreon will add more options for outputs in the future