Global integrations about healthchecks HOT 3 CLOSED

How many projects, and how many integrations per project are you working with?

from healthchecks.

How many projects, and how many integrations per project are you working with?

Currently evaluating it in my home lab, which uses 3 projects (home, a dedicated server, offsite backup) with 2 integrations each (email + telegram). However, in my enterprise environment if implemented that would be a few dozen of projects with 2-3 integrations each. Treating projects as physical locations offers a nice compartmentalization for the NOC view and brings a nice feature: if an internet connection is down for the site I will see multiple checks failing but all of them will be isolated to a single project. That way I know it's most likely not that the server room burned down (hopefully ;)) but probably the whole location lost internet access.

A sensible scenario with shared integration would be to have:

• a global downtime notification set-up for e.g. Slack for all sites [shared]
• an email notification for all locations [shared]
• an email notification to on-site person [per-project]

Now, when the responsibility changes or some infra change is happening I don't need to go to every single project and change the integration - I can go to the parent project/global integrations and simply change it in one place.

from healthchecks.

There's one existing feature that may perhaps work for your described use case: in the Account Settings > Email Reports you can enable ongoing hourly or daily email reminders when any checks are down. Unlike the integrations you set up in projects, these reminders are account-wide – you will get notified about checks in any and all projects you have access to. These reminders would arrive with a delay though – after a check goes down, you would get a "x checks are still down" reminder only an hour later.

If all projects have the same or almost the same 2-3 integrations, you could also put the checks in a single project, and compartmentalize them using tags.

Regarding the enterprise environment, are you considering implementing Healthchecks there? I'd be hesitant to add any new features and add complexity, unless there is a concrete and clear need from multiple users. And even then it's often ultimately a "no" – adding a feature that helps 1% of users but makes the service worse (harder to use due to UI clutter, bugs caused by the extra complexity, other potential features blocked by design decisions, ...) for 99% users, it's probably not worth it.

from healthchecks.