Feature request: exposing server logs to a JupyterHub user - but how?

[consideRatio]

As a k8s admin of a JupyterHub deployed in k8s I commonly inspect logs of a user pod to help a user debug an issue. But how can we enable users do that themselves, and preferably not by locking into some k8s native tech?

Questions

• Does the notebook server or jupyter_server emit logs to a file as well?
• Can you use journalctl or similar?
• Can we configure a location to emit logs (because some paths won't be persistent between restarts and if the server crashes...).
• Can it be addressed from within the server itself, or must an external component be involved?

[manics]

Relevant discussions on BinderHub and repo2docker:

• Persist repository build logs for later access binderhub#1156 (comment)
• [MRG] Stream jupyter server logs to a file repo2docker#987
• Investigating the missing logs repo2docker#1008
• reimplement entrypoint in Python repo2docker#1014