Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Cannot modify 'Request Timeout (Timeout after XX seconds)' #5445

Open
2 tasks done
nowniz opened this issue Dec 17, 2024 · 5 comments
Open
2 tasks done

Cannot modify 'Request Timeout (Timeout after XX seconds)' #5445

nowniz opened this issue Dec 17, 2024 · 5 comments
Labels

Comments

@nowniz
Copy link

nowniz commented Dec 17, 2024

⚠️ Please verify that this question has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

The item in each monitor > Edit > General > 'Request Timeout' does not change from previous value
For exampple, even if I change a number other than 16 and click 'Save', the status value is reflected as 16.
I am using the Docker version with the beta tag, but I would like to inquire whether the bug only occurs in that version.

📝 Error Message(s) or Log

Dec-17-2024 17-16-36

🐻 Uptime-Kuma Version

2.0.0-beta.0

💻 Operating System and Arch

Amazon Linux release 2023.4.20240401, Docker

🌐 Browser

Google Chrome 128.0.6613.120

🖥️ Deployment Environment

  • Runtime: Docker 25.0.3
  • Database: sqlite
  • Filesystem used to store the database on: Amazon EBS gp3 (SSD)
  • number of monitors: 58
@nowniz nowniz added the help label Dec 17, 2024
@homelab-alpha
Copy link
Contributor

@nowniz, If I’m correct, the minimum values are 20 seconds when setting the following settings: Heartbeat Interval, Heartbeat Retry Interval, and Request Timeout.

@nowniz
Copy link
Author

nowniz commented Dec 18, 2024

@homelab-alpha , The screen above showing the change process from 16s to 12s is an example. In reality, if �I click 'save' with over 20 seconds value has changed more than most values, it's retaining the previous value before keeping it changed.

@homelab-alpha
Copy link
Contributor

@nowniz, It seems that a calculation is being performed in the background involving the Heartbeat Interval, Heartbeat Retry, and Request Timeout. When you adjust the Heartbeat Interval, the other two values are also automatically adjusted.

Although the minimum value for both the Heartbeat Interval and Heartbeat Retry is 20 seconds, this does not appear to apply to the Request Timeout.

Based on my testing, it is possible to set the Request Timeout to 12 seconds or lower; however, after saving, it reverts back to 16 seconds. It seems that the minimum value for Request Timeout is 16 seconds.

Personally, I don’t fully understand the logic behind this calculation. Is there a specific reason for setting it lower than 16 seconds?

@nowniz
Copy link
Author

nowniz commented Dec 18, 2024

@homelab-alpha ,
I tried to maintain the settings (12s) from the previous version, version 1.23.11.
As you mentioned, it appears that the 'Request Response' value is determined depending on the 'Heartbeat Interval' value and a certain operation of 'Heartbeat Retry'.

So, isn't it possible to set only the Request Response value separately and separately?

@homelab-alpha
Copy link
Contributor

@nowniz, I'm not sure about that. It seems that it's not possible if the other two have a minimum value of 20 seconds.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants