Healthchecks new updated widget
Churator opened this issue · comments
Description
I'm getting this error when I remove the UUID from the widget of Healthchecks
API Error: Invalid data
URL: https://healthchecks.io/api/v2/checks/
Config:
- HealthChecks:
href: https://healthchecks.io/
icon: healthchecks
widget:
type: healthchecks
url: https://healthchecks.io/
key:
Fully response:
{"checks": [{"name": "LanSVC", "slug": "lansvc", "tags": "", "desc": "", "grace": 60, "n_pings": 27636, "status": "up", "started": false, "last_ping": "2024-01-21T13:56:01+00:00", "next_ping": "2024-01-21T13:58:00+00:00", "manual_resume": false, "methods": "", "subject": "", "subject_fail": "", "start_kw": "", "success_kw": "", "failure_kw": "", "filter_subject": false, "filter_body": false, "unique_key": "", "schedule": "*/2 * * * *", "tz": "Asia/Jerusalem"}, {"name": "Uptime Kuma", "slug": "uptime-kuma", "tags": "", "desc": "", "grace": 120, "n_pings": 492274, "status": "up", "started": false, "last_ping": "2024-01-21T13:56:04+00:00", "next_ping": "2024-01-21T13:58:04+00:00", "manual_resume": false, "methods": "", "subject": "", "subject_fail": "", "start_kw": "", "success_kw": "", "failure_kw": "", "filter_subject": false, "filter_body": false, "unique_key": "", "timeout": 120}]}
Steps to reproduce
remove UUID from existing widget to see all checks statistics
homepage version
0.8.4
Installation method
Docker
Configuration
No response
Container Logs
No response
Browser Logs
No response
Troubleshooting
add UUID and I see the specific one
Other
No response
Before submitting, I have made sure to
- Check the documentation
- Follow the troubleshooting guide (please include output above if applicable).
- Search existing issues and discussions.
Make sure you followed all the steps of the troubleshooting guide. Using the data you supplied (thanks) works fine:
Similarly, using real data works fine:
- Healthchecks:
description: healthchecks
icon: healthchecks.png
href: https://healthchecks.io
widget:
url: https://healthchecks.io
type: healthchecks
key: **
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.