summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorvarac <varacanero@zeromail.org>2014-11-18 11:04:53 +0100
committervarac <varacanero@zeromail.org>2014-11-18 11:04:53 +0100
commit5a967f908c64c74df2b66d20aba4234f592cbf5b (patch)
tree63569aa5b65f0516605dc1aff6f63be73b813091
parent00a379b0479c1381c233e0db06eed454f3870fb2 (diff)
document log monitoring and -purging (Bug #6174)
-rw-r--r--docs/platform/tests.md18
1 files changed, 13 insertions, 5 deletions
diff --git a/docs/platform/tests.md b/docs/platform/tests.md
index eeefa0e..40c049a 100644
--- a/docs/platform/tests.md
+++ b/docs/platform/tests.md
@@ -16,13 +16,21 @@ Alternately, you can run test on all nodes (probably only useful if you have pin
## Monitoring
-If you have a node with the 'monitor' service, then this node will regularly poll every node to ask for the status of various health checks. These health checks include the checks run with `leap test`, plus many others.
+In order to set up a monitoring node, you simply add a `monitor` service tag to the node configuration file. It could be combined with any other service, but we propose that you add it to the webapp node, as this already is public accessible via HTTPS.
+After deploying, this node will regularly poll every node to ask for the status of various health checks. These health checks include the checks run with `leap test`, plus many others.
+We use [Nagios](http://www.nagios.org/) together with [Check MK agent](https://en.wikipedia.org/wiki/Check_MK) for running checks on remote hosts.
-You can log into the monitoring web interface via XXXX. The username and password are found in the secrets.json file in your provider directory.
+You can log into the monitoring web interface via (https://<MONITORNODE>/nagios3/). The username is `nagiosadmin` and the password is found in the secrets.json file in your provider directory.
TODO:
-* add how to set up monitoring. just need to add 'monitor' service? what is it compatible with?
-* add url
-* add username/password
* add how to write your own `leap test` tests and/or nagios tests
+
+Log Monitoring
+--------------
+
+At the moment, we use [check-mk-agent-logwatch](https://mathias-kettner.de/checkmk_check_logwatch.html) for searching logs for irregularities.
+Logs are parsed for patterns using a blacklist, and are stored in `/var/lib/check_mk/logwatch/<Nodename>`.
+
+In order to "acknoledge" a log warning, you need to log in to the monitoring server, and delete the corresponding file in `/var/lib/check_mk/logwatch/<Nodename>`. This should be done via the nagios webinterface in the future.
+