Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-02-04 Thread Foley, Emma L

> nice, do you have resource to look at this? or maybe something to add to
> Gnocchi's potential backlog. existing plugin still seems useful to those who
> want to use custom/proprietary storage.

I should have resources for this. 

Question is where it should live. 
Since gnocchi is designed to be standalone, it seem like that's a potential 
home for it. 
If not, it also fits in with the existing plugin.

Regards,
Emma

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-02-04 Thread Julien Danjou
On Thu, Feb 04 2016, Foley, Emma L wrote:

> Question is where it should live. 
> Since gnocchi is designed to be standalone, it seem like that's a potential 
> home for it. 
> If not, it also fits in with the existing plugin.

It it's a collectd plugin that talk statsd protocol, I'd say it should
live near collectd, no?

-- 
Julien Danjou
;; Free Software hacker
;; https://julien.danjou.info


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-02-04 Thread Foley, Emma L
> > So, metrics are grouped by the type of resource they use, and each metric
> has to be listed.
> > Grouping isn't a problem, but creating an exhaustive list might be, since
> there are 100+ plugins [1] in collectd which can provide statistics, although
> not all of these are useful, and some require extensive configuration. The
> plugins each provide multiple metrics, and each metric can be duplicated for
> a number of instances, examples: [2].
> >
> > Collectd data is minimal: timestamp and volume, so there's little room to
> find interesting meta data.
> > It would be nice to see this support integrated, but it might be very
> > tedious to list all the metric names and group by resource type without any
> form of Do the resource definitions support wildcards? Collectd can provide
> A LOT of metrics.
> >
> > Regards,
> > Emma
> >
> > [1] https://collectd.org/wiki/index.php/Table_of_Plugins
> > [2] https://collectd.org/wiki/index.php/Naming_schema
> 
> gnocchi is strongly typed when compared to classical ceilometer db where
> you can dump anything and everything. we don't support wildcards as is but i
> believe it's something we can aim to support?

> Mehdi is currently in process of implementing dynamic resources which
> would give more flexiblity on what type of data we can store in Gnocchi.
> i believe from ceilometer pov, we can add support to allow wildcard support
> in regards to adding new metrics.
> 

It makes sense to support wildcards, if someone is introducing a huge source of 
 meters.
I can help with that, if needed.

Regards,
Emma

--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-02-04 Thread Foley, Emma L

> On Thu, Feb 04 2016, Foley, Emma L wrote:
> 
> > Question is where it should live.
> > Since gnocchi is designed to be standalone, it seem like that's a potential
> home for it.
> > If not, it also fits in with the existing plugin.
> 
> It it's a collectd plugin that talk statsd protocol, I'd say it should live 
> near
> collectd, no?
> 

If it's in Python, collectd doesn't take it. 
I'll house it with the existing plugin. 

Emma



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-02-03 Thread Simon Pasquier
On Tue, Feb 2, 2016 at 5:08 PM, Foley, Emma L <emma.l.fo...@intel.com>
wrote:

> Hi Simon,
>
>
>
> So collectd acts as a statsd server, and the metrics are aggregated and
> dispatched to the collectd daemon.
>
> Collectd’s write plugins then output the stats to wherever we want them to
> go.
>
>
>
> In order to interact with gnocchi using statsd, we require collectd to act
> as a statsd client and dispatch the metrics to gnocchi-statsd service.
>

AFAICT there's no such thing out of the box but it should be fairly
straightforward to implement a StatsD writer using the collectd Python
plugin.

Simon

[1] https://collectd.org/documentation/manpages/collectd-python.5.shtml


