getting service.discovery to work in zabbix 3.0

[xanadu]

Today I've been trying to get service.discovery to work although I fail to do so.

I followed the manual on https://www.zabbix.com/documentation...ndows_services

but it would be nice if someone could post a screenshot of a configured item prototype(s) and trigger(s) as well.

Currently the host is discovery the services but it doesn't display any values.

[harmonica]

Today I've been trying to get service.discovery to work although I fail to do so.

I followed the manual on https://www.zabbix.com/documentation...ndows_services

but it would be nice if someone could post a screenshot of a configured item prototype(s) and trigger(s) as well.

Currently the host is discovery the services but it doesn't display any values.

Hello,

What's zabbix agent version?

[xanadu]

Hello,

What's zabbix agent version?

Hello,

3.0 as well. It's a brand new installation.

[xanadu]

Is there more information available to have this configured?
Previously I was using the servdisc.vbs / servdisc.ps1 script from github:

https://github.com/q1x/zabbix-templates/blob/master/service-discovery/servdisc.vbs

But as LLD service discovery is now build in into Zabbix I would like to use that.

I just need some help to configure the Item protoypes and triggers.

[xanadu]

Has anyone on 3.0 got this working?

[harmonica]

Has anyone on 3.0 got this working?

I will test and give feedback as soon as possible.

[xanadu]

I will test and give feedback as soon as possible.

Looking forward to your findings!

[xanadu]

Hereby my Item Prototype which doesn't give the status of the service, although it discovers all services without any problem.





If someone knows what I'm doing wrong, please assist

[harmonica]

I will test and give feedback as soon as possible.

Hi,

Try this example

Discovery Rule
Name > Services discovery
Type > zabbix agent (active)
Key > service.discovery

Filters
{#SERVICE.STARTUP} matches 1
{#SERVICE.STARTUP} matches 0

Item prototypes
Name > Startup type of {#SERVICE.DISPLAYNAME} ($1)
Key > service.info[{#SERVICE.NAME},startup]

Name > Status of {#SERVICE.DISPLAYNAME} ($1)
Key > service.info[{#SERVICE.NAME},state]

[xanadu]

Thank you harmonica! Works like a charm

However I would like to achieve the following:

- Have friendly names instead of the numbers
- Have a trigger when a service becomes stopped/stopping/starting for services that are on Automatic / Automatic (Delayed start)

So I guess I don't need the "Startup type" item prototype?

[mse]

I just upgrade installed on 3.0. I would like to use this function services.discovery also.

Do I have the agent on 3.0 Upgrade?

Xanadu, can I see your Discovery Rules?

[xanadu]

Is there anyone who could help us with this matter?
Still haven't this working. Would love to see this added in the documentation.

[mse]

I have already found a solution to the problem.

I am currently out of the office, will like the solution on Friday to post here.

[xanadu]

I have already found a solution to the problem.

I am currently out of the office, will like the solution on Friday to post here.

That's very kind! Looking forward to have this sorted.

[mse]

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.