Current metric name structure is hard to parse
See original GitHub issueCurrent metric name structure is hard to parse for other applications like influxdb(see more explanations here)
So I propose the metric name to be in a more uniformed structure, as <prefix><hostname>[suffix]<metric name><measure>[device], for example,
servers.localhost.cpu.cpu0.irq => servers.localhost.cpu.irq.cpu0
servers.desolation.loadavg.01 => servers.desolation.loadavg.01
servers.desolation.iostat.sda.reads => servers.desolation.iostat.reads.sda
To do this, we need to patch some of the collectors. And I don’t think these changes would break the use cases before.
Issue Analytics
- State:
- Created 8 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
text format parsing error in line 1: invalid metric name · Issue ...
Exactly what it says, you have duplicate metrics. It looks like you're missing labels.
Read more >Simple way to parse a person's name into its component parts?
If you must do this parsing, I'm sure you'll get lots of good suggestions here. My suggestion is - don't do this parsing....
Read more >“gnparser”: a powerful parser for scientific names based on ...
This makes most names amenable to parsing by regular expressions. Current examples of scientific name parsers based on regular expressions ...
Read more >Parser FAQ - The Stanford Natural Language Processing Group
Yes, you can train a parser. You will need a collection of syntactically annotated data such as the Penn Treebank to train the...
Read more >difference between soft parse and hard parse - Ask TOM
Can you explain briefly the difference between soft and hard parse? ... COM> column name format a40 ops$tkyte@ORA817DEV.US.ORACLE.COM> declare 2 l_start ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

So many refactors, so little time.
We should just cut a release of python-diamond now, start removing all the collectors, make a new release that supports external collectors, then start working on something that can resolve this. 😦
http://metrics20.org (not sure how old/active/relevant this still is, but worth a read)