Björn Rabenstein
Björn Rabenstein
I mostly assigned this to myself as a “default” because I used to be the maintainer of this repo. Therefore, I'm un-assigning this from myself no. New maintainers @bwplotka &...
Parser shenanigans aside, the actual issue here is that the standard metrics exposed by the Go collector are fine with the old Prometheus formats, but run into a known issue...
It made me quite happy that finally tools like Grafana start to make use of metadata in tooltips etc. Obfuscating counters as unknown is not ideal for them.
Yes, that's what I had in mind. It's still not ideal… :disappointed:
Depending on the decision on https://github.com/prometheus/docs/issues/543, it might be alright to not tolerate trailing whitespace.
Un-assigning from myself as I intend to focus on other Prometheus project. Right now, others are way more involved in text format affairs than I am.
I guess a typical scenario where to run into this is the textfile collector of the node exporter. That's where all kind of whitespace usage will be encountered because the...
We wouldn't change the creation code, we would only make the parser more tolerant. It doesn't have to be part of the standard, it's just following the https://en.wikipedia.org/wiki/Robustness_principle . Obviously,...
I don't follow that line of argument. It all hinges on the premise that the parser is a compliance test and that the parser code defines the standard. For better...
Most people who run into this issue will probably realize after a while that they made a mistake. Very few will come here and complain. It is still surprising that...