mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Notications to Contact groups instead to notication providers #308
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#308
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 @trapecija on GitHub (Oct 3, 2021).
Is it a duplicate question?
No
Is your feature request related to a problem? Please describe.
Just want to suggest some interesting features
Describe the solution you'd like
Contact groups (feature from StatusCake)
You have 10 domains added on HTTP monitoring, but you want to assign this domains to different contact groups, for example:
5 domains -> domain_group_1 -> notifications to email1@example.com
5 domains -> domain_group_2 -> notifications to email2@example.com
Describe alternatives you've considered
Additional context
@Rush-er commented on GitHub (Oct 8, 2021):
+1 for API integration with the platform
@deefdragon commented on GitHub (Oct 10, 2021):
Referencing #118 for the api functionality.
@CommanderStorm commented on GitHub (May 24, 2023):
@trapecija Can you please edit this issue to only include 1.?
2. is tracked in different issues and 3. is implemented.
In addition, please have a look if https://github.com/louislam/uptime-kuma/pull/2693 solves the first problem (e.e. if this is one of the related duplicates)
having more than one thing per issue makes issue management unmanageble
@jordantrizz commented on GitHub (Apr 22, 2024):
Going a step further, creating a Contact Object would allow for defining specific details that can be used for a Notification Type. The fields would be as follows.
Name
Phone 1
Phone 2
Email 1
Email 2
There could be an option to create custom fields with data.
Then create a new object called Contact Groups, which holds multiple Contact objects and be attached to a Notification Service object.
https://github.com/louislam/uptime-kuma/issues/1850