[ZBXNEXT-3635] Allow multiple service.discovery keys Created: 2016 Dec 27  Updated: 2016 Dec 27  Resolved: 2016 Dec 27

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Agent (G), Frontend (F), Server (S)
Affects Version/s: 3.2.2
Fix Version/s: None

Type: Change Request Priority: Trivial
Reporter: Janne Korkkula Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: agent, windows
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates ZBXNEXT-1606 a way to use multiple lld rules for s... Confirmed

 Description   

The Windows agent service.discovery key/LLD is extremely convenient, but not all services are created equal; We need different kinds of item/trigger prototypes for different kinds of services, tied to application specific templates.

As service.discovery is an agent item with a static name, only one such item can exist per host/template, even though a different filter makes the item practically unique. The most simple approach would be to allow a parameter (which doesn't need to do anything) for the service.discovery item, thus the key would be different and everything would just work.



 Comments   
Comment by Aleksandrs Saveljevs [ 2016 Dec 27 ]

Looks like a duplicate of ZBXNEXT-1606.

Comment by Glebs Ivanovskis (Inactive) [ 2016 Dec 27 ]

ZBXNEXT-3206 is an official solution to this problem.

Generated at Sat Jan 11 02:57:10 EET 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.