Make JupyterLab logs visible inside JupyterLab

[ManPython]

Problem

Whe jupyter is used on hosting, cloud when user is no admin or if app is run as screen comand via terminal, then hard to analyse some problems/issues, logs.

Proposed Solution

Want suggest to add some card/tab with logs on jupyter web app like lnx terminal.

Additional context

[welcome]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.

You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

[fcollonval]

This repository does not seems to fit your issue. You are speaking of server logs for JupyterLab?

One comment on the issue itself, the way logs are stored/configured is highly dependent on the hosting platform set up. So having a generic way may not be easy.

[ManPython]

You are speaking of server logs for JupyterLab?

Yes, as Python. Sure.. are stored, but must operate on terminal, restart app outside screen function to see whats is wrong, wg. why reseting, why binding on series of python versions not working, how many resets, etc.
I was in idea that this can be good option to offer for some users this tatb, eg. configured privilages in configs to access this.
This touching both JupyterLab and pure Jupyter. Wrong addres?

[krassowski]

Wrong addres?

You originally opened this issue in jupyterlab/team-compass repository which is for a high-level discussions abut the project and coordination between contributors. The repository for tracking issues and enhancements in JupyterLab is jupyterlab/jupyterlab. Sometimes search engines suggest a wrong repository. I transferred the issue.

As for the issue itself, I think that jupyter-events may enable this kind of event tracking.

I recall that there are several other issues about exposing logs already open - would you mind searching in jupyterlab/jupyterlab issueas and if you find an issue which already discusses it, link it here and clarify if your request differs from the earlier ones?

[JasonWeill]

Similar issue: #7411 (concerns logging for terminals spawned inside JupyterLab)

For people using remotely-hosted JupyterLab, an admin would benefit from being able to access logs inside JupyterLab. We would need an opt-in solution; only an administrator should be able to see server logs inside JupyterLab so that less-privileged users don't see any log data that they shouldn't.

[krassowski]

The discussion on the server-side is happening in jupyter-server/jupyter_server#684.

I think we can implement this with a sever extension building upon this with jupyter-events on the server side and our new API for events introduced in #12667 writing to logs console component.