I'd like to see if mybinder's analytics-publisher can be moved upstream to the main Binderhub chart? Or if it could be pushed to a chart of its own? I started the process of copying the existing analytics-publisher bits from this repo to pangeo-binder but quickly realized that may not be the best way to proceed.
Making its own package out of it so that it is easier to reuse in other binder deployments makes sense.
Maybe @yuvipanda has interest/time to do so or work with you to do it. I think it would be Ok for @jhamman to create the package, chart, etc for doing this and we later move it back into the jupyterhub org or leave it with you for maintenance (or some such).
I think this would be great - I'm not sure whether @yuvipanda has documented the service that the publisher performs but I'm happy to help write up some docs and deployment information as a first step, then we could look into integrating into the helm chart over time
There's docs on using it here: https://mybinder-sre.readthedocs.io/en/latest/analytics/events-archive.html
This issue and PRs linked in https://github.com/jupyterhub/mybinder.org-deploy/issues/789 should be useful.
The code in BinderHub itself is very generic, and has no direct dependency on Google Cloud or any particular logging solution. https://binderhub.readthedocs.io/en/latest/eventlogging.html has docs on how to use that.
Would love for someone to take this on! It should be a package by itself, and something we should include as a separate chart at least to begin with.
Am happy to answer more questions if need be.
Most helpful comment
There's docs on using it here: https://mybinder-sre.readthedocs.io/en/latest/analytics/events-archive.html
This issue and PRs linked in https://github.com/jupyterhub/mybinder.org-deploy/issues/789 should be useful.
The code in BinderHub itself is very generic, and has no direct dependency on Google Cloud or any particular logging solution. https://binderhub.readthedocs.io/en/latest/eventlogging.html has docs on how to use that.
Would love for someone to take this on! It should be a package by itself, and something we should include as a separate chart at least to begin with.
Am happy to answer more questions if need be.