Skip to content
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

Closed
mikkeloscar opened this issue Oct 28, 2016 · 4 comments
Closed

Connection drops when doing kubectl logs or exec #49

mikkeloscar opened this issue Oct 28, 2016 · 4 comments
Labels

Comments

@mikkeloscar
Copy link
Contributor

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.

@hjacobs
Copy link
Contributor

hjacobs commented Nov 17, 2016

I'll try to reproduce this too.

@hjacobs
Copy link
Contributor

hjacobs commented Nov 17, 2016

This looks like idle timeout as it does not happen if we output something every 10s:

$ zalando-kubectl exec -it mypod bash
root@deploy01-0:/# while true; do sleep 10; date; done
Thu Nov 17 12:04:06 UTC 2016
...
Thu Nov 17 12:25:07 UTC 2016

hjacobs added a commit that referenced this issue Nov 17, 2016
hjacobs added a commit that referenced this issue Nov 17, 2016
@hjacobs
Copy link
Contributor

hjacobs commented Nov 21, 2016

@mikkeloscar can you try again? Are 5 minutes good enough as idle timeout for you?

@hjacobs
Copy link
Contributor

hjacobs commented Dec 6, 2016

@mikkeloscar closing this for now --- I assume everybody is happy with the current 5 minutes idle timeout.

@hjacobs hjacobs closed this as completed Dec 6, 2016
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
Labels
Projects
None yet
Development

No branches or pull requests

2 participants