getting service.discovery to work in zabbix 3.0

[xanadu]

Thanks for your answer.

Earlier on I used the Windows service discovery template which you can find here:

https://github.com/q1x/zabbix-templates/tree/master/service-discovery

However as from Zabbix v3.0 it is build in I would like to use LLD discovery for that.

I just need to some help to setup the item prototypes and triggers.

[xanadu]

In this constellation, it works for me.

1. Upgrade the Host Agent of 3.0 V

2. Add the Regular Expressions

3. Import Win Services Discovery Template

4. Link the Template to the Host.


For feedback I would be delighted.

Ok thanks! I noticed you've put the new way of discovery in a template, had a weak moment I guess.
Now it's discovering both "automatic" and "automatic delayed" services. I would like to have only "automatic" services. What regular expression should I use to only have these?

Cheers

[mse]

It would look like in the attached image.

[xanadu]

It would look like in the attached image.

Can you upload a higher resolution image, I can't read it

[mse]

Can you upload a higher resolution image, I can't read it

already happend.

[xanadu]

already happend.

Great! Works like a charm indeed. Thank you so much

[xanadu]

Great! Works like a charm indeed. Thank you so much

Could you also post a high res from Windows service exceptions? eg. to exclude "Remote Registry" and others?

[xanadu]

already happend.

Could you also post a high res from Windows service exceptions? eg. to exclude "Remote Registry" and others?

[xanadu]

ok, found that you need to add regular expressions under the menu Administration / General / Regular expressions.

[LLC]

Great template! Thank you so much!
How to setup trigger only at specified service?

like:
(#SERVICE.NAME=DNS) and
({Template OS Windows services discovery:service.info[{#SERVICE.NAME},state].last()}<>0)

[mse]

Great template! Thank you so much!
How to setup trigger only at specified service?

like:
(#SERVICE.NAME=DNS) and
({Template OS Windows services discovery:service.info[{#SERVICE.NAME},state].last()}<>0)

I can not help you at the moment. I still have too little experience.

[sege]

Could someone paste better pics and the regexps in clear text perhaps? My eyes just aren't good enough to read those pics..

[mse]

Name: Windows service names for discovery
Expressions:
Expression Type: Result is FALSE
Expression: ^(MMCSS|gupdate|sppsvc|RemoteRegistry|SysmonLog|cl r_optimization_v2.0.50727_32|clr_optimization_v4.0 .30319_32|clr_optimization_v4.0.30319_64)$

Name: Windows service startup states for discovery
Expressions:
Expression Type: Result is TRUE
Expression: ^(automatic|automatic delayed)$

[nick0909]

Services discovery seems to be working for me after only updating the agents to 3.0. I am still running server 2.4.6 and I am able to get service discovery items to create dynamically. Just in case anyone else is in the same place and wants to use this feature before upgrading their server.

Does anyone have the value mapping for {#SERVICE.STARTUP}? It looks like 0 is automatic, but I am not sure of the rest.

Edit - found it in the 3.0 documentation:
0 - automatic,
1 - automatic delayed,
2 - manual,
3 - disabled,
4 - unknown

[jerelev]

I (think i) did what you wrote in this post - but i get an error on the discovery rule:
Value should be a JSON object.

Someone knows how to fix it?