-
-
Notifications
You must be signed in to change notification settings - Fork 160
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
[API] Statistics API end point like those displayed on /stats #1080
Comments
I presume you know of For the others, I've added Let me know if this enough for your needs. |
Thanks! And yeah I'm aware of the tag cloud data, though I didn't find the total count (or maybe I missed it somewhere?) so as lazy as I am I just use Python to scrap the statistics page lol. I guess if we already have a count for the statistics page it shouldn't be too complicated to add another end point...? As for the total size, I didn't realized it's hard coded to GB so there is no need to rush, just when you have free time. |
The correct way to do this would be to use prometheus metrics, which are the standard for monitoring applications nowadays. That way then it can be pulled into grafana/any other system out there without worrying about supporting different custom apps. |
Yes, my idea is we have some general API end points so people can decide what to do with them, I have prometheus and homepage supports custom API so there is no need for LANraragi to do extra development about dashboard support. |
I'll be playing around with prometheus for a bit. |
Suggestion
For a homelab environment where poeple usually has a dashboard, maybe extend the current API end point to add something like total archives, tags etc. display on the https://yourinstance.com/stats? Maybe add them to the /info end point since it already have
total_pages_read
there.Additional Context
The dashboard I'm using now is https://github.com/gethomepage/homepage which support custom API so I can display the statics there. I have a Python script to grab the numbers from the /stats page the expose my homemade API but I felt it's not the most elegant way to do it lol.
The text was updated successfully, but these errors were encountered: