Minimize requests to /metrics using some logic about connectivity from browser->server about jupyter-resource-usage HOT 1 OPEN

Thanks @consideRatio for all these details!

I suspect that the /metrics calls come from the [nbresuse]

It does indeed come from the nbresuse frontend:

• in the classic notebook extension: https://github.com/yuvipanda/nbresuse/blob/de920c0aec27467805e61678da2c8c61eecbbced/nbresuse/static/main.js#L36-L37
• in JupyterLab: https://github.com/jupyterlab/jupyterlab/blob/0b88d64b622fc03f4c06ce9cceaa13bc443db468/packages/statusbar/src/defaults/memoryUsage.tsx#L288-L291

/api/kernels - unknown interval

The polling logic for these endpoints is defined here:

https://github.com/jupyterlab/jupyterlab/blob/0b88d64b622fc03f4c06ce9cceaa13bc443db468/packages/services/src/kernel/manager.ts#L32-L40

hope it's possible to make use of a common interface to determine if the notebook-server / jupyter-server is available, and cut down on requests if it isn't.

Yes either this common interface (but it would have to be usable from multiple frontends), or use exponential backoff when making the requests.

For nbresuse specifically there has also been the idea of switching to event streams: #19

from jupyter-resource-usage.