-
Notifications
You must be signed in to change notification settings - Fork 1.1k
feat: add webhook setup instructions via webhook_description for UptimeKuma #5438
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
base: main
Are you sure you want to change the base?
Conversation
Adds webhook_description (steps + authenticated URL). Leaves webhook_template blank since Kuma’s preset JSON works out-of-the-box. No functional changes.
|
Skipped: This PR does not target one of your configured branches: ( |
|
@Aze331 is attempting to deploy a commit to the KeepHQ Team on Vercel. A member of the Team first needs to authorize it. |
|
No linked issues found. Please add the corresponding issues in the pull request description. |
|
Hey! thanks for opening this PR! We have some problem with the CI/CD. Going to handle it soon and let this PR in :) |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Hey @shahargl , thanks for fixing the problem, I realize now that I made a mistake in ee225e7 The file was not generated due to my ignorance, Saw that I should execute Should I fix it in this PR or create a new one? |
📑 Description
This PR updates the
UptimekumaProviderwith awebhook_descriptionto guide users through configuring Uptime Kuma to send alerts to Keep.The
webhook_templateremains an empty string, because Uptime Kuma’s preset JSON works out-of-the-box with Keep’s webhook endpoint. There are no functional or behavioral changes to the provider.✅ Checks
ℹ Additional Information
STATUS_MAPbehavior.{keep_webhook_api_url_with_auth}placeholder is consistent with other providers (e.g., Pingdom) and is resolved by Keep at runtime.