Metric 2.0 Format

Instead of sending metrics without the property names as in the Graphite convention, Anodot recommends the following metric 2.0 naming format: 

property1=val1.property2=val2. … .what=<what do I count/measure>

For example, in the metric 2.0 format, the above example is reported as:

device=android.browser=chrome.country=US.eventID=7033.metricType=
event_counts.what=clicks 

The “what=” property describes what is actually being measured, while the rest of the properties describe the various dimensions used to create the measure.

By adding the property name with equal sign (=) to each token, you can use the Anodot service to easily find, aggregate, manipulate and understand any metric.

The order of the property-value pairs in a 2.0 metric does not matter. All you need to do is simply be consistent with the property names, making sure that each metric has a unique name. Metrics are uniquely identified using their generated names; therefore, no two metrics should share all the same the property-value pairs.

If you adopt the recommended metrics naming convention into Anodot, you’ll gain many benefits: Anodot’s flexible metric search will take into account the properties you defined to make it easier to find what you need, create new metrics that are functions of existing ones, easily define alerts and dashboards. Everyone in the organization will be able to understand better the anomalies and find those that are relevant to their needs. It will also provide future benefits for additional advanced analytics capabilities, like predictions and advanced alerting.

Was this article helpful?
0 out of 0 found this helpful