mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Notification Webhook different on up and down cases #2901
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#2901
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @clement-igonet on GitHub (Dec 10, 2023).
⚠️ Please verify that this feature request has NOT been suggested before.
Already covered in other notification types, but not for webhook type:
🏷️ Feature Request Type
New Notification
🔖 Feature description
When triggering a notification by webhook, I'd like the ability to send different POST request on
upcase anddowncase.For instance:
upcase: Requesthttps://my_alerting_app/webhook/1/issueswith{"issue_key":"NOTIF-1234"}BODYdowncase: Requesthttps://my_alerting_app/webhook/1/issues/NOTIF-1234/closewith empty BODYHow may I set it up ?
✔️ Solution
Ability to select if the defined webhook is just for
upcase,downcase, or the both.❓ Alternatives
Create a dedicated notification specific for DevLake application.
Specs to generate a downtime INCIDENT by webhook: https://devlake.apache.org/docs/v0.20/Plugins/webhook
📝 Additional Context
@CommanderStorm commented on GitHub (Dec 10, 2023):
I don't see why this is not a duplicate of #508.
As far as I understand said issue, this covers all notification types.
=> closing as a duplicate