<div dir="ltr">Is it possible to send http requests from monit, e.g for creating notifications?<div>I scanned through the docs and found only alerts for sending mail,</div><div>also where token (username/pass) for monit will be stored?</div><div><br></div><div>Or maybe there is another plan? without any api interaction</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Nov 27, 2014 at 9:39 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">
This I didn't know. It's true in fact, I checked the manifests.
Though monit is not deployed yet because of lack of packages in Fuel
ISO. Anyways, I think the argument about using yet another
monitoring service is now rendered invalid.<br>
<br>
So +1 for monit? :)<span class="HOEnZb"><font color="#888888"><br>
<br>
P.</font></span><div><div class="h5"><br>
<br>
<div>On 11/26/2014 05:55 PM, Sergii
Golovatiuk wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Monit is easy and is used to control states of
Compute nodes. We can adopt it for master node. <br>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div>
<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 Wed, Nov 26, 2014 at 4:46 PM,
Stanislaw Bogatkin <span dir="ltr"><<a href="mailto:sbogatkin@mirantis.com" target="_blank">sbogatkin@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 dir="ltr">As for me - zabbix is overkill for one node.
Zabbix Server + Agent + Frontend + DB + HTTP server, and
all of it for one node? Why not use something that was
developed for monitoring one node, doesn't have many deps
and work out of the box? Not necessarily Monit, but
something similar.<br>
</div>
<div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Nov 26, 2014 at 6:22
PM, 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">We
want to monitor Fuel master node while Zabbix is
only on slave nodes and not on master. The
monitoring service is supposed to be installed on
Fuel master host (not inside a Docker container)
and provide basic info about free disk space, etc.<span><font color="#888888"><br>
<br>
P.</font></span>
<div>
<div><br>
<br>
On 11/26/2014 02:58 PM, Jay Pipes wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 11/26/2014 08:18 AM, Fox, Kevin M wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So then in the end, there will be 3
monitoring systems to learn,<br>
configure, and debug? Monasca for cloud
users, zabbix for most of the<br>
physical systems, and sensu or monit "to
be small"?<br>
<br>
Seems very complicated.<br>
<br>
If not just monasca, why not the zabbix
thats already being deployed?<br>
</blockquote>
<br>
Yes, I had the same thoughts... why not just
use zabbix since it's used already?<br>
<br>
Best,<br>
-jay<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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>
</blockquote>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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>
<br>
<fieldset></fieldset>
<br>
<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>
</blockquote>
<br>
</div></div></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>