diff options
| author | varac <varacanero@zeromail.org> | 2014-11-18 14:00:55 +0100 |
|---|---|---|
| committer | varac <varacanero@zeromail.org> | 2014-11-18 14:00:55 +0100 |
| commit | 4b963bc91b0d1d33c0a5d7d185b786b4bcf4b4ac (patch) | |
| tree | 154b5d8f83ef0b122afe7bc806fedc01bb12bd18 | |
| parent | 5a967f908c64c74df2b66d20aba4234f592cbf5b (diff) | |
updated docs/platform/tests.md and included it into navigation
| -rw-r--r-- | docs/platform/tests.md | 6 | ||||
| -rw-r--r-- | menu.txt | 1 |
2 files changed, 2 insertions, 5 deletions
diff --git a/docs/platform/tests.md b/docs/platform/tests.md index 40c049a..71b47c1 100644 --- a/docs/platform/tests.md +++ b/docs/platform/tests.md @@ -20,11 +20,7 @@ In order to set up a monitoring node, you simply add a `monitor` service tag to 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 (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 write your own `leap test` tests and/or nagios tests +You can log into the monitoring web interface via [https://MONITORNODE/nagios3/](https://MONITORNODE/nagios3/). The username is `nagiosadmin` and the password is found in the secrets.json file in your provider directory. Log Monitoring -------------- @@ -22,6 +22,7 @@ docs config commands under-the-hood + tests known-issues faq troubleshooting |