Getting unexpected_error when trying to query Prometheus about prometheus-query-js HOT 11 OPEN

TBH it has been a while since I worked on it, so I will try to find time to look into it but not promising anything :)

from prometheus-query-js.

Hi @omerlh

Can you tell me more about this issue, please?
I didn't find any information about such a requirement.

Are you using This library from a browser or into NodeJS? 🤔

Do you confirm this is not a proxy configuration in front of your prometheus server?

• reference to a Prometheus Github issue?
• some error message?

Thanks for your help ;)

(FYI, unexpected_error may be inserted into response by the library itself =>

from prometheus-query-js.

I am using NodeJS. Not using proxy, but using kubectl port-forward to access prom - not sure if related...

from prometheus-query-js.

kubectl port-forward is a simple tcp proxy. I don't expect any error here.

I suppose your proxy connection was broken at that time, and the lib responded with an "unexecpted_error" message.

I let the issue opened, in case we have a similar bug report in the future.

from prometheus-query-js.

Nope, this was very reproducible: as long as gzip encoding is not set, it was broken. Once I added it, it was solved...

from prometheus-query-js.

fixed v3.0.1

from prometheus-query-js.

hi @omerlh,

Since setting the Accept-Encoding header is forbidden, I wonder what browser are you using?

Looks like browsers automatically set this header.

from prometheus-query-js.

I am not using a browser... The code I wrote was running in nodeJS

from prometheus-query-js.

This is really weird. I cannot reproduce your error.

Can you start a local Prometheus instance ? docker run --rm -it -p 9090:9090 prom/prometheus:v2.25.0

Then: npx ts-node examples/nodejs/app.ts (replace the hostname at the top of the file)

I upgraded Axios yesterday. Can you try again please?

from prometheus-query-js.

I get the same problem with my "proxy" I made for my API, all I did was add the Authorization header to my user's access token. Works fine in curl but fails with the error message described here.

from prometheus-query-js.

I might have a solution, it just needs to be verified. You just need to append this to your PrometheusDriver configuration:

{
  requestInterceptor: {
    onFulfilled: (cfg) => ({
      ...cfg,
      responseType: 'json',
      decompress: false
    })
  }
}

from prometheus-query-js.