Open Stack

We have been using influxdata's influxdb, telegraf, and kapacitor with
grafana for visualization [1]. You do not have to install telegraf in the
VM to gather data on them however will need telegraf on the compute node
and more than likely have to use some coding of telegraf to get what you
want out.

There is also a tool called netdata [2] which may suffice for what you are
wanting to collect. Robert and Joe seem to have a sense of what you want
and may offer the best option.

[1] http://influxdata.com
[2] https://github.com/firehol/netdata

On Sun, Dec 11, 2016 at 7:33 PM, Đức Nguyễn Công <
nguyencongduc3112 at gmail.com> wrote:

> Using Collectd virt plugin is a good point to start, for more information,
> you can read this article https://community.rackspace.com/products/f/25/t/
> 6800
> Using Ceilometer with MongoDB for monitoring services will give heavy load
> because of too many api requests (tesed with Kilo and Liberty). We used
> Ceilometer only for alert perpose.
> In newer cycle, you shoud have a try MaaS or Ceilomer + Gnocchi + Aodh.
>
>
> 2016-11-21 15:17 GMT+07:00 Van Leeuwen, Robert <rovanleeuwen at ebay.com>:
>
>> >>I know that ceilometer may be an option, but I believe operators use
>> all kind of tools for their own ressource usage monitoring. So what do you
>> people use?
>>
>> >>
>> >>(For this use case, we're looking for something that can be used
>> without installing an agent in the VM, which makes it impossible to get a
>> VM's load metric. I would be satisfied with cpu/memory/network/io metrics
>> though.)
>>
>>
>>
>>
>>
>> Although I’d like to re-evaluate ceilometer at some point we currently
>> use something very simple with the infra we already had in place.
>>
>>
>>
>> We use the collectd libvirt plugin and push the metrics to graphite.
>>
>> https://collectd.org/wiki/index.php/Plugin:virt
>>
>>
>>
>> If you use the following format you get the instance uuid in the metric
>> name:
>>
>> HostnameFormat "hostname uuid"
>>
>>
>>
>> The output of those graphite keys is not exactly what we want (IIRC you
>> get hostname_uuid instead of hostname.uuid)
>>
>> We rewrite it a bit with carbon-(c-)relay daemon to something more usable
>> so you get:
>>
>> computenode.libvirt.UUID.metrics
>>
>>
>>
>> We made a grafana dashboard where you can select the uuid and get the
>> stats of the instance.
>>
>>
>>
>> Pros:
>>
>> * Simple, just needs collectd on compute nodes
>>
>> * Graphite scales (with the proper setup)
>>
>>
>>
>> Cons:
>>
>> * No tenant-id in the metric name  (I guess with some scripting you can
>> make a mapping-tree in graphite)
>>
>> * No metrics in Horizon. (We still have to make some time to integrate
>> these metrics into horizon but that should be doable.)
>>
>> * Just instance metrics nothing else
>>
>>
>>
>> Cheers,
>>
>> Robert van Leeuwen
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>
>
> --
> Best Regards!
>
> Duc, Nguyen Cong
> Skype: ducncvn at hotmail.com
> Phone: (+84)948309446 <+84%2094%20830%2094%2046>
> Site: http://ducnc.github.io/
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20161211/43773cb0/attachment.html>