-
Notifications
You must be signed in to change notification settings - Fork 8
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
Metrics page #6
Comments
Hi @victorb, this is a great project, thank you for taking the time to do it. Haven't had the chance to setup this project locally so a couple of questions on this to see how I can help. How are you thinking about tackling this issue?
I could setup another page on the existing website, trying to fetch data from Prometheus and showing them in some nice metrics using a third-party metrics library. Thank you |
Thanks, makes me very happy to hear! :)
Yes, currently prometheus is used everywhere, even for the finances, the idea being that we can have one dashboard in Grafana that is public that gives a overview of everything from the finances, infrastructure or application-specific metrics.
I think we can use a Grafana Dashboard for the main view. What would be nice and is planned, is to fetch data from Prometheus and show is on the website. I was planning to include it in the first version of the website, but didn't have time. You can see the commented HTML where the metrics/finances are supposed to be here: https://github.com/open-services/open-registry-website/blob/master/index.html#L248-L345
So the The configuration for the docs config is here: https://github.com/open-services/open-registry/blob/master/mkdocs.yml The main website has a different repository: https://github.com/open-services/open-registry-website Regarding the landing page (https://open-registry.dev) it's currently very simple and hopefully we can keep it so. There is no framework and works without JS, which would be nice to keep it like that. Unless there is a sudden jump in complexity compared to now, I'd like to avoid any frameworks. If you feel up for it, I added a issue in the website repository about working |
Part of being a Open Service is having all the useful metrics also be public. Metrics we currently have is bunch of data about the JVM + metadata/tarball requests (cached vs non-cached)
The text was updated successfully, but these errors were encountered: