summaryrefslogtreecommitdiffstats
path: root/wiki/src/blueprint/monitor_servers.mdwn
diff options
context:
space:
mode:
authorbertagaz <bertagaz@ptitcanardnoir.org>2015-06-23 21:07:10 +0200
committerbertagaz <bertagaz@ptitcanardnoir.org>2015-06-23 21:07:10 +0200
commitab1d216a2c5a218f02e0dae3ccbf89a8123c4e6f (patch)
tree5aab04a9dd79bdbf81333d27f3150c28678b9a8c /wiki/src/blueprint/monitor_servers.mdwn
parent9184b41b0c53a23c1729371f9d77a7d677997ed1 (diff)
blueprint/monitoring_servers: precisions.
Diffstat (limited to 'wiki/src/blueprint/monitor_servers.mdwn')
-rw-r--r--wiki/src/blueprint/monitor_servers.mdwn10
1 files changed, 6 insertions, 4 deletions
diff --git a/wiki/src/blueprint/monitor_servers.mdwn b/wiki/src/blueprint/monitor_servers.mdwn
index 37def72..d93a482 100644
--- a/wiki/src/blueprint/monitor_servers.mdwn
+++ b/wiki/src/blueprint/monitor_servers.mdwn
@@ -172,10 +172,12 @@ anything needed for basic usage (plugins, checks, etc.).
Here, we have two major desires. One is the ability for humans to
easily review the monitoring system's configuration, or changes
-proposed to it. The other is the ability to include monitoring aspects
-within the description of the services we run, in a self-contained
-way. Note that a system that satisfies the second requirement has
-great chances to also mostly satisfy the first one as well.
+proposed to it, so that contributions are made easier. The other is
+the ability to include monitoring aspects within the description of
+the services we run, in a self-contained way, so that describing them
+in puppet is easier. Note that a system that satisfies the second
+requirement has great chances to also mostly satisfy the first one as
+well.
The chosen monitoring system: