There's also OpenStack's monasca-agent:
https://github.com/stackforge/monasca-agent
We could try to run it standalone (without Monasca API), add a plugin
for it that checks disk and sends notification straight to Fuel DB and
omits generating Forwarder requests. Or set up a fake API though both
ways seem a bit hackish.
I wasn't aware that we want email notifications too?
P.
On 11/21/2014 10:35 AM, Igor Kalnitsky wrote:
I heard about Monit a lot of good reviews, but unfortunately it looks
like Monit doesn't support plugins and doesn't provide API. It may be
a stumbling block if one day we decide to go deeper in monitoring
task.
On Fri, Nov 21, 2014 at 11:01 AM, Matthew Mosesohn
<mmoses...@mirantis.com> wrote:
I'm okay with Sensu or Monit, just as long as the results of
monitoring can be represented in a web UI and has a configurable
option for email alerting. Tight integration with Fuel Web is a
nice-to-have (via AMQP perhaps), but anything that can solve our
out-of-disk scenario is ideal. I did my best to tune our logging and
logs rotation, but monitoring is the most sensible approach.
-Matthew
On Fri, Nov 21, 2014 at 12:21 PM, Przemyslaw Kaminski
<pkamin...@mirantis.com> wrote:
BTW, there's also Monit
http://mmonit.com/monit/
(though it's in C) that looks quite nice. Some config examples:
http://omgitsmgp.com/2013/09/07/a-monit-primer/
P.
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 <tnapier...@mirantis.com>
wrote:
On 06 Nov 2014, at 12:20, Przemyslaw Kaminski <pkamin...@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
tnapier...@mirantis.com
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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
