[ZBXNEXT-6380] Add new vmware keys for cluster monitoring Created: 2020 Dec 04 Updated: 2024 Apr 10 Resolved: 2021 Jan 18 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Proxy (P), Server (S) |
Affects Version/s: | None |
Fix Version/s: | 5.4.0alpha1, 5.4 (plan) |
Type: | Change Request | Priority: | Minor |
Reporter: | Elina Kuzyutkina (Inactive) | Assignee: | Dmitrijs Goloscapovs |
Resolution: | Fixed | Votes: | 0 |
Labels: | VMware | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: | ZBXNEXT-6380-52.patch | ||||
Issue Links: |
|
||||
Team: | Team C | ||||
Sprint: | Sprint 71 (Dec 2020), Sprint 72 (Jan 2021) | ||||
Story Points: | 0.5 |
Description |
Hello! vmware.cl.perfcounter[<url>,<id>,<path>,<instance>] or specific key for each available cluster metric (there are not so many) from the link |
Comments |
Comment by Dmitrijs Goloscapovs [ 2020 Dec 29 ] |
Available in:
Updated documentation: |
Comment by Marco Hofmann [ 2021 Mar 30 ] |
Will there be new templates, that honor the new features? |
Comment by Michael Veksler [ 2021 Mar 30 ] |
Not planned. But you can create ZBX. |
Comment by Seth Simmons [ 2021 Nov 03 ] |
Is there any evidence of this working properly? Per https://support.zabbix.com/browse/ZBX-20117, it doesn't appear to function due to an issue with instance/metricID no matter the instance specified (or left default ""). |
Comment by Michael Veksler [ 2022 Jan 05 ] |
Dear setsimmo The response to Your question here |