NRPE can be related as well, this is true. Maybe I misstated it a bit, I'll blame the jetlag ;)
Put it this way, if a user is implementing a to-be promulgated charm, as a minimum (for those who expose such a thing) why not ensure the port is up and listening, not just the host ping, for those who have capability already in Nagios for a more in depth NPRE make sure its available for those who want to monitor it, procrunning as well for alarms. My point being, I guess, is considering how much Juju tries to do at an application level for sys admins, why shouldn't monitors.yaml be required OOTB? Don't get me wrong this was just a brief convo we had and I'm sure there are plenty of reasons against it, but monitoring, which is more than just "is my box alive" type monitoring, would seem pretty important and having people tack stuff on manually to a NPRE setup seems to get away from the Juju ethos somewhat. Tom -------------- Director Meteorite.bi - Saiku Analytics Founder Tel: +44(0)5603641316 (Thanks to the Saiku community we reached our Kickstart <http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/> goal, but you can always help by sponsoring the project <http://www.meteorite.bi/products/saiku/sponsorship>) On 16 May 2016 at 14:52, Charles Butler <charles.but...@canonical.com> wrote: > I love it when you support my arguments and I'm too dense to pick up on it > Tim :D > >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
