Hacker News new | past | comments | ask | show | jobs | submit login

We don't use tags, but we basically encode tags into the metric name of our time series. An example would be "host.queries.c.1374c6821ead6f47.tput". This tells you the category, type of query, query ID, and the metric associated with it. In this case, it's the time series for the throughput of the query with ID 1374c6821ead6f47.



If you have multiple tags, do you canonicalize the ordering of the metric name? If so, where does that canonicalization happen (on the metric origination side or on the server/collection side)? It would seem to be a pain if you end up with metrics named

    host.queries.type=GET.result=200.tput 
and

    host.queries.result=200.type=GET.tput


Good question. We do have a specific ordering, and that happens when the metrics are generated. Again, we don't really treat them as tags for a specific metric, but rather unique metrics. Having a different name means it's a different metric.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: