-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Where did the grafana dashboard go? #4374
Comments
Good catch. Said dashboard was not maintained/owned by us (maintainers). Possibly related: #3225 @proffalken you added this dashboard in louislam/uptime-kuma-wiki@e9a64ea |
@CommanderStorm / @nmcc1212 - ah, my mistake, I've not used Uptime Kuma for well over a year now, hadn't maintained the dashboard, and it had two reviews, both of which were single stars saying it was useless, so I literally deleted it this afternoon. I don't have a backup I'm afraid, and am unlikely to have the time to launch UptimeKuma in the near future to recreate it. Sorry, I didn't realise people were still using it :( |
Found the revision 2 on Wayback machine @proffalken If you don't mind, you could give this json file a open source license like MIT and your copyright info, so that other users can continue your work and republish it.😃 |
Good find @louislam - yes, happy to do that, is there a "contrib" dirnor similar in the repo I can add it to so it's not lingering in a git repo owned by me somewhere? |
https://github.com/louislam/uptime-kuma/tree/unofficial/grafana-dashboard I just created a new branch here, feel free to create a pull request to modify the license info. |
🛡️ Security Policy
📝 Describe your problem
The grafana dashboard referenced here https://github.com/louislam/uptime-kuma/wiki/Prometheus-Integration gives me a 404 error when going to the link https://grafana.com/grafana/dashboards/14847-uptime-kuma/
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
N/A
💻 Operating System and Arch
N/A
🌐 Browser
N/A
🐋 Docker Version
No response
🟩 NodeJS Version
No response
The text was updated successfully, but these errors were encountered: