Hey folks, I've been researching options for enabling user activity monitoring in Jupyter notebooks, and I've come across various related topics here in the group and in GitHub over the last year or two [1][2][3][4]. My use case is deploying JupyterHub in an environment where compliance requirements compel us to record all user activity on their notebook server.
gclen's implementation in [4] is the simpler of the approaches listed back in last year's discussion [2], being very specifically logging-based with the python logger config file for the kernel messages the only config option. There was also mention of what sounded like a more general 'message middleware' kind of approach where logging would just be something you could add to a configurable pipeline of pre/post message processors that could enable much more powerful and far-reaching customisations. My question is; before I dive in too far into reviving the simple logging approach for the kernel message handler is there any opposition to taking this route now? Is kernel message-handling middleware a thing that might be on the horizon that would clash with this approach, or could we possibly go ahead and just move auditing/logging concerns around later should that become a reality? Cheers Gary [1]https://groups.google.com/d/msg/jupyter/bZlWn_Tas1c/WN5w4T6GCwAJ [2]https://groups.google.com/d/msg/jupyter/sLKCCBwlKEc/CqrvYCvfBwAJ [3]https://github.com/jupyter/notebook/issues/4136 [4]https://github.com/jupyter/notebook/issues/2251 -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/327b8191-f53c-4e39-9c5b-0dea4af8b9d8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
