[ZBXNEXT-5049] Network Discovery :: Save progress state of current discovery rule check to persist discoverer process termination Created: 2015 Dec 14  Updated: 2019 Feb 17

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: Proxy (P), Server (S)
Affects Version/s: None
Fix Version/s: None

Type: New Feature Request Priority: Trivial
Reporter: James Lodge Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: networkdiscovery, performance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

All



 Description   

Right now network discovery is very slow due to the serial nature of the 1:1 mapping of rules to discoverer process. Its exacerbated by having multiple check within a single network discovery rule.

The issue is if the discoverer process is terminated, e.g. stop/start zabbix_server or zabbix_proxy then the network discovery starts from the very first host in the subnet. It could have been that your were 3/4 on the way through the subnet in the network discovery rule, but now you're back to square one. It seems like state could be save in a table to be retrieved once the discoverer process starts executing the checks so that it resumes from the last ( or near as) IP:Port/Protocol rather than from the beginning.


Generated at Thu Mar 28 16:08:32 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.