You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New checks are initially set to "critical" when registered in consul. It would be nice to have the ability to initially set them to "passing" for certain job types as noted in the consul docs: https://www.consul.io/docs/agent/checks.html.
The text was updated successfully, but these errors were encountered:
We've also noticed this with the Nomad Client HTTP Check as clients come online. This ends up triggering alarms based on the failed consul status. Would it be possible to 1) have nomad wait to register itself once healthy or 2) initially set itself as passing (as described above)?
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
New checks are initially set to "critical" when registered in consul. It would be nice to have the ability to initially set them to "passing" for certain job types as noted in the consul docs: https://www.consul.io/docs/agent/checks.html.
The text was updated successfully, but these errors were encountered: