From e872587e195a94f41b32bff356548750f84de8c3 Mon Sep 17 00:00:00 2001 From: Ryan Uber Date: Fri, 5 Jun 2015 17:15:57 -0700 Subject: [PATCH] website: document TTL check persistence --- website/source/docs/agent/checks.html.markdown | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/website/source/docs/agent/checks.html.markdown b/website/source/docs/agent/checks.html.markdown index 324661b249..d9b0c0f17b 100644 --- a/website/source/docs/agent/checks.html.markdown +++ b/website/source/docs/agent/checks.html.markdown @@ -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, 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 - 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