-
Notifications
You must be signed in to change notification settings - Fork 163
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
Connection drops when doing kubectl logs
or exec
#49
Labels
Comments
I'll try to reproduce this too. |
This looks like idle timeout as it does not happen if we output something every 10s:
|
hjacobs
added a commit
that referenced
this issue
Nov 17, 2016
hjacobs
added a commit
that referenced
this issue
Nov 17, 2016
#49 set API ELB idle timeout to 5 min
@mikkeloscar can you try again? Are 5 minutes good enough as idle timeout for you? |
@mikkeloscar closing this for now --- I assume everybody is happy with the current 5 minutes idle timeout. |
femueller
pushed a commit
that referenced
this issue
Oct 5, 2018
* Fix empty strict_labels skipping all containers (#70) * Additionally pass 'environment' label to Scalyr (#69) * Fixes bug that strict labels are configured but not checked against (#67) * Fixes bug that strict labels are configured but not checked against * Updated test to verify if `strict_labels` are passed from down properly * Fixed formatting in test * Adds configurable JSON log parsing(#49) (#66) * With the new configuration parameter `WATCHER_SCALYR_PARSE_LINES_JSON` the Scalyr agent can be configured to parse log lines as JSON entries which is useful to process raw Docker logs. This behaviour is disabled by default. Signed-off-by: Felix Mueller <felix.mueller@zalando.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I often see the connection drop when following the logs of a pod or when exec'ing into a pod.
This usually happens after 30-60 secs.
The text was updated successfully, but these errors were encountered: