[ZBX-2661] showing of same discovery checks with different ports Created: 2010 Jul 07 Updated: 2017 May 30 Resolved: 2010 Oct 13 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Frontend (F) |
Affects Version/s: | None |
Fix Version/s: | 1.8.4 |
Type: | Incident report | Priority: | Minor |
Reporter: | Aleksandrs Saveljevs | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
r13199 of 1.8 |
Attachments: | edit-discovery.png view-discovery.png |
Description |
(1a) In simple checks, we recently made the port parameter to tcp and tcp_perf mandatory, because port 80 has no particular reason for being a default port for TCP checks. Similarly here, in edit-discovery.png, we should always show the port used for TCP checks. (1b) This is not seen from edit-discovery.png, but after creating a Zabbix agent check and creating an SNMP agent check after it, the SNMP OID defaults to the agent's key. (2) When viewing a list of discovery rules, checks of the same type with a non-default port should have ports shown in parentheses. For TCP checks, the port should always be shown, same as (1a). See view-discovery.png. |
Comments |
Comment by Alexey Fukalov [ 2010 Sep 08 ] |
ports now are shown always. 1.b bug wasn't fixed it will be quite many not convenient changes for such a small bug, in future this should be rewritten anyway for JS support. |
Comment by richlv [ 2010 Sep 27 ] |
has this been committed anywhere ? what's the status of this issue ? |
Comment by Alexey Fukalov [ 2010 Sep 27 ] |
ye, dev branch: |
Comment by Alexey Fukalov [ 2010 Oct 13 ] |
branches/1.8 14838 |