| func TestOpenMetricsParseErrors(t *testing.T) { | |
| cases := []struct { | |
| input string | |
| err string | |
| }{ | |
| { | |
| input: "", | |
| err: "unexpected end of data, got \"EOF\"", | |
| }, |
Hello,Got another issue with our custom exporter in Prometheus 2.6 (worked in 2.5 and below).We are now getting-msg="append failed" err="unexpected end of data, got \"EOF\""
Errors - it's not a timeout as it's well below the duration/timeout values.Curl'ing the data looks good and piping through "promtool check metrics" complains about the lack of help text but that is all.The only thing I can possible see it that some parts have spaces in (some don't) for example:-msg_queues_is_durable{server="myserver",vpn="#config-sync",queue="#CFGSYNC/OWNER/ONE/VPN/TWO VPNNAME/CFG"} 1.0But this has never been an issue before, this from the openmetricsparse_test.go:-
func TestOpenMetricsParseErrors(t *testing.T) { cases := []struct { input string err string }{ { input: "", err: "unexpected end of data, got \"EOF\"", }, Is the only reference I can see to it but no idea why it's getting caught ?Any help much appreciated.Thanks.
--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To post to this group, send email to promethe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/37b023e3-2141-406c-b094-9cec596f256b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
On Fri, 4 Jan 2019 at 17:30, 'Paul Seymour' via Prometheus Users <promethe...@googlegroups.com> wrote:Hello,Got another issue with our custom exporter in Prometheus 2.6 (worked in 2.5 and below).We are now getting-msg="append failed" err="unexpected end of data, got \"EOF\""What version of the Python client are you using?Brian
--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To post to this group, send email to promethe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/CAHJKeLoSKSSMuK5nRS_-ABLj5iXe%3DjSAF88FhWm-1Gw4MHjEZg%40mail.gmail.com.
We should not be breaking scrapes, even if they're not technically correct, without a major version bump.
What are the headers going each way, and which java client is it?--Brian Brazil
Thanks
--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To post to this group, send email to promethe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/ee33273d-e690-4794-baa7-0f2cb6f6bb61%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I can't find any Prometheus-related code in there, or even a http server. Can you point me at the relevant parts?
Convinced this is because this exporter doesn't appear to be sending metrics data back in plaintext encoding. But it's not my code so cannot say for sure.
Convinced this is because this exporter doesn't appear to be sending metrics data back in plaintext encoding. But it's not my code so cannot say for sure.
On Monday, 7 January 2019 15:59:40 UTC, Paul Seymour wrote:
Convinced this is because this exporter doesn't appear to be sending metrics data back in plaintext encoding. But it's not my code so cannot say for sure.This was true. It was the encoding. It's not gzip and the type wasn't coming in as text/plainI think this commit was the one that changed the behaviour.
The error message was a little odd. But makes sense ultimately.Thanks again to Brian for pointing me in the right direction on this. Using https and the endpoint on k8s and going through a few layers made it fun :)
--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To post to this group, send email to promethe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/7cdf1a7c-8b18-48e6-9e76-32543b800af8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
It should be encoded as utf-8, what is the content-type?
It should be encoded as utf-8, what is the content-type?The charset was UTF-8 but the was text/html, forcing plain text made it work as it's not gzip'ed I think the commit I referenced in the other mail was the one that changed the behaviour between versions.
Thanks so much for the help, and your time.
Something is still not right here, if we don't recognise the content-type we should be treating it the same as text/plain. What exact headers were you sending back?Brian