Team A
[ZBX-22831] network discovery does not identified already monitored hosts Created: 2023 May 22 Updated: 2024 Apr 10 |
|
| Status: | Reopened |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 6.4.2 |
| Fix Version/s: | None |
| Type: | Problem report | Priority: | Trivial |
| Reporter: | Steven Brickell | Assignee: | Zabbix Support Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
container zabbix-server-mysql |
||
| Team: | Team A |
| Description |
|
Steps to reproduce:
Result: the network discovery does identify many hosts that have already been configured as "monitored host"s. however, it does identify all already monitored hosts as such. Expected: |
| Comments |
| Comment by Edgar Akhmetshin [ 2023 May 24 ] |
|
Hello
Could you please describe the problem? https://www.zabbix.com/documentation/6.0/en/manual/discovery/network_discovery |
| Comment by Steven Brickell [ 2023 Jun 04 ] |
|
This must be a joke? You ask me to describe the problem while quoting the description and at the same time - not understanding the problem you close the issue? How is issue tracking supposed to work properly? |
| Comment by Steven Brickell [ 2023 Jun 04 ] |
|
You already quoted the problem description. What about this is unclear to you, please aleborate. |
| Comment by Steven Brickell [ 2023 Jun 06 ] |
|
The problem has been described and is not resolved.
|
| Comment by Peterson Basso [ 2023 Sep 11 ] |
|
Discovery guarantees uniqueness only on the same proxy, hosts discovered by different proxies are always treated as different hosts, wouldn't that be your case? |