[openstack-dev] [Fuel] fuel master monitoring

Przemyslaw Kaminski pkaminski at mirantis.com
Fri Nov 21 08:17:21 UTC 2014

I have nothing against using some 3rd party service. But I thought this 
was to be small -- disk monitoring only & notifying the user, not stats 
collecting. That's why I added the code to Fuel codebase. If you want 
external service you need to remember about such details as, say, 
duplicate settings (database credentials at least) and I thought this 
was an overkill for such simple functionality. Also, for a 3rd party 
service, notification injecting code still needs to be written as a 
plugin -- that's why I also don't think Ruby is a good idea :)

So in the end I don't know if we'll have that much less code with a 3rd 
party service. But if you want a statistics collector then maybe it's OK.

I found some Python services that might suit us:



On 11/20/2014 09:13 PM, Dmitriy Shulyak wrote:
> Guys, maybe we can use existing software, for example Sensu [1]?
> Maybe i am wrong, but i dont like the idea to start writing our 
> "small" monitoring applications..
> Also something well designed and extendable can be reused for 
> statistic collector
> 1. https://github.com/sensu
> On Wed, Nov 12, 2014 at 12:47 PM, Tomasz Napierala 
> <tnapierala at mirantis.com <mailto:tnapierala at mirantis.com>> wrote:
>     On 06 Nov 2014, at 12:20, Przemyslaw Kaminski
>     <pkaminski at mirantis.com <mailto:pkaminski at mirantis.com>> wrote:
>     > I didn't mean a robust monitoring system, just something
>     simpler. Notifications is a good idea for FuelWeb.
>     I’m all for that, but if we add it, we need to document ways to
>     clean up space.
>     We could also add some kind of simple job to remove rotated logs,
>     obsolete spanshots, etc., but this is out of scope for 6.0 I guess.
>     Regards,
>     --
>     Tomasz 'Zen' Napierala
>     Sr. OpenStack Engineer
>     tnapierala at mirantis.com <mailto:tnapierala at mirantis.com>
>     _______________________________________________
>     OpenStack-dev mailing list
>     OpenStack-dev at lists.openstack.org
>     <mailto:OpenStack-dev at lists.openstack.org>
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141121/1cc2b877/attachment.html>

More information about the OpenStack-dev mailing list