Notications to Contact groups instead to notication providers #308

Open
opened 2026-02-28 01:42:10 -05:00 by deekerman · 4 comments
Owner

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

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** -
Author
Owner

@Rush-er commented on GitHub (Oct 8, 2021):

+1 for API integration with the platform

@Rush-er commented on GitHub (Oct 8, 2021): +1 for API integration with the platform
Author
Owner

@deefdragon commented on GitHub (Oct 10, 2021):

Referencing #118 for the api functionality.

@deefdragon commented on GitHub (Oct 10, 2021): Referencing #118 for the api functionality.
Author
Owner

@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

@CommanderStorm commented on GitHub (May 24, 2023): @trapecija Can you please edit this issue to only include 1.? 2. is [tracked in different issues](https://github.com/louislam/uptime-kuma/issues/118) 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
Author
Owner

@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

@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
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#308
No description provided.