In order to monitor anything in your juju environment for working PING and SSH, just relate the services to this service. juju deploy nagios central-monitor juju deploy mysql big-db juju deploy statusnet microblog juju add-reation big-db microblog juju add-relation big-db central-monitor juju add-relation mocroblog central-monitor This should result in your Nagios monitoring all of the service units. monitors interface ================== The monitors interface expects three fields: * monitors - YAML matching the monitors yaml spec. See example.monitors.yaml for more information. * target-id - Assign any monitors to this target host definition. * target-address - Optional, specifies the host of the target to monitor. This must be specified by at least one unit so that the intended target-id will be monitorable. nrpe ==== There is an NRPE subordinate charm which must be used for any local monitors. See the 'nrpe' charm's README for information on how to make use of it.
|2012/08/07 Mark Mims merging lp:~clint-fewbar/charms/precise/nagios/add-monitors-2 (revno 8)|
|2012/05/22 Clint Byrum Setting maintainer (revno 7)|
|2012/05/14 Clint Byrum fixed incorrect formatting for multi-unit hostnames (thanks "ihashacks!") (revno 6)|
|2012/05/14 Clint Byrum Critical refactors to bring charm up to policy compliance and put in a working state (revno 5)|
|2011/10/12 Clint Byrum -rename to juju -split revision into file -use private-address when possible (revno 4)|
|2011/08/09 Chuck Short Store passwd in /var/lib/ensemble (revno 3)|
|2011/08/09 Chuck Short Updates based on clint's feedback (revno 2)|