[GH-ISSUE #848] Integrations - ability to make them off by default for new checks #595

Closed
opened 2026-02-25 23:42:58 +03:00 by kerem · 1 comment
Owner

Originally created by @amcsi on GitHub (Jun 23, 2023).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/848

Whenever I add a new integration, every time I create a new check it associates all the existing integrations with it by default.

I would like to mark some integrations that I deem are for more important checks to be off by default when creating new checks.

I would like this, because I would like to set up a "severe" integration (for say, SMS) and to only have it associated with a select few very important checks. Otherwise, when creating a new unimportant check, it would associate the SMS notification by default, and I may forget to disassociate it with the unimportant check, resulting in SMS noise.

Originally created by @amcsi on GitHub (Jun 23, 2023). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/848 Whenever I add a new integration, every time I create a new check it associates all the existing integrations with it by default. I would like to mark some integrations that I deem are for more important checks to be off by default when creating new checks. I would like this, because I would like to set up a "severe" integration (for say, SMS) and to only have it associated with a select few very important checks. Otherwise, when creating a new unimportant check, it would associate the SMS notification by default, and I may forget to disassociate it with the unimportant check, resulting in SMS noise.
kerem closed this issue 2026-02-25 23:42:58 +03:00
Author
Owner

@cuu508 commented on GitHub (Jun 26, 2023):

How about moving the important checks and the important integrations in their own separate project?

The problem with every new configuration switch, and every new special mode is, although it solves a specific problem for one group of users, it makes the product more complex and harder to understand for everyone else.

<!-- gh-comment-id:1607423633 --> @cuu508 commented on GitHub (Jun 26, 2023): How about moving the important checks and the important integrations in their own separate project? The problem with every new configuration switch, and every new special mode is, although it solves a specific problem for one group of users, it makes the product more complex and harder to understand for everyone else.
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/healthchecks#595
No description provided.