-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seting up HTTP_TARGETS_TIMEOUT value make results unstable #131
Comments
Using goldpinger 3.9, I see the same behavior, we had some http targets that took longer than 500ms, and when trying to increase the timeout, the UI basically disappears. Just the presence of the http_targets_timeout seems to cause this issue. Any update on a possible solution or workaround? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
After setting this value the target appears and disappears from the UI.
I've tried also with and without double quotes, with and wihout 'ms'.
Logs from the daemonset don't show much and we see no option to increase logging level through an ENV variable.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The target website should appear green after increasing the timeout from the default "500ms" to "1000ms"
https://github.com/bloomberg/goldpinger/blob/95363554e4078ce20e4fe746ce98b332e472e469/pkg/goldpinger/config.go#LL56C1-L56C1
Environment (please complete the following information):
After removing the http timeout, the nodes come back green and the target website red
The text was updated successfully, but these errors were encountered: