summaryrefslogtreecommitdiffstats
path: root/wiki/src/blueprint/monitor_servers.mdwn
diff options
context:
space:
mode:
authorbertagaz <bertagaz@ptitcanardnoir.org>2015-06-23 21:27:48 +0200
committerbertagaz <bertagaz@ptitcanardnoir.org>2015-06-23 21:27:48 +0200
commitd8a89377edd260a335179bd27109a314e6dcbbd2 (patch)
tree02a9046c28930c42555542e4dd81cd64cbf0499a /wiki/src/blueprint/monitor_servers.mdwn
parentab1d216a2c5a218f02e0dae3ccbf89a8123c4e6f (diff)
blueprint/monitor_servers: precision.
Diffstat (limited to 'wiki/src/blueprint/monitor_servers.mdwn')
-rw-r--r--wiki/src/blueprint/monitor_servers.mdwn3
1 files changed, 2 insertions, 1 deletions
diff --git a/wiki/src/blueprint/monitor_servers.mdwn b/wiki/src/blueprint/monitor_servers.mdwn
index d93a482..5fedbdb 100644
--- a/wiki/src/blueprint/monitor_servers.mdwn
+++ b/wiki/src/blueprint/monitor_servers.mdwn
@@ -219,7 +219,8 @@ scale up to 50 hosts.
monitoring system MUST allow using a configured SOCKS proxy for
specific checks (worst case, for _all_ checks, but it prevents us
from). Wrapping checks with `torsocks` might be an acceptable
- option, depending on how involved and hackish this would be.
+ option, depending on how involved and hackish this would be. Ability
+ to retry and not notify on first error is interesting here.
## Hosting of the monitoring machine