>
>
> Regards,
>
> Emma
>
>
>
>
>
> *From:* Simon Pasquier [mailto:spasqu...@mirantis.com]
> *Sent:* Monday, February 1, 2016 9:02 AM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>; Foley, Emma L <emma.l.fo...@intel.com>
> *Subject:* Re: [openstack-dev] [telemetry][ceilometer] New project:
> collectd-ceilometer-plugin
>
>
>
>
>
>
>
> On Fri, Jan 29, 2016 at 6:30 PM, Julien Danjou <jul...@danjou.info> wrote:
>
> On Fri, Jan 29 2016, Foley, Emma L wrote:
>
> > Supporting statsd would require some more investigation, as collectd's
> > statsd plugin supports reading stats from the system, but not writing
> > them.
>
> I'm not sure what that means?
> https://collectd.org/wiki/index.php/Plugin:StatsD seems to indicate it
> can send metrics to a statsd daemon.
>
>
>
> Nope that is the opposite: collectd can act as a statsd server. The man
> page [1] is clearer than the collectd Wiki.
>
> Simon
>
>
> [1]
> https://collectd.org/documentation/manpages/collectd.conf.5.shtml#plugin_statsd
>
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-02-03 Thread Foley, Emma L

AFAICT there's no such thing out of the box but it should be fairly 
straightforward to implement a StatsD writer using the collectd Python plugin.
Simon

[1] https://collectd.org/documentation/manpages/collectd-python.5.shtml

I guess that’ll have to be the plan now: get a prototype in place and have a 
look at how well it does.
The first one is always the most difficult, so it should be fairly quick to get 
this going.

Regards,
Emma


--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-02-03 Thread gordon chung


On 03/02/2016 9:16 AM, Foley, Emma L wrote:
>   AFAICT there's no such thing out of the box but it should be fairly 
> straightforward to implement a StatsD writer using the collectd Python plugin.
>   Simon
>
>   [1] https://collectd.org/documentation/manpages/collectd-python.5.shtml
>
> I guess that’ll have to be the plan now: get a prototype in place and have a 
> look at how well it does.
> The first one is always the most difficult, so it should be fairly quick to 
> get this going.
>

nice, do you have resource to look at this? or maybe something to add to 
Gnocchi's potential backlog. existing plugin still seems useful to those 
who want to use custom/proprietary storage.

cheers,

-- 
gord

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-02-02 Thread Foley, Emma L
Hi Simon,

So collectd acts as a statsd server, and the metrics are aggregated and 
dispatched to the collectd daemon.
Collectd’s write plugins then output the stats to wherever we want them to go.

In order to interact with gnocchi using statsd, we require collectd to act as a 
statsd client and dispatch the metrics to gnocchi-statsd service.

Regards,
Emma


From: Simon Pasquier [mailto:spasqu...@mirantis.com]
Sent: Monday, February 1, 2016 9:02 AM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>; Foley, Emma L <emma.l.fo...@intel.com>
Subject: Re: [openstack-dev] [telemetry][ceilometer] New project: 
collectd-ceilometer-plugin



On Fri, Jan 29, 2016 at 6:30 PM, Julien Danjou 
<jul...@danjou.info<mailto:jul...@danjou.info>> wrote:
On Fri, Jan 29 2016, Foley, Emma L wrote:

> Supporting statsd would require some more investigation, as collectd's
> statsd plugin supports reading stats from the system, but not writing
> them.

I'm not sure what that means?
https://collectd.org/wiki/index.php/Plugin:StatsD seems to indicate it
can send metrics to a statsd daemon.

Nope that is the opposite: collectd can act as a statsd server. The man page 
[1] is clearer than the collectd Wiki.
Simon

[1] 
https://collectd.org/documentation/manpages/collectd.conf.5.shtml#plugin_statsd

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-02-01 Thread Simon Pasquier
On Fri, Jan 29, 2016 at 6:30 PM, Julien Danjou  wrote:

> On Fri, Jan 29 2016, Foley, Emma L wrote:
>
> > Supporting statsd would require some more investigation, as collectd's
> > statsd plugin supports reading stats from the system, but not writing
> > them.
>
> I'm not sure what that means?
> https://collectd.org/wiki/index.php/Plugin:StatsD seems to indicate it
> can send metrics to a statsd daemon.
>

Nope that is the opposite: collectd can act as a statsd server. The man
page [1] is clearer than the collectd Wiki.

