You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"My kernel restarted, why?" is one of the most common support questions when supporting JupyterHubs. Being able to tell when a kernel was restarted - ideally being able to differentiate between user initiated restarts and nanny initiated restarts - would be extremely helpful to JupyterHub admins in providing this support, as well as detecting when memory limits and guarantees need to be changed (because too many users are running into memory limits)
The text was updated successfully, but these errors were encountered:
Should the metric include the kernel ID? It might be useful if you want to identify a specific kernel that's restarting a lot (e.g. correlating it with logs), but I'm not sure that's usually useful.
"My kernel restarted, why?" is one of the most common support questions when supporting JupyterHubs. Being able to tell when a kernel was restarted - ideally being able to differentiate between user initiated restarts and nanny initiated restarts - would be extremely helpful to JupyterHub admins in providing this support, as well as detecting when memory limits and guarantees need to be changed (because too many users are running into memory limits)
The text was updated successfully, but these errors were encountered: