<div dir="ltr"><div>Hi,<br><br></div><div>monasca looks overcomplicated for the purposes we need. Also it requires Kafka which is Java based transport protocol.<br></div><div>I am proposing Sensu. It's architecture is tiny and elegant. Also it uses rabbitmq as transport so we won't need to introduce new protocol.<br></div><div><br><br><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">--<br>
Best regards,<br>
Sergii Golovatiuk,<br>
Skype #golserge<br>
IRC #holser<br></div></div></div>
<br><div class="gmail_quote">On Mon, Nov 24, 2014 at 10:55 AM, Przemyslaw Kaminski <span dir="ltr"><<a href="mailto:pkaminski@mirantis.com" target="_blank">pkaminski@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
I proposed monasca-agent in a previous mail in this thread.<span class="HOEnZb"><font color="#888888"><br>
<br>
P.</font></span><div><div class="h5"><br>
<br>
<div>On 11/21/2014 04:48 PM, Fox, Kevin M
wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
How about this?<br>
<a href="https://wiki.openstack.org/wiki/Monasca" target="_blank">https://wiki.openstack.org/wiki/Monasca</a><br>
<br>
Kevin <strong>
<div><font face="Tahoma" color="#000000"> </font></div>
</strong>
<hr>
<font face="Tahoma"><b>From:</b> Dmitriy Shulyak<br>
<b>Sent:</b> Friday, November 21, 2014 12:57:45 AM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage
questions)<br>
<b>Subject:</b> Re: [openstack-dev] [Fuel] fuel master
monitoring<br>
</font><br>
<div>
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote"><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF">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.
</div>
</blockquote>
<div> </div>
<div>Yes, it will be much more complex than simple daemon
that creates notifications but our application is
operating in isolated containers, and most of the
resources cant be discovered from any particular
container. So if we will want to extend it, with another
task, like monitoring pool of dhcp addresses - we will
end up with some kindof server-agent architecture, and
this is a lot of work to do<br>
</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF">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 :)<br>
<br>
</div>
</blockquote>
<div>Afaik there is a way to write python plugins for
sensu, but if there is monitoring app in python, that
have friendly support for extensions, I am +1 for python</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF">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.<br>
<span><font color="#888888"><br>
</font></span></div>
</blockquote>
<div>I think that monitoring application is fits there,
and we kindof already introducing our whell for
collecting</div>
<div>statistic from openstack. I would like to know what
guys who was working on stats in 6.0 thinking about it.
So it is TBD</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><span class=""><pre>_______________________________________________
OpenStack-dev mailing list
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</span></blockquote>
<br>
</div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>