Hello,
​@fmattes 
For Centreon NSClient Service auto we are using  command

/usr/lib64/nagios/plugins/check_centreon_nrpe3

-H

*****

-p

5***

-t

40

-2

-u

-P

8192

-c

check_service

-a

filter=start_type = 'auto' and is_trigger = 0 and name not like 'GoogleUpdaterInternalService' and name not like 'clr_optimization' and name not like 'GoogleUpdaterService' and name not in ('BITS','TrustedInstaller','gupdate','MapsBroker','tiledatamodelsvc','InventorySvc','SysmonLog','gupdate')

service=*

exclude=StateRepository

exclude=

warning=not state_is_perfect()

critical=not state_is_ok()

top-syntax=${problem_list}

detail-syntax=${name}=${state} (${start_type})

perf-config=none

which give us result : -OK: All 52 service(s) are ok.

We are planing to move to CMA , CMA command is 

{"check":"service", "args":{"start-auto" : true, "filter-name" : ".*", "exclude-name" : "", "filter-display" : ".*", "exclude-display" : "", "warning-state" : "'stopped'", "critical-state" : "", "warning-total-running" : "", "critical-total-running" : "", "warning-total-paused" : "", "critical-total-paused" : "", "warning-total-stopped" : "", "critical-total-stopped" : ""}}

Giving us almost all services no matter startup type.
 

Can you please help us how can we configure CMA check same as Centreon NSClient . Because we use  event handler to automatically start that service using sript.

Thank You