Related Problem or Business Case

There are currently 3 health endpoints, one for the application (getFrankHealth), a more finegrained one for a configuration (getConfigurationHealth) and a specific one for each adapter (getAdapterHealth).

When an adapter is stopped, the configuration and adapter endpoints will return an 503 error. The application endpoint is unaffected by this, however when an adapter is in state ERROR, it will also return a 503.

Describe the Feature

It would be nice if you could add a query parameter to the application getFrankHealth endpoint, so when a configuration error occurs it does not return a 503 but 200 OK.

This way people can still use the endpoint to validate if the application starts up, even though the configurations have not.

Collaboration with External Companies

No, community resolution only

Anything else?

It looks like the endpoint has already been implemented correclty, to only look at configuration exceptions.