Simon

[1]
https://collectd.org/documentation/manpages/collectd.conf.5.shtml#plugin_statsd
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-01-29 Thread Foley, Emma L
> So, metrics are grouped by the type of resource they use, and each metric has 
> to be listed.
> Grouping isn't a problem, but creating an exhaustive list might be, 
> since there are 100+ plugins [1] in collectd which can provide 
> statistics, although not all of these are useful, and some require 
> extensive configuration. The plugins each provide multiple metrics, 
> and each metric can be duplicated for a number of instances, examples: [2].
>
> Collectd data is minimal: timestamp and volume, so there's little room to 
> find interesting meta data.
> It would be nice to see this support integrated, but it might be very 
> tedious to list all the metric names and group by resource type without any 
> form of Do the resource definitions support wildcards? Collectd can provide A 
> LOT of metrics.

One also has to put into balance the upside of going through Ceilometer, as 
Gnocchi has direct support for statsd:

  http://gnocchi.xyz/statsd.html



Supporting statsd would require some more investigation, as collectd's statsd 
plugin supports reading stats from the system, but not writing them.
 Also, what are the usage figures for gnocchi? How many people use it, 
and how easy is it to convert existing deployments to use gnocchi? I mean, if 
someone was upgrading, would their data be preserved?
 How easy is it to consume gnocchi statistics using an external 
system/application?
 I'm not against the idea, but it requires a little more consideration.

Regards,
Emma

--
Intel Research and Development Ireland Limited 
Registered in Ireland 
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare 
Registered Number: 308263



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-01-29 Thread gordon chung


On 29/01/2016 10:48 AM, Foley, Emma L wrote:
>> So, metrics are grouped by the type of resource they use, and each metric 
>> has to be listed.
>> Grouping isn't a problem, but creating an exhaustive list might be,
>> since there are 100+ plugins [1] in collectd which can provide
>> statistics, although not all of these are useful, and some require
>> extensive configuration. The plugins each provide multiple metrics,
>> and each metric can be duplicated for a number of instances, examples: [2].
>>
>> Collectd data is minimal: timestamp and volume, so there's little room to 
>> find interesting meta data.
>> It would be nice to see this support integrated, but it might be very
>> tedious to list all the metric names and group by resource type without any 
>> form of Do the resource definitions support wildcards? Collectd can provide 
>> A LOT of metrics.
> One also has to put into balance the upside of going through Ceilometer, as 
> Gnocchi has direct support for statsd:
>
>http://gnocchi.xyz/statsd.html
>
>
>
> Supporting statsd would require some more investigation, as collectd's statsd 
> plugin supports reading stats from the system, but not writing them.
>   Also, what are the usage figures for gnocchi? How many people use 
> it, and how easy is it to convert existing deployments to use gnocchi? I 
> mean, if someone was upgrading, would their data be preserved?
>   How easy is it to consume gnocchi statistics using an external 
> system/application?
>   I'm not against the idea, but it requires a little more 
> consideration.
>
> Regards,
> Emma
>
Gnocchi is intended to solve the use case of timestamp+value type data, 
that's essentially how it stores it. the best way i would describe it 
is, if you use ceilometer statistics command, you should probably be 
using Gnocchi. if you use ceilometer sample-list, it's arguable whether 
Gnocchi or legacy Ceilometer db is right. so basically do you want 
slower, full-fidelity data (ceilometer) or do you want responsive, 
light-weight data (gnocchi)

Gnocchi implements the concept of archive policies which basically 
dictates how much or little is store. it's purpose is to rollup and 
pre-calculate data so less is stored, and as a side effect, is more 
response as it has less clutter to deal with. in theory, you could 
define a granularity to store everything with no roll ups so all the 
data is preserved, but even though we store timestamp+value: the more 
you store, the bigger the size.

cheers,

-- 
gord


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-01-29 Thread gordon chung


