[GH-ISSUE #124] Automatically assign checks to integrations #82

New issue

Closed

opened 2026-02-25 23:41:06 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 23:41:06 +03:00

Owner

Originally created by @bellini666 on GitHub (May 22, 2017).
Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/124

After you create an integration (email/pushover/telegram/etc) it will not assign new checks automatically to it and you have to do that manually.

That is a huge problem when you have lots of checks and lots of them are created every time. For example, in the company that I work we use healthchecks for some services that we deploy. We usually create ~10 new checks per week using the api (i.e. it is not created manually). That means that from time to time I have to go to the integrations page and manually assign the missings checks to all the integrations that I have there.

I understand that there are some people that probably wouldn't like the "auto async" thing so my suggestion is to make that configurable for each integration: Add a checkbutton there to verify if "New checks should be automatically assigned".

Originally created by @bellini666 on GitHub (May 22, 2017). Original GitHub issue: https://github.com/healthchecks/healthchecks/issues/124 After you create an integration (email/pushover/telegram/etc) it will not assign new checks automatically to it and you have to do that manually. That is a huge problem when you have lots of checks and lots of them are created every time. For example, in the company that I work we use healthchecks for some services that we deploy. We usually create ~10 new checks per week using the api (i.e. it is not created manually). That means that from time to time I have to go to the integrations page and manually assign the missings checks to all the integrations that I have there. I understand that there are some people that probably wouldn't like the "auto async" thing so my suggestion is to make that configurable for each integration: Add a checkbutton there to verify if "New checks should be automatically assigned".

kerem closed this issue

2026-02-25 23:41:07 +03:00

kerem commented

2026-02-25 23:41:07 +03:00

Author

Owner

@cuu508 commented on GitHub (May 22, 2017):

Hi Thiago,

one of the parameters for the "Create a check" API call is "channels". If you set it to "*", the check will be assigned to all existing channels. By setting this field, you can match the UI behavior: when a check is added from UI, it is assigned to all existing checks.

Would the "channels": "*" help your use case?

@cuu508 commented on GitHub (May 22, 2017): Hi Thiago, one of the parameters for the "Create a check" API call is "channels". If you set it to "*", the check will be assigned to all existing channels. By setting this field, you can match the UI behavior: when a check is added from UI, it is assigned to all existing checks. Would the `"channels": "*" ` help your use case?

kerem commented

2026-02-25 23:41:07 +03:00

Author

Owner

@bellini666 commented on GitHub (May 22, 2017):

@cuu508 oh, I didn't know about that channels. Yes it worked great! Marking this as closed, thank you!

@bellini666 commented on GitHub (May 22, 2017): @cuu508 oh, I didn't know about that `channels`. Yes it worked great! Marking this as closed, thank you!

kerem referenced this issue

2026-02-25 23:44:02 +03:00

[PR #85] [MERGED] adds a unique parameter to the check creation API #885