Configuration of discovery rules

[753713]

has anyone examples or howto of "CONFIGURATION OF DISCOVERY RULES" in the version 1.9?

thanks
753713

[zalex_ua]

Documentation (draft) about Low Level Discovery already exists, but it is not yet available for all to read. Ask a developers for documentation.

I've tested LLD a lot.

[zalex_ua]

I was looking to test the low level documentation. From the forums you have said that you have received a copy. Can you send it my way?

So, thanks to your request, the developers have opened access to the 2.0 documentation.
Read:
http://www.zabbix.com/documentation/...ig/lldiscovery

[753713]

Thanks!!!
I will test LLD in my network next week.

[zalex_ua]

Thanks!!!
I will test LLD in my network next week.

The tracker has several ZBXNEXT created by me , which related to LLD.
Take a look and if you agree then you can vote.

[753713]

HD Monitoring running without problems in my enviroment ,
but how I can browse services in windows?

many thanks,
753713

[zalex_ua]

HD Monitoring running without problems in my enviroment ,

HD? cool! but this is typo

but how I can browse services in windows?

I do not see any sense in this

See services[<type>,<state>,<exclude>] key.

[753713]

with services[<type>,<state>,<exclude>] I have only a list with services.

The idea is, I discover all (running/stoped/disabled) services on my win server, I create a rule and item prototype and I can see all services and services states (similar snmp interfaces discovery).

Here my screenshot with manually configuration.

[sbockelman]

Using LLD Macros in trigger equations

Here is what I am trying to accomplish. Custom vfs.fs.discovery that will return the following on each server:

{#FSNAME} - name of the filesystem
{#FSTYPE} - type of filesystem
{#FSTRIGGER} - value in % that trigger will alert. This value will be pulled in from a file stored locally on a server or return a default. ie 90

So for each filesystem, I will be able to modify what % the trigger gets set off at.

This is what I want my trigger to look like:
{Template_OS_Linux:vfs.fs.size[{#FSNAME},pused].last(0)}>{#FSTRIGGER}

However, after saving I get:
ERROR: Cannot update trigger
* Array

Is this just a bug in zabbix 1.9.1?