Ability for Consul to serve traffic despite an optional Health Check failure

[teeto11]

Proposal Hello it will be nice to have a way to configure health checks for certain services as optional , so when this service fails, the app still works on the failure of just that particular service. Does something like this exist and i may have missed it ?

Use-cases For example if a health check for a service is marked as not healthy on consul, i want to be able to still serve traffic to the app because that service isn't a major dependency to cause a restart.

[teeto11]

Just like this issue but this should not stop consul from still serving the app

[pkazmierczak]

Hi @teeto11, you can set on_update field to ignore_warnings or ignore to instruct Nomad to treat the service as healthy regardless of its Consul status. Is that what you meant? let me know if this works for you.

[teeto11]

@pkazmierczak I actually tried this but consul still registered the check i applied it on as critical and the app failed to start, hence this feedback, except i am doing something wrong. i think the flag only works for warning health status

[pkazmierczak]

right, so ignore_warnings is a Nomad setting, it will only affect how Nomad will proceed with service deployment. If you don't want the check to register on Consul as critical, you can use a script check type or perhaps set high values for failures_before_critical or timeout fields? Or disable the check altogether?

[teeto11]

Thanks @pkazmierczak , where can i find the check type script

[pkazmierczak]

We have some examples in our documentation and there's more examples on Consul website