-
New Feature Request
-
Resolution: Duplicate
-
Critical
-
None
-
4.0.0alpha4
-
Sprint 33
-
5
Because of ZBXNEXT-1490 and lack of ZBXNEXT-735, defining multiple host interfaces of same type is actually of little use.
Nevertheless I took the challenge and use the space-work-around to achieve item key uniqueness and take on the burden of manually updating every single LLD prototype and rule of every single host due to ZBXNEXT-1190 and ZBXNEXT-1451.
However there is another hurdle to overcome. Network errors on one host interface may interfere operation of other host interfaces of same type.
I've got a 3rd party application Zorka in place that makes use Zabbix agent protocol. Thus there is an additional Zabbix agent host interface dedicated to Zorka on the corresponding hosts.
Whenever Zorka agent is not reachable (eg. application server stopped), it may lead to stop Zabbix agent related checks as well.
This makes using multiple host interfaces of same type finally unusable at all.
Would be nice to get this fixed - and the other mentioned shortcomings of course too
- causes
-
ZBXNEXT-195 Proposal: Privilege separation for ZABBIX agent
- Open
- depends on
-
ZBXNEXT-4676 Process Not supported SSH items with Unreachable Poller
- Open
- duplicates
-
ZBXNEXT-6311 Move host availability to host interfaces
- Closed
- is duplicated by
-
ZBX-6789 Host unavailable handling with multible JMX
- Closed
-
ZBX-8854 jmx agent wrong issue and intermittent graphs
- Closed
-
ZBX-8855 Zabbix wrong alert on host with multiple jmx interfaces
- Closed
- mentioned in
-
Page Loading...