Promulgated charms (production readiness)

Marco Ceppi marco.ceppi at canonical.com
Mon May 16 20:10:18 UTC 2016


I think a layer:nrpe isn't the right choice, but a layer:monitoring might
be. Esp with the layer/interface/subordinate model now, it seems that we
could actualize an abstract means to declare what to monitor and have
nrpe/zabbix-agent/promethous translate that.

Marco

On Mon, May 16, 2016 at 11:19 AM Cory Johns <cory.johns at canonical.com>
wrote:

> I think this is a strong argument for creating an interface:nrpe layer to
> make supporting this as easy as possible.  There was also discussion a long
> time ago about creating a translation layer of sorts for supporting
> multiple different monitoring solutions (like in the Puppet example).  I
> think with layers and layer APIs that's now more possible than ever.
>
> Once we have a simplified interface, I do think that the review process
> should strongly recommend that monitoring support be included, though I
> don't think we'll be able to make it a hard requirement.
>
> On Mon, May 16, 2016 at 10:06 AM, Tom Barber <tom at analytical-labs.com>
> wrote:
>
>> 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.butler at 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 at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20160516/3ebe6097/attachment.html>


More information about the Juju mailing list