On 28/01/2016 2:32 AM, Foley, Emma L wrote:
> So, metrics are grouped by the type of resource they use, and each metric has 
> to be listed.
> Grouping isn't a problem, but creating an exhaustive list might be, since 
> there are 100+ plugins [1] in collectd which can provide statistics, although 
> not all of these are useful, and some require extensive configuration. The 
> plugins each provide multiple metrics, and each metric can be duplicated for 
> a number of instances, examples: [2].
>
> Collectd data is minimal: timestamp and volume, so there's little room to 
> find interesting meta data.
> It would be nice to see this support integrated, but it might be very tedious 
> to list all the metric names and group by resource type without any form of
> Do the resource definitions support wildcards? Collectd can provide A LOT of 
> metrics.
>
> Regards,
> Emma
>
> [1] https://collectd.org/wiki/index.php/Table_of_Plugins
> [2] https://collectd.org/wiki/index.php/Naming_schema

gnocchi is strongly typed when compared to classical ceilometer db where 
you can dump anything and everything. we don't support wildcards as is 
but i believe it's something we can aim to support?

Mehdi is currently in process of implementing dynamic resources which 
would give more flexiblity on what type of data we can store in Gnocchi. 
i believe from ceilometer pov, we can add support to allow wildcard 
support in regards to adding new metrics.

cheers,

-- 
gord


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-01-29 Thread Julien Danjou
On Fri, Jan 29 2016, Foley, Emma L wrote:

> Supporting statsd would require some more investigation, as collectd's
> statsd plugin supports reading stats from the system, but not writing
> them.

I'm not sure what that means?
https://collectd.org/wiki/index.php/Plugin:StatsD seems to indicate it
can send metrics to a statsd daemon.

>  Also, what are the usage figures for gnocchi?

42?
Not sure what that means :)

> How many people use it, and how easy is it to convert existing
> deployments to use gnocchi?

We don't know how many people are using it, as usual people barely
communicate on their usage and we only know a few operators we are
working with.
There's no conversion tool as of today that I am aware of.

> I mean, if someone was upgrading, would their data be preserved?

It's not an upgrade, it'd be a migration.
So far nobody ever asked for migrating any data, considering it's
simpler to store to Ceilometer database and Gnocchi at the same time for
a while, and then ditch Ceilometer database.

> How easy is it to consume gnocchi statistics using an external
> system/application?

There's a complete REST API documented online at:

  http://gnocchi.xyz/rest.html

I'd say it's pretty easy, but I am not objective obviously.

> I'm not against the idea, but it requires a little more consideration.

Against which idea exactly?

I'm not even sure what you're trying to do and why you're doing in the
first place, so I was just throwing alternative ideas for the sake of
it.

Cheers,
-- 
Julien Danjou
;; Free Software hacker
;; https://julien.danjou.info


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-01-28 Thread Julien Danjou
On Thu, Jan 28 2016, Foley, Emma L wrote:

> So, metrics are grouped by the type of resource they use, and each metric has 
> to be listed.
> Grouping isn't a problem, but creating an exhaustive list might be, since 
> there
> are 100+ plugins [1] in collectd which can provide statistics, although not 
> all
> of these are useful, and some require extensive configuration. The plugins 
> each
> provide multiple metrics, and each metric can be duplicated for a number of
> instances, examples: [2].
>
> Collectd data is minimal: timestamp and volume, so there's little room to 
> find interesting meta data.
> It would be nice to see this support integrated, but it might be very tedious 
> to list all the metric names and group by resource type without any form of 
> Do the resource definitions support wildcards? Collectd can provide A LOT of 
> metrics.

One also has to put into balance the upside of going through Ceilometer,
as Gnocchi has direct support for statsd:

  http://gnocchi.xyz/statsd.html

-- 
Julien Danjou
# Free Software hacker
# https://julien.danjou.info


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-01-27 Thread Foley, Emma L
So, metrics are grouped by the type of resource they use, and each metric has 
to be listed.
Grouping isn't a problem, but creating an exhaustive list might be, since there 
are 100+ plugins [1] in collectd which can provide statistics, although not all 
of these are useful, and some require extensive configuration. The plugins each 
provide multiple metrics, and each metric can be duplicated for a number of 
instances, examples: [2].

