[ZBXNEXT-5003] Improve Zabbix operation usability Created: 2019 Feb 05  Updated: 2019 Feb 25  Resolved: 2019 Feb 06

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

Type: New Feature Request Priority: Major
Reporter: T.J. Yang Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: frontend, usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2019-02-05-12-01-42-723.png    

 Description   

Hi 

In other monitoring solution(Ex: Nagios Core), one usually can configure the monitoring server to test out the configuration right away.   Form my limited usage of Zabbix 4.2alph3 so far I found followings:

  1. One can configure ldap server binding and check the LDAP configuration right away which is expected.
  2. But when one configure a mail server (media type), we can not test out the mail server connection right away and had to go extra further to trigger and email sending. ( I know this is being requested on another issue.
  3. When adding a new host on the Zabbix server side, one can't issue the zabbix connection from server's GUI. This is a minus for Zabbix operation usability.

 Comments   
Comment by richlv [ 2019 Feb 05 ]

1. Does not seem to be a problem.
2. Is a duplicate of ZBXNEXT-1238.
3. Seems to be mostly covered by ZBXNEXT-473 - but by design, Zabbix can have so many different ways to connect, it cannot be covered by a single method anyway.

Comment by T.J. Yang [ 2019 Feb 05 ]

Hi Richlv

Thanks for the response. 

  • yes. 1. is not a problem I wanted to report. it should be an expected feacture to test out ldap connection right after GUI configuration. 2. has been worked on for long time.
  • For  3. I like to use following  screenshot as example.

  •  from red popup tooltip, I know miqregion01 was not added into DNS server on test.lan. If would be great if I can have another button called  "check now" beside "Delete" once I registered miqregions01.
  • Is this being worked on in another issue ? 
Comment by T.J. Yang [ 2019 Feb 06 ]

Will create another issue on 3. 

Generated at Thu Apr 25 01:23:17 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.