[ZBXNEXT-9492] Change "VMware SD-WAN VeloCloud by HTTP" template to use host prototypes instead of dependent items Created: 2024 Sep 17 Updated: 2025 Dec 29 Resolved: 2025 Dec 12 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Templates (T) |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.22rc1, 7.4.6rc1, 8.0.0alpha2 |
| Type: | Change Request | Priority: | Minor |
| Reporter: | Tomass Janis Bross | Assignee: | Evgenii Gordymov |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 129.5h | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
VeloCloud SD-WAN Edge by HTTP_7.0_Edit 2025.md
image-2025-11-17-13-36-36-720.png
screenshot-1.png
|
||||
| Issue Links: |
|
||||
| Team: |  Team INT |
||||
| Story Points: | 3 | ||||
| Description |
|
Currently due to the limit of 29999 dependent items it is quite easy to lose ability to monitor VMware SD-WAN VeloCloud because of the dependent item limit. With issues like https://support.zabbix.com/browse/ZBXNEXT-9233 being scheduled for 7.2, it will take some time before it is released, and dependent item limit is increased. In the meantime, it could be possible to re-work the template to be something similar like the "Cisco Meraki Dashboard by HTTP" template, where host prototypes are used to create hosts inside of Zabbix based on the discovered devices, and a template is attached to them to actually perform the monitoring. The "WMware SD-WAN VeloCloud by HTTP" is similar in the way that it also discovers devices - Edge routers and Gateways, so creating hosts from host prototypes for these discovered devices makes sense, and also will help with hitting the dependent item limit. |
| Comments |
| Comment by Andrew Harris [ 2024 Sep 17 ] |
|
As a reference point, we currently have 2,704 edges in our VMWare/Velocloud deployment. With the 8 out of box item prototypes, that's 21,632 dependent items just for edges. 2 links per edge (a primary and backup connection) is our standard, which means 5,408 links which gives us another 54,080 dependent items with the out of box VMware SD-WAN VeloCloud by HTTP template. We disabled them trying to get us under the limit but Peers and path metric item counts basically scale with edges so you can see where this is going. While the proposed item limit increase in 7.2 should at least allow all items to be created, it's still a bit of a UI/Navigation nightmare. The otherwise functioning normally web server config had to be changed (upgrading memory limits, etc) to handle viewing items, latest data, and so how just for this host. Trying to find link data or graphs for a specific edge is painful. It's also important to note that unless you're aware of the item limit, you likely not aware there's an issue as there's nothing in the UI telling you that you're missing data. With 30,000 items there's no practical way to audit if anything is missing. You can see you've got links, edges, gateways, so you assume all is well. Last but not least, the script struggles to complete even with timeouts increased to max as it's returning 300MB+ of data. |
| Comment by Evgenii Gordymov [ 2025 Nov 26 ] |
|
Available in:
|
| Comment by Marianna Zvaigzne [ 2025 Dec 04 ] |
|
Documented in: |