I mean with monit you can execute arbitrary scripts so use curl? Or save
them directly to DB?
http://omgitsmgp.com/2013/09/07/a-monit-primer/
I guess some data has to be stored in a configuration file (either DB
credentials or Nailgun API URL at least, if we were to create
notifications via the API). I proposed a hand-crafted solution
https://review.openstack.org/#/c/135314/
that lives in fuel-web code and uses settings.yaml so no config file is
necessary. It has the drawback though that the nailgun code lives inside
a Docker container so the monitoring data isn't reliable.
P.
On 11/27/2014 09:53 AM, Dmitriy Shulyak wrote:
Is it possible to send http requests from monit, e.g for creating
notifications?
I scanned through the docs and found only alerts for sending mail,
also where token (username/pass) for monit will be stored?
Or maybe there is another plan? without any api interaction
On Thu, Nov 27, 2014 at 9:39 AM, Przemyslaw Kaminski
<pkamin...@mirantis.com <mailto:pkamin...@mirantis.com>> wrote:
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.
So +1 for monit? :)
P.
On 11/26/2014 05:55 PM, Sergii Golovatiuk wrote:
Monit is easy and is used to control states of Compute nodes. We
can adopt it for master node.
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
On Wed, Nov 26, 2014 at 4:46 PM, Stanislaw Bogatkin
<sbogat...@mirantis.com <mailto:sbogat...@mirantis.com>> wrote:
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.
On Wed, Nov 26, 2014 at 6:22 PM, Przemyslaw Kaminski
<pkamin...@mirantis.com <mailto:pkamin...@mirantis.com>> wrote:
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.
P.
On 11/26/2014 02:58 PM, Jay Pipes wrote:
On 11/26/2014 08:18 AM, Fox, Kevin M wrote:
So then in the end, there will be 3 monitoring
systems to learn,
configure, and debug? Monasca for cloud users,
zabbix for most of the
physical systems, and sensu or monit "to be small"?
Seems very complicated.
If not just monasca, why not the zabbix thats
already being deployed?
Yes, I had the same thoughts... why not just use
zabbix since it's used already?
Best,
-jay
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
<mailto:OpenStack-dev@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
