Hi,
im starting to migrate checks from icinga1 to icinga2
i’ve implemented this command check and it return me that the service does not exist.
if i change a service name like schedule it works, seems my service definition in server win is too long?
this is the service name in win server: “edok.HyperDok-Acquisti.DokLabelserviceTenacta”
i’ve inserted temporary in command.conf for debug reason, it works on icinga1, someone know if there is some limit regarding var length definition?
regards, livio.
welcome to the Icinga community You’re a little late for the migration party, but let’s try it nevertheless. I assume you have read the migration docs already?
While I agree that learning to migrate the command lines to proper 2.x syntax, you should also take into account that the Icinga 2 template library already may provide certain CheckCommand objects.
check_nt is covered by the monitoring plugins, and available inside the ITL as nscp. That being said, it is now key to extract the command line arguments and match them accordingly.
hi michael,
thanks for you quicly reply, but the problem is not the syntax of the definition, the problem i think is the length of this service defined in windows and icinga2 seems have a tips when is so long, no problem with icing1 but this service name “edok.HyperDok-Acquisti.DokLabelserviceTenacta” it’s too long or it doent like some special char, if i change it with another service like “schedule” or “dnscache” it works fine. also if i try to execute command line check_nt with all params it woks, so i think that icinga2 have some tips.
regards, livio.