Skip to content
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

Open
victorb opened this issue Apr 11, 2019 · 2 comments
Open

Metrics page #6

victorb opened this issue Apr 11, 2019 · 2 comments

Comments

@victorb
Copy link
Member

victorb commented Apr 11, 2019

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)

@kbariotis
Copy link

kbariotis commented May 5, 2019

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 saw that you are using Prometheus. Are these metrics stored there?
  • Should we setup a basic website that would fetch them from Prometheus?
  • I saw you have setup a website on the gh-pages. I don't see how this is being built so I guess you are managing it manually. Have you thought about moving to a framework? Is this a good time to talk about it?

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

@victorb
Copy link
Member Author

victorb commented May 6, 2019

Hi @victorb, this is a great project, thank you for taking the time to do it.

Thanks, makes me very happy to hear! :)

I saw that you are using Prometheus. Are these metrics stored there?

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.

Should we setup a basic website that would fetch them from Prometheus?

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

I saw you have setup a website on the gh-pages. I don't see how this is being built so I guess you are managing it manually. Have you thought about moving to a framework? Is this a good time to talk about it?

So the gh-pages you see here in open-services/open-registry is the documentation available over at https://docs.open-registry.dev. It's built with mkdocs already.

The configuration for the docs config is here: https://github.com/open-services/open-registry/blob/master/mkdocs.yml
And the actual documents are here: https://github.com/open-services/open-registry/tree/master/docs

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
towards showing the finance metrics there. Take a look and let me know what
you think: open-services/open-registry-website#1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants