-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EPIC] Collect analytics information from all our binderhub ui installations #4365
Comments
I identified more complexity @yuvipanda, so refining this properly takes a bit of time for me. The complexity was that:
Adding google-cloud-logging is simple, but the other parts led me to think. We could go for adding extraVolume and adding the creation of a k8s Secret in basehub with misc info to mount in binderhub-service - but - since we anyhow add google-cloud-logging we can reasonably also setup chart config to consume google credentials in binderhub-service as well. I think adding this to binderhub-service is the right call, so I'm now refining things towards that. |
Refinement complete! |
Success for all five binderhub-ui enabled hubs we have running! Related extra things: |
This is so cool! I am intrigued to build some kind of aggregator to identify which repos are launched most often. |
To be collectively refined (EDIT: Done!) by me and @consideRatio after the outcome of #4309
Refined text
The goal with this work is ensure an ability in the future to internally produce reports that can summarize launch events over time from any of our binderhub-ui hubs.
To accomplish this, the plan is to configure all existing and future binderhub-ui based hubs to submit launch events into a centralized Google service and retained for at least a year there.
Tasks
The text was updated successfully, but these errors were encountered: