luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

website: document TTL check persistence

This commit is contained in:
Ryan Uber 2015-06-05 17:15:57 -07:00
parent bd448d27fe
commit cf21fb1d0c
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
website/source/docs/agent/checks.html.markdown
View File

@ -37,7 +37,10 @@ There are three different kinds of checks:
set to the failed state. This mechanism, conceptually similar to a dead man's switch, set to the failed state. This mechanism, conceptually similar to a dead man's switch,
relies on the application to directly report its health. For example, a healthy app relies on the application to directly report its health. For example, a healthy app
can periodically `PUT` a status update to the HTTP endpoint; if the app fails, the TTL will can periodically `PUT` a status update to the HTTP endpoint; if the app fails, the TTL will
expire and the health check enters a critical state. expire and the health check enters a critical state. TTL checks also persist
their last known status to disk. This allows the Consul agent to restore the
last known status of the check across restarts. Persisted check status is
valid through the end of the TTL from the time of the last check.
## Check Definition ## Check Definition