[ZBXNEXT-2721] Ability to configure timeout on network discoveries Created: 2015 Feb 20 Updated: 2024 Mar 20 Resolved: 2024 Mar 20 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Frontend (F), Proxy (P), Server (S) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Trivial |
| Reporter: | Raymond Kuiper | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 9 |
| Labels: | networkdiscovery, timeout | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
When running a SNMP based discovery on the network, scanning each host for a response is very, very slow. I suspect the normal timeout value from the server config file is being used. As this setting is set to 10 seconds, it'll could take about 2550 second to scan a /24 network for a single SNMP check. If we were able to configure the timeout (preferably in ms) on the discovery rule, we could lower the amount of time it takes. |
| Comments |
| Comment by Oleksii Zagorskyi [ 2015 Feb 21 ] |
|
I absolutely support that. I recall related discussions in the past. For network discovery it should be indeed separated from regular checks. Preferably on a discovery check level, or maybe on discovery rule would be enough. Timeout consideration being changed in different versions as bug fixes or as new features, for example |
| Comment by Oleksii Zagorskyi [ 2015 Jul 08 ] |
|
Just a note - current feature request has been mentioned in |
| Comment by Aleksandrs Saveljevs [ 2016 Jan 28 ] |
|
As mentioned by kodai, it would also be nice to configure the number of SNMP retries for network discovery, similar to |