[collectd] RFC: Changes to data sources and naming schema

Pierre-Yves Ritschard pyr at spootnik.org
Mon Sep 23 21:56:01 CEST 2013


resending, forgot list


On Mon, Sep 23, 2013 at 9:54 PM, Pierre-Yves Ritschard <pyr at spootnik.org>wrote:

> The idea is to have a simple way of naming things, the identity of a
> metric will be defined by the keys in the attr section.
> To generate path names for graphite or rrd plugins, the write output
> plugin would look for special expected keys (source, metric). Input plugins
> could additionally hint at the way to format
> their name, by specifying a list of keys to look up (e.g: format: [
> "source", "cpu-type", "cpu-id"]).
>
> This would actually make the metric names of such plugins as IPMI or
> GenericJMX much cleaner, especially with graphite since right now it's a
> mess of arbitrary length trees
>
>
>
> On Mon, Sep 23, 2013 at 9:45 PM, Poil <poil at quake.fr> wrote:
>
>>  It's a good idea to change this naming schema.
>>
>> I like the first alternative "a path", really simple, and easy to draw,
>> group ...
>> I don't understand how you can have a JSON object with RRD/Filesystem,
>> will you go on a only nosql storage ?
>>
>> If you use a path, types.db can be limited to derive/counter, the labels
>> can be in the path himself or in the filename, like this we will not have
>> to deploy it on all nodes when we need a new "type"
>>
>> Today I have to hack it for GenericJMX, Curl, some python code ...
>> I'm using this (
>> https://github.com/Poil/CGraphz/wiki/CGraphz%20Naming%20Schema) :
>>
>>    - host
>>    - plugin
>>    - plugin category (custom optional)
>>    - plugin instance (optional)
>>    - type
>>    - type category (custom optional)
>>    - type instance (optional)
>>
>> PluginCategory is used to separate
>> GenericJMX|varnish|curl_json|curl|curl_xml|P2000|tcpconns
>> TypeCategory is used to separate some customplugins
>> (GenericJMX|elasticsearch|P2000)
>>
>> Regards,
>>
>>
>>
>>
>> _______________________________________________
>> collectd mailing list
>> collectd at verplant.org
>> http://mailman.verplant.org/listinfo/collectd
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.verplant.org/pipermail/collectd/attachments/20130923/ac98a785/attachment.html>


More information about the collectd mailing list