[ZBXNEXT-3295] Add optional timeout parameter to items like net.tcp.port, net.tcp.service, ... Created: 2016 Jun 06 Updated: 2023 Sep 27 Resolved: 2023 Sep 27 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Agent (G), Server (S) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Change Request | Priority: | Minor |
| Reporter: | Selivanov Pavel | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 4 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
This will create more flexibility for such checks, and will allow to escape problems like this: Important: if given timeout is more than timeout in agent or server config, it should create a warning. |
| Comments |
| Comment by Aleksandrs Saveljevs [ 2016 Jun 06 ] |
|
Similar request specifically for SSH checks: |
| Comment by Aleksandrs Saveljevs [ 2016 Jun 06 ] |
Why should it give a warning? Shouldn't the item timeout override Timeout in the configuration file? |
| Comment by Selivanov Pavel [ 2016 Jun 06 ] |
|
> Why should it give a warning? Shouldn't the item timeout override Timeout in the configuration file? |
| Comment by Aleksandrs Saveljevs [ 2016 Jun 06 ] |
If we make the item timeout override Timeout in the agent configuration file, then that is not a problem. The important thing is how the item timeout relates to Timeout in the server configuration file, assuming that passive agent checks are used. |
| Comment by Selivanov Pavel [ 2016 Jun 06 ] |
|
Well, anyway there should be note in documentation and warnings in web interface (like the ones for items with incorrect type, ...). Users should not get unexpected behavior just because they didn't memorize whole server config. |
| Comment by Dmitrijs Goloscapovs [ 2023 Sep 27 ] |
|
Versatile timeouts (including configurable timeouts for simple checks) have been implemented in 7.0.0alpha5. Please follow |