[Feature Request] Public status page, configurable #1979

Open
opened 2025-11-02 04:20:02 -06:00 by GiteaMirror · 10 comments
Owner

Originally created by @BNolet on GitHub (Jun 26, 2018).

Currently, I have to be admin to view stats about the server though I would like to be able to publish some stats publicly.

What I propose:

Public_Stat_Page

  • Open - Anybody can see the public stat page, regardless of whether the user is logged in or not
  • Logged in - Only logged in users can see the public stat page
  • Off - There is no public stat page

The stat page can have a section within app.ini where certain stats can be marked as true or false as to whether the admin wants this stat to be published on the public stat page

Feel free to add or comment below

Originally created by @BNolet on GitHub (Jun 26, 2018). Currently, I have to be admin to view stats about the server though I would like to be able to publish some stats publicly. What I propose: ### Public_Stat_Page * `Open` - Anybody can see the public stat page, regardless of whether the user is logged in or not * `Logged in` - Only logged in users can see the public stat page * `Off` - There is no public stat page The stat page can have a section within `app.ini` where certain stats can be marked as true or false as to whether the admin wants this stat to be published on the public stat page Feel free to add or comment below
GiteaMirror added the type/featuretype/proposal labels 2025-11-02 04:20:02 -06:00
Author
Owner

@techknowlogick commented on GitHub (Jun 27, 2018):

This is related to #2751. Personally I would prefer it to be published out to an external tool rather than baking this customization into Gitea itself. GitLab publishes their prometheus dashboards, but not everyone does.

@techknowlogick commented on GitHub (Jun 27, 2018): This is related to #2751. Personally I would prefer it to be published out to an external tool rather than baking this customization into Gitea itself. GitLab publishes their prometheus dashboards, but not everyone does.
Author
Owner

@BNolet commented on GitHub (Jun 27, 2018):

Hmm, I didn't know that there was a "standard" for this already. That being said, I'd like to be able to decide which metrics to expose to the endpoint using the settings(app.ini) file

@BNolet commented on GitHub (Jun 27, 2018): Hmm, I didn't know that there was a "standard" for this already. That being said, I'd like to be able to decide which metrics to expose to the endpoint using the settings(app.ini) file
Author
Owner

@kolaente commented on GitHub (Jan 8, 2019):

You could also create a custom grafana dashboard based on the metrics from gitea and only show what you want publicly while keeping the metrcis endpoint private.

@kolaente commented on GitHub (Jan 8, 2019): You could also create a custom grafana dashboard based on the metrics from gitea and only show what you want publicly while keeping the metrcis endpoint private.
Author
Owner

@adelowo commented on GitHub (Jan 26, 2019):

Can we close this issue since we now have Prometheus support ? Or is a status page actually in the pipeline?

@adelowo commented on GitHub (Jan 26, 2019): Can we close this issue since we now have Prometheus support ? Or is a status page actually in the pipeline?
Author
Owner

@kolaente commented on GitHub (Jan 26, 2019):

@adelowo With Prometheus you can set that up pretty easily. You could stick a Grafana to it and then make that publicly.

We could publish an example config for that though.

@kolaente commented on GitHub (Jan 26, 2019): @adelowo With Prometheus you can set that up pretty easily. You could stick a Grafana to it and then make that publicly. We could publish an example config for that though.
Author
Owner

@adelowo commented on GitHub (Jan 26, 2019):

Sure, Prometheus already gets us halfway. I don’t know what next weekend is going to look like for me as per schedule but if free enough, I’d put up a grafana dashboard.

I thought this feature request was a status page like a minimal https://www.statuspage.io instead .

@adelowo commented on GitHub (Jan 26, 2019): Sure, Prometheus already gets us halfway. I don’t know what next weekend is going to look like for me as per schedule but if free enough, I’d put up a grafana dashboard. > I thought this feature request was a status page like a minimal https://www.statuspage.io instead .
Author
Owner

@BNolet commented on GitHub (Jan 27, 2019):

Something like that but also with some stuff like average RAM usage, users signed up, number of repos, as well as uptime percentage, as well as some announcement page? But that could easily just be a repo that one admin makes and updates as seen fit

@BNolet commented on GitHub (Jan 27, 2019): Something like that but also with some stuff like average RAM usage, users signed up, number of repos, as well as uptime percentage, as well as some announcement page? But that could easily just be a repo that one admin makes and updates as seen fit
Author
Owner

@kolaente commented on GitHub (Jan 27, 2019):

@BNolet AFAIK you can do all of that (maybe without the announcement page) with a Grafana dashboard and prometheus.

@kolaente commented on GitHub (Jan 27, 2019): @BNolet AFAIK you can do all of that (maybe without the announcement page) with a Grafana dashboard and prometheus.
Author
Owner

@juanpablo-santos commented on GitHub (Apr 22, 2020):

Having an example grafana dashboard would be really nice, as prometheus metrics are already there O:-)

@juanpablo-santos commented on GitHub (Apr 22, 2020): Having an example grafana dashboard would be really nice, as prometheus metrics are already there O:-)
Author
Owner

@juanpablo-santos commented on GitHub (Jun 24, 2021):

seems someone has already pulled a sample grafana dashboard for gitea.

@juanpablo-santos commented on GitHub (Jun 24, 2021): seems someone has already pulled a [sample grafana dashboard for gitea](https://grafana.com/grafana/dashboards/13192).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1979