Using LLD to monitor Windows Services

[qix]

I've created a Low Level Discovery script to monitor Windows services automatically.

By default it will use item and trigger prototypes to start monitoring services that are started on boot time.
Filtering is possible on multiple discovery macros:

{#SERVICENAME}		The name of the Windows service
{#SERVICEDISPLAY}	The displayname of the Windows service
{#SERVICESTATE}		The state of the Windows service
{#SERVICEDESC}		The Windows service description

This will also help a lot for applications where a new service is defined per instance (like SAP, MS-SQL, Biztalk, etc.) which are currently kind of hard to create templates for. In this case you can filter on the name instead of the state.

You can find all you need here: https://github.com/q1x/zabbix-templa...vice-discovery

Also, if you would like this function build into the agent instead of using a script, please vote for https://support.zabbix.com/browse/ZBXNEXT-1368

[daniel.s]

I've created a Low Level Discovery script to monitor Windows services automatically.

Thanks. This sounds good, I'll try it out this week.

Great timing as I want to figure out how to get these Windows LLD scripts working and write an Exchange 2010 mailbox discovery script.

[alledm]

Hi,

haven't had the chance to test it but it looks great.

Can you also add one #SERVICESTARTSTATUS or something similar to tell whether it is "Automatic", "Manual" or "Disabled" ?

[qix]

Can you also add one #SERVICESTARTSTATUS or something similar to tell whether it is "Automatic", "Manual" or "Disabled" ?

Shouldn't be too hard to do, however...I wanted to do a discovery on "automatic" services. Therefor, I'm using a filter to only return those services. The macro will never match Manual or Disabled in this case.

[alledm]

Unfortunately that's exactly what I need because we have loads of manual services that are time dependent and we only start them at specific times

[alledm]

Oh well looking at the code it seems extremely easy to change so I will do it myself.
Thank you for this

[qix]

In servdisc.ps1 remove:

| where-object { $_.StartMode -eq 'Auto' }

Change:

 $line =  " { `"{#SERVICESTATE}`":`"" + $objItem.State + "`" , `"{#SERVICEDISPLAY}`":`"" + $objItem.DisplayName + "`" , `"{#SERVICENAME}`":`"" + $objItem.Name + "`" , `"{#SERVICEDESC}`":`"" + $objItem.Description + "`" },"

To:
 $line =  " { `"{#SERVICESTART}`":`"" + $objItem.StartMode + "`" , `"{#SERVICESTATE}`":`"" + $objItem.State + "`" , `"{#SERVICEDISPLAY}`":`"" + $objItem.DisplayName + "`" , `"{#SERVICENAME}`":`"" + $objItem.Name + "`" , `"{#SERVICEDESC}`":`"" + $objItem.Description + "`" },"

That should do it

[qix]

The only problem is that you can only filter on one macro during LLD discovery phase. You could also adjust the

| where-object { $_.StartMode -eq 'Auto' }

to

| where-object { $_.StartMode -eq 'Manual' }

[thk]

Hi,

My first ZABBIX post and I'm rather new to Zabbix. So bare with me please.
I'm pretty much into monitoring and managing host on several systems, but my knowledge are limited to HP OM and IBM Omnibus.

This is an interesting post to get started on windows boxes, but I'm not that familiar with ZABBIX templates and LLD. Could someone be so kind to post a quick "how to" or "Step by step" for this Excellent Service-discovery.

I guess I would start by importing the xml template Template_Windows_Service_Discovery.xml, but it errors:

XML file contains fatal error 76:Opening and ending tag mismatch: meta line 44 and head [ Line: 51 | Column: 10 ]

So I'm guessing I'm doing it wrong already?

Cheers!

Ubuntu 12.04.
Zabbix server 2.04

Thomas

[garcaman]

you have to copy the xml content file in web page and paste for a note pad file, after that save this file with xml extention file and try again

[garcaman]

Windows Service LLD Discovery

Hello guys,

I've done the configuration for monitoring the windows services according the article "http://blog.zabbix.com/low-level-discovery-for-windows-services/1867/#more-1867".

I'm receiving the follow information in my host discovery rule "value should be a JSON object". What does it mean?

I dont know what I need to do in order to solve this problem, could you please guys help me on that?

Thanks in advance.

Leandro

[qix]

Hi Thomas,

Welcome to the forum and the Zabbix community!

Hi,

This is an interesting post to get started on windows boxes, but I'm not that familiar with ZABBIX templates and LLD. Could someone be so kind to post a quick "how to" or "Step by step" for this Excellent Service-discovery.

For a somewhat more detailed explanation see here:

http://blog.zabbix.com/low-level-discovery-for-windows-services/1867/

If you need any further help, please let us know. Make sure that the XML you are trying to import really is a proper XML formatted file.

Please do keep in mind that this is a workaround for the mentioned ticket, so if you want this functionality in a production environment, please vote for the ticket as well!

[qix]

Oh, and if you need some help in working with templates and such, you can check here: http://www.zbxtutorials.org/2012/08/...rs-course.html

It's for the 1.8 version of Zabbix, but the idea remains the same

[JPtheGeezer]

Hi,

I've been using the LLD and for 2K8 servers this works well, and for 2K3 servers the VBS file works to discover the services, it does take a long time to kick in and discover but I don't mind.

How do I now create an action to alert us about services stopping?

[JPtheGeezer]

Hello guys,

I've done the configuration for monitoring the windows services according the article "http://blog.zabbix.com/low-level-discovery-for-windows-services/1867/#more-1867".

I'm receiving the follow information in my host discovery rule "value should be a JSON object". What does it mean?

I dont know what I need to do in order to solve this problem, could you please guys help me on that?

Thanks in advance.

Leandro

Hi, I was having this issue too, you just need to make sure you do this:

1. In the CONF file on the servers the User Parameter line should read:

UserParameter=service.discovery,cscript /B c:\zabbix\servdisc.vbs

2. Make sure the VBS file is located in the same folder that is referenced in the CONF file.

3. Restart the service on the server.

4. Disable and re-enable the discovery on Zabbix for the host.

5. Wait for 30 mins and the services will start discovering and appearing in the items for that host.

6. If you still have problems it could be that the VBS file was downloaded and the code is all messed up. If this is the case just go back to the site and rather than downloading the code from your browser just click on the VBS file and let the code open on your browser page. Then just copy the code from your browser into the VBS file using a text editor like notepad or Notepad + (Plus).

After all that you should be fine.