255 character limit on an item/trigger

[rjurek]

I am currently using service[automate,stopped,exlcude] to monitor service on windows servers. My exclude list has taking me past the 255 character limit has anyone found a way around this?

Example:
services[automatic,stopped,"PGPsdkServ,RemoteRegistry,STSch edEx,ShellHWDetection,SysmonLog,agent_watchdog,clr _optimization_v2.0.50727_32,clr_optimization_v2.0. 50727_64,clr_optimization_v4.0.30319_32,clr_optimi zation_v4.0.30319_64,gupdate,sppsvc"]

I need to add several more service to be excluded but can't due to the limit. I have opened a support case and they have suggested aliases, but I have tried that method and it does not work, unless I set it up wrong....

Thanks
Ross

[ingus.vilnis]

Hi Ross,

There might be a workaround for this. It kind of worked on my 2.4 test instance so you can give it a try on a real production environment.

In short, you can use Macros on template (or host) level.
To do so you can create two or more macros containing a list of services to exclude.

{$SERVICES1} => "PGPsdkServ,RemoteRegistry,STSch edEx,ShellHWDetection,SysmonLog,agent_watchdog,clr _optimization_v2.0.50727_32,clr_optimization_v2.0. 50727_64,clr_optimization_v4.0.30319_32,clr_optimi zation_v4.0.30319_64,gupdate,sppsvc,

{$SERVICES2} => continued list of services"

Then for the item key you can use the macro names

services[automatic,stopped,{$SERVICES1}{$SERVICES2}]

As a result the macros should be resolved with length over 255 chars and the information returned.

Hope this helps.

Best Regards,
Ingus

[rjurek]

Ingus,
your suggest works great, but I did fine a little bug I think.. The first and last service in the list was getting ignore, so I just added a bogus name at the beginning and end of the list and now all the good services are included..

thanks for your help, this is a simple and manageable means of handling the service exclusion monitoring.