diff options
author | elijah <elijah@riseup.net> | 2016-08-29 22:55:41 -0700 |
---|---|---|
committer | elijah <elijah@riseup.net> | 2016-08-29 22:55:41 -0700 |
commit | 0a09a6e6f247729457d15480f8d2b9bb0b89ae5e (patch) | |
tree | aec1e88cb9d8a4942068fb46333d5719ed5af79f /doc/services/monitor.md | |
parent | 568688b5a7d17de26a275a2f6dde8bbd3054cdc6 (diff) |
Updated (very out of date) docs and README.md
Diffstat (limited to 'doc/services/monitor.md')
-rw-r--r-- | doc/services/monitor.md | 36 |
1 files changed, 0 insertions, 36 deletions
diff --git a/doc/services/monitor.md b/doc/services/monitor.md deleted file mode 100644 index 576b36a9..00000000 --- a/doc/services/monitor.md +++ /dev/null @@ -1,36 +0,0 @@ -@title = "monitor" -@summary = "Nagios monitoring and continuous testing." - -The `monitor` node provides a nagios control panel that will give you a view into the health and status of all the servers and all the services. It will also spam you with alerts if something goes down. - -Topology --------------------------------------- - -Currently, you can have zero or one `monitor` nodes defined. It is required that the monitor be on the webapp node. It was not designed to be run as a separate node service. - -Configuration ------------------------------------------------ - -* `nagios.environments`: By default, the monitor node will monitor all servers in all environments. You can optionally restrict the environments to the ones you specify. - -For example: - - { - "nagios": { - "environments": ["unstable", "production"] - } - } - -Access nagios web ------------------------------------------------ - -*Determine the nagios URL* - - $ leap ls --print domain.name,webapp.domain,ip_address monitor - > chameleon chameleon.bitmask.net, demo.bitmask.net, 199.119.112.10 - -In this case, you would open `https://demo.bitmask.net/cgi-bin/nagios3` in your browser (or alternately you could use 199.119.112.10 or chameleon.bitmask.net). - -*Determine the nagios password* - -The username for nagios is always `nagiosadmin`. The password is randomly generated and stored in `secrets.json` under the key `nagios_admin_password`. Note that the login is `nagiosadmin` without underscore, but the entry in secrets.json is with underscores. |