Collectd data is minimal: timestamp and volume, so there's little room to find 
interesting meta data.
It would be nice to see this support integrated, but it might be very tedious 
to list all the metric names and group by resource type without any form of 
Do the resource definitions support wildcards? Collectd can provide A LOT of 
metrics.

Regards,
Emma

[1] https://collectd.org/wiki/index.php/Table_of_Plugins 
[2] https://collectd.org/wiki/index.php/Naming_schema 


Original Message-
From: gordon chung [mailto:g...@live.ca] 
Sent: Monday, January 25, 2016 5:12 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [telemetry][ceilometer] New project: 
collectd-ceilometer-plugin

you can consider ceilometer database (and api) as an open-ended model designed 
to capture the full fidelity of a datapoint (something useful for auditing, 
post processing). alternatively, gnocchi is a strongly type model which 
captures only required data.

in the case of ceilometer -> gnocchi, the measurement data ceilometer collects 
is sent to gnocchi and mapped to specific resource types[1]. 
here we define all the resources and the metric mappings available. with 
regards to collectd, i'm just wondering what additional metrics are added and 
possibly any interesting metadata?

[1]
https://github.com/openstack/ceilometer/blob/master/etc/ceilometer/gnocchi_resources.yaml

On 25/01/2016 9:21 AM, Foley, Emma L wrote:
> I'm not overly familiar with Gnocchi, so I can't answer that off the bat, but 
> I would be looking for answers to the following questions:
> What changes need to be made to gnocchi to accommodate regular data from 
> ceilometer?
> Is there anything additional in Gnocchi's data model that is not part of 
> Ceilometer?
>
> Regards,
> Emma
>
>
> -Original Message-
> From: gord chung [mailto:g...@live.ca]
> Sent: Friday, January 22, 2016 2:41 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [telemetry][ceilometer] New project: 
> collectd-ceilometer-plugin
>
> nice! thanks Emma!
>
> i'm wondering if there's an additional metrics/resources we should add to 
> gnocchi to accommodate the data?
>
> On 22/01/2016 6:11 AM, Foley, Emma L wrote:
>> Hi folks,
>>
>> A new plug-in for making collectd[1] stats available to Ceilometer [2] is 
>> ready for use.
>>
>> The collectd-ceilometer-plugin make system statistics from collectd 
>> available to Ceilometer.
>> These additional statistics make it easier to detect faults and identify 
>> performance bottlenecks (among other uses).
>>
>> Regards,
>> Emma
>>
>> [1] https://collectd.org/
>> [2] http://github.com/openstack/collectd-ceilometer-plugin
>>
>> --
>> Intel Research and Development Ireland Limited Registered in Ireland 
>> Registered Office: Collinstown Industrial Park, Leixlip, County 
>> Kildare Registered Number: 308263
>>
>>
>> _
>> _  OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> --
> gord
>
>
> __
>  OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
>  OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--
gord


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-01-25 Thread Foley, Emma L

I'm not overly familiar with Gnocchi, so I can't answer that off the bat, but I 
would be looking for answers to the following questions:
What changes need to be made to gnocchi to accommodate regular data from 
ceilometer?
Is there anything additional in Gnocchi's data model that is not part of 
Ceilometer?

Regards,
Emma


-Original Message-
From: gord chung [mailto:g...@live.ca] 
Sent: Friday, January 22, 2016 2:41 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [telemetry][ceilometer] New project: 
collectd-ceilometer-plugin

nice! thanks Emma!

i'm wondering if there's an additional metrics/resources we should add to 
gnocchi to accommodate the data?

