Using . in performance data labels has effect on graphite usage
When using "." in a performancedata label and sending the data to graphite, every . marks another level in the path within carbon/graphite.
At first I thought the output should be changed but I'm not sure if this won't be a feature when sending more and more performance data to graphite.
Should I change the output to keep the graphite tree flat?
PNP as fare as I am aware will have no problems with it and for Graphite it is a nice feature which also helps when creating templates.
+1 for keeping them as long as you think naming (and grouping by doing so) is good
Thank you for your feedback! It is much appreciated.
Closed, since it seems we're keeping the dots for now. We could introduce a flag to change the separator in the future