Metrics name - Large System - Avoiding Name collision

[RajanBhatt]

I am soliciting Metrics name convention. in large deployment. Metrics name should not collide with each other and I believe Metrics name should represent where it came from Host name, Data center Name, Application Name and Metrics Name

So,

DatacenterName.HostName.ApplicatioName.MetricsName

At the same time size of metrics name should be around reasonable size may be 30 characters. Metrics name also cab be used for co-relation with other Metrics and potentially log file system.

Any idea or suggestion on this issue

Thanks in advance for your thoughts and suggestions.

[eladroz]

Hi, Seems reasonable to me, but you may need to find some short abbreviations for any of the metric name components, to keep the name short.

Note that after you settle on a convention and start sending metrics, it's a cumbersome manual process to change the existing file names in Graphite if you ever want to change the convention and keep older data accessible.

[mrtazz]

I think this is generally the way to go. It really depends on your setup and for business metrics (like logins) it might not be that important to track where it's coming from.

Closing this, if you still have questions about it, please feel free to reopen.