On 22/01/2016 6:11 AM, Foley, Emma L wrote:
> Hi folks,
>
> A new plug-in for making collectd[1] stats available to Ceilometer [2] is 
> ready for use.
>
> The collectd-ceilometer-plugin make system statistics from collectd available 
> to Ceilometer.
> These additional statistics make it easier to detect faults and identify 
> performance bottlenecks (among other uses).
>
> Regards,
> Emma
>
> [1] https://collectd.org/
> [2] http://github.com/openstack/collectd-ceilometer-plugin
>   
> --
> Intel Research and Development Ireland Limited Registered in Ireland 
> Registered Office: Collinstown Industrial Park, Leixlip, County 
> Kildare Registered Number: 308263
>
>
> __
>  OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--
gord


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-01-25 Thread gordon chung
you can consider ceilometer database (and api) as an open-ended model 
designed to capture the full fidelity of a datapoint (something useful 
for auditing, post processing). alternatively, gnocchi is a strongly 
type model which captures only required data.

in the case of ceilometer -> gnocchi, the measurement data ceilometer 
collects is sent to gnocchi and mapped to specific resource types[1]. 
here we define all the resources and the metric mappings available. with 
regards to collectd, i'm just wondering what additional metrics are 
added and possibly any interesting metadata?

[1] 
https://github.com/openstack/ceilometer/blob/master/etc/ceilometer/gnocchi_resources.yaml

On 25/01/2016 9:21 AM, Foley, Emma L wrote:
> I'm not overly familiar with Gnocchi, so I can't answer that off the bat, but 
> I would be looking for answers to the following questions:
> What changes need to be made to gnocchi to accommodate regular data from 
> ceilometer?
> Is there anything additional in Gnocchi's data model that is not part of 
> Ceilometer?
>
> Regards,
> Emma
>
>
> -Original Message-
> From: gord chung [mailto:g...@live.ca]
> Sent: Friday, January 22, 2016 2:41 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [telemetry][ceilometer] New project: 
> collectd-ceilometer-plugin
>
> nice! thanks Emma!
>
> i'm wondering if there's an additional metrics/resources we should add to 
> gnocchi to accommodate the data?
>
> On 22/01/2016 6:11 AM, Foley, Emma L wrote:
>> Hi folks,
>>
>> A new plug-in for making collectd[1] stats available to Ceilometer [2] is 
>> ready for use.
>>
>> The collectd-ceilometer-plugin make system statistics from collectd 
>> available to Ceilometer.
>> These additional statistics make it easier to detect faults and identify 
>> performance bottlenecks (among other uses).
>>
>> Regards,
>> Emma
>>
>> [1] https://collectd.org/
>> [2] http://github.com/openstack/collectd-ceilometer-plugin
>>
>> --
>> Intel Research and Development Ireland Limited Registered in Ireland
>> Registered Office: Collinstown Industrial Park, Leixlip, County
>> Kildare Registered Number: 308263
>>
>>
>> __
>>  OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> --
> gord
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 
gord


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-01-22 Thread Foley, Emma L
Hi folks,

A new plug-in for making collectd[1] stats available to Ceilometer [2] is ready 
for use.

The collectd-ceilometer-plugin make system statistics from collectd available 
to Ceilometer.
These additional statistics make it easier to detect faults and identify 
performance bottlenecks (among other uses).

Regards,
Emma

[1] https://collectd.org/ 
[2] http://github.com/openstack/collectd-ceilometer-plugin
 
--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

2016-01-22 Thread gord chung

nice! thanks Emma!

i'm wondering if there's an additional metrics/resources we should add 
to gnocchi to accommodate the data?


On 22/01/2016 6:11 AM, Foley, Emma L wrote:

Hi folks,

A new plug-in for making collectd[1] stats available to Ceilometer [2] is ready 
for use.

The collectd-ceilometer-plugin make system statistics from collectd available 
to Ceilometer.
These additional statistics make it easier to detect faults and identify 
performance bottlenecks (among other uses).

Regards,
Emma

[1] https://collectd.org/
[2] http://github.com/openstack/collectd-ceilometer-plugin
  
--

Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


--
gord


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev