Hi All
So looking at various discussions on the forums, there are many solutions to automatically discovery Linux and Windows Services and Processes via LLD. Extremely helpful in a high volume environment.
The issue I am currently facing with LLD Services, as an example, is when it comes to Trigger Prototypes i.e.
Client Side
UserParameter=windows.services,"C:\Program Files\Zabbix Agent\bin\services.exe"
Server Side
Discovery Rule -> Service Discovery
Type -> Zabbix Agent
Key -> windows.services
Item Prototype -> Service state of {#FSSERNAME} *** {$1}
Type -> Zabbix Agent
service_state[{#FSSERVICE}]
etc.
When applied to my 300+ windows servers I get current service states for all windows servers on all services. Cool!
Problem?NoProblem?
ZBXNEXT-1368 - Keith Braithwaite pretty much hits the nail on the head, I've got this cool feature to auto discover all these services but when I try and create "trigger prototypes" i'm left with very limiting options to create triggers for my 50+ important windows services. Currently, this has lead me to create Templates for the different groups of Windows Services and Create Items, Triggers etc. for each group.... kinda defeating the whole point of LLD Discovery.
Am I looking at this completely wrong?
What I would like to achieve is a list of triggers for different service states on Item Prototypes where {#FSSERNAME} = "Microsoft SQL Server" or Item Prototype where {#FSSERNAME} = "Airwatch Mobile Manager" etc.
Thanks for your time!
So looking at various discussions on the forums, there are many solutions to automatically discovery Linux and Windows Services and Processes via LLD. Extremely helpful in a high volume environment.
The issue I am currently facing with LLD Services, as an example, is when it comes to Trigger Prototypes i.e.
Client Side
UserParameter=windows.services,"C:\Program Files\Zabbix Agent\bin\services.exe"
Server Side
Discovery Rule -> Service Discovery
Type -> Zabbix Agent
Key -> windows.services
Item Prototype -> Service state of {#FSSERNAME} *** {$1}
Type -> Zabbix Agent
service_state[{#FSSERVICE}]
etc.
When applied to my 300+ windows servers I get current service states for all windows servers on all services. Cool!
Problem?NoProblem?
ZBXNEXT-1368 - Keith Braithwaite pretty much hits the nail on the head, I've got this cool feature to auto discover all these services but when I try and create "trigger prototypes" i'm left with very limiting options to create triggers for my 50+ important windows services. Currently, this has lead me to create Templates for the different groups of Windows Services and Create Items, Triggers etc. for each group.... kinda defeating the whole point of LLD Discovery.
Am I looking at this completely wrong?
What I would like to achieve is a list of triggers for different service states on Item Prototypes where {#FSSERNAME} = "Microsoft SQL Server" or Item Prototype where {#FSSERNAME} = "Airwatch Mobile Manager" etc.
Thanks for your time!
Comment