From fa575db15c8ac46e66c08fabd7cdaf905c27196b Mon Sep 17 00:00:00 2001 From: Matt Shean Date: Thu, 25 Feb 2016 21:12:13 -0800 Subject: [PATCH] Update documentation for CheckMonitor timeout --- website/source/docs/agent/checks.html.markdown | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/website/source/docs/agent/checks.html.markdown b/website/source/docs/agent/checks.html.markdown index b5cd2a7130..105cbf1af9 100644 --- a/website/source/docs/agent/checks.html.markdown +++ b/website/source/docs/agent/checks.html.markdown @@ -22,6 +22,9 @@ There are five different kinds of checks: generates some output. A script is paired with an invocation interval (e.g. every 30 seconds). This is similar to the Nagios plugin system. The output of a script check is limited to 4K. Output larger than this will be truncated. + By default, Script checks will be configured with a timeout equal to 30 seconds. + It is possible to configure a custom Script check timeout value by specifying the + `timeout` field in the check definition. * HTTP + Interval - These checks make an HTTP `GET` request every Interval (e.g. every 30 seconds) to the specified URL. The status of the service depends on the HTTP response code: @@ -83,7 +86,8 @@ A script check: "id": "mem-util", "name": "Memory utilization", "script": "/usr/local/bin/check_mem.py", - "interval": "10s" + "interval": "10s", + "timeout": "1s" } } ```