[ZBXNEXT-2279] zabbix[proxy,,lastaccess] internal item should be always performed by server Created: 2014 Apr 23 Updated: 2018 Jan 11 Resolved: 2014 Jul 17 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Proxy (P), Server (S) |
| Affects Version/s: | 2.2.3 |
| Fix Version/s: | 2.3.3 |
| Type: | New Feature Request | Priority: | Minor |
| Reporter: | Gabriele Armao | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | internalmonitoring, proxy | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
it would be very useful if the zabbix[proxy,,lastaccess] internal item would always be performed by Zabbix Server even if the item is configured on a host monitored by a Zabbix Proxy, in this way, it would be trivial to add to the existing Zabbix Proxy Template an item that checks if the Zabbix Proxy is reporting correctly to the Server. |
| Comments |
| Comment by richlv [ 2014 Jul 16 ] |
|
this will most likely be solved in |
| Comment by Alexander Vladishev [ 2014 Jul 17 ] |
|
Available in pre-2.3.3 (trunk) r47422. |
| Comment by Martins Valkovskis [ 2014 Jul 18 ] |
|
Documented with sasha CLOSED |
| Comment by OFN Team [ 2014 Jul 31 ] |
|
I think that new zabbix should provide special key which will generate json string which can be used on add monitoring of zabbix[proxy,<proxy_name>,lastaccess] over LLD .. if something like this is not implemented yet. Without this probably will be quite hard to maintain proxies availability monitoring in environments where set of proxies is not static. sasha Moved to ZBXNEXT-2548. |
| Comment by Oleksii Zagorskyi [ 2015 Mar 10 ] |
|
It worth to mention that the proxy name (2nd item key param) is still required. But |