From cef8305bd0faf4fa3530228e5039a1e06604c9d0 Mon Sep 17 00:00:00 2001 From: Ryan Breen Date: Thu, 29 Jan 2015 17:10:15 -0500 Subject: [PATCH] Make it clear that checks persist with the node, period, not just across runs of the agent but across reboots as well. --- website/source/docs/agent/checks.html.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/agent/checks.html.markdown b/website/source/docs/agent/checks.html.markdown index c3bf9449c6..f87702f031 100644 --- a/website/source/docs/agent/checks.html.markdown +++ b/website/source/docs/agent/checks.html.markdown @@ -13,7 +13,7 @@ checks. A health check is considered to be application-level if it is associated service. If not associated with a service, the check monitors the health of the entire node. A check is defined in a configuration file or added at runtime over the HTTP interface. Checks -created via the HTTP interface persist across runs of the Consul agent on that node. +created via the HTTP interface persist with that node. There are three different kinds of checks: