Thanks Dan, that's very neat!
(For code blocks, in groups.google.com web interface anyway, I just select
the text and set font to 'Courier New'. I can't see a less dumb way of
doing this)
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
T
I should include the relevant article:
https://www.robustperception.io/invalid-is-not-a-valid-start-token-and-other-scrape-errors
(and in other news I need to figure out how to paste code blocks)
On Tuesday, November 16, 2021 at 8:10:34 AM UTC+2 Dan S wrote:
> You can use promtool for this:
>
>
You can use promtool for this:
```
cat metrics.txt | promtool check metrics
error while linting: text format parsing error in line 444: unexpected end
of label value "persistent://public/default/"
```
these metrics have values with quotes in them, there's a several:
pulsar_subscriptions_count{cl
> As for the binary chop method, it's really a bit complicated
I'm not going to do it for you.
If this is broken metric output from pulsar, then I suggest you take your
problem to the pulsar mailing list. I suggest you'll likely get a quicker
response if you can help them by proving which
First try a couple of simple things:
curl http://10.70.20.10:8080/metrics -o metrics.txt
grep INVALID metrics.txt
If the grep doesn't find anything, then examine the file manually for
structural errors. Maybe you have a label name with an invalid character?
The valid characters in label names
5 matches
Mail list logo
