[ZBX-22774] HTTP agent timeout (redfish) Created: 2023 May 08  Updated: 2023 May 09  Resolved: 2023 May 09

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: files Assignee: Zabbix Support Team
Resolution: Won't fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Zabbix server and proxies are running on Rocky linux 9.1.
Zabbix server and proxies version 6.4.1

Attachments: JPEG File zabbix.JPG    

 Description   

Hello,

I am using DELL PowerEdge R740 by HTTP template for servers monitoring.
https://www.zabbix.com/integrations/dell_r740_http

I have made various modifications and added additional items and discovery rules in order to have monitoring of all major server components.
Everything works great expect timeouts.

Server parts (disks, fans, etc) are discovered using discovery rules.
Each discovery rule (type HTTP agent) has timeout setting and it maximum value is 60s. Zabbix does not allow setting timeout value to 5m for example. Trying to set timeout to move than 60s gives error.

Error is: Invalid parameter "/timeout": value must be one of 1-60.

60 seconds is not enough in order to get response (collect all data) from iDrac via redfish.
Some parts like {$API.URL}/redfish/v1/Systems/System.Embedded.1/Storage can have 20+ elements and getting data from all these elements requires more time.
iDrac redfish api some times can be really slow, especially if it's not latest generation server.

I have modified discovery rules in order to collect lest data, but 60s timeout is still not enough.

Can anyone please advise how to overcome this limitation?

Thanks!

 

 Comments   
Comment by Edgar Akhmetshin [ 2023 May 09 ]

You need to open support case with DELL and troubleshoot why device is not able to provide small amount of information related to the hardware using API.

Please be advised that this section of the tracker is for bug reports only. The case you have submitted can not be qualified as one, so please reach out to [email protected] for commercial support (https://zabbix.com/support) or consultancy services. Alternatively, you can also use our IRC channel or community forum (https://www.zabbix.com/forum) for assistance. With that said, we are closing this ticket. Thank you for understanding.

Generated at Tue Apr 29 10:20:52 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.