Feature : Endpoints dependecies

[MartTave]

Hello!

First of all, thanks for the great work. I recently deployed Gatus and it works like a charm while remaining extremely lightweight :).

Currently, the only way to implement conditional test runs is through test suites. However, the scope of suites seems geared toward sequential tests sharing a specific context, rather than simply skipping an endpoint if a dependency is down.

I’m proposing a new endpoint property named dependencies, which would take a list of endpoints identified by <group>_<name>.

This would introduce a new endpoint status (e.g., stale or skipped). This status would indicate that not all dependencies are healthy. We could add this to the frontend and include a description of the unhealthy dependencies. Something like this:

The main objective is to avoid alerting for multiple endpoints at the same time : if an entire server or core service is down, we would avoid running (and alerting on) all the secondary tests linked to it.

One consideration:

• Currently, there is no strict order for running tests. I don't think it is necessary to implement a specific execution order for this feature, but users should be aware that if a dependent test runs before the "main" one, it might not be marked as stale until the next cycle after the main test fails.

If there is interest in this functionality, I would be happy to (try) submit a PR!