Open Stack

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 <pkaminski at 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 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/20141126/08bdb41e/attachment-0001.html>