[ZBXNEXT-5478] Screen: Auto Add Graphs For Each Hosts That Uses A Template Created: 2019 Oct 01  Updated: 2019 Oct 12

Status: Reopened
Project: ZABBIX FEATURE REQUESTS
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Request Priority: Major
Reporter: Abhishek Dasgupta Assignee: Zabbix Support Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2019-10-01 at 2.56.09 AM.png    

 Description   

We have a template with an item and associated trigger and graph.

Currently to see the graph for each host that uses that template in a screen, we need to manually add the graph for each host.

Considering our ecosystem is in AWS with numerous dynamic hosts, it's really painful to keep updating this screen manually each time the host set changes.

 

We would like to see an option to add a graph from template. Then the screen will find out which all host uses that template and show its corresponding graph. Something similar to how graph prototype works for a single host.

 

Following is an example of manually created screen -

 



 Comments   
Comment by dimir [ 2019 Oct 02 ]

Closing as duplicate of ZBXNEXT-927

Comment by Abhishek Dasgupta [ 2019 Oct 02 ]

How is this a duplicate? That one talks about same host, this one spans across multiple hosts and has nothing to do with LLD. This request is purely to add a feature to create screen with graph from template. And then screen automatically figure out which all hosts using that graph and render them.

Comment by dimir [ 2019 Oct 03 ]

Oh, sorry. Misunderstood the description.

Somewhat similar issue ZBXNEXT-927 - asks for grouping graphs of items created from LLD. 

Comment by Abhishek Dasgupta [ 2019 Oct 12 ]

Any plan so far to get this implemented anytime soon? We are migrating to latest version (4.4) and creating all these screens is very tedious without this proposed solution.

Generated at Wed Jul 16 10:20:05 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.