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@verplant.org
http://mailman.verplant.org/listinfo/collectd
