JSON API: Bad Gateway

[grafana]

JSON API: Bad Gateway

[zoltanbedi]

Thanks for coming back @AP-XD. I'm going to close this then.

[mbarradas]

I'm pasting the error I'm getting I guess the issue is related with the call being done through ip and not by the url of the process.

error="http: proxy error: dial tcp ip:port: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond."

[marcusolsson]

@mbarradas Are you still experiencing this issue?

[DanielA2119]

Marcus,
I have a similar issue when attempting to connect to Azure for getting alert status information. First I get an error that API version is required, I add it to the headers section then I get a bad Gateway error. Could an example of a working connection to Azure using this DataSource plugin be provided? Here is a link to Microsofts DOC on the what I am attempting to perform. https://docs.microsoft.com/en-us/rest/api/monitor/alertsmanagement/alerts/get-all. Thanks.

[AP-XD]

Hello I just wanted to share that I also faced the similar issue while serving json file using localhost
But when I use npoint.io for it it works fine.

[0128zzc]

hi how can I solve this problem ?

[0128zzc]

I meet the same question with you

[Christoper-Lloyd2]

I have also experienced the same issue as @AP-XD

Please note that the bad request in the second image is not my issue, it's simply because my endpoint does not return JSON at the root URL, everything works fine with the datasource in the second image

[VictorZuluaga]

Hello I just wanted to share that I also faced the similar issue while serving json file using localhost But when I use npoint.io for it it works fine.

Use your IPV4 instead of localhost, it worked for me

[AP-XD]

Hello I just wanted to share that I also faced the similar issue while serving json file using localhost But when I use npoint.io for it it works fine.

Use your IPV4 instead of localhost, it worked for me

Yeah I also used npoint in the beginning but it was not a good solution for me to use ipv4 because I needed to serve some metrics which was being generated locally.
So actually what I did was create a kubernetes service for hosting the metrics locally which would be accessible by the kubernetes environment and thereby the grafana pod.
I needed it this way because other metrics were also being served to the grafana pod via prometheus which was also in kubernetes environment.

[AP-XD]

This issue can be closed I think @marcusolsson .
Since being unable to access localhost in environment other than kubernetes is a problem in grafana.
For which they have also provided a config hostNetwork: true in case if you want to access it though.

[TomiwaAribisala-git]

Hello I just wanted to share that I also faced the similar issue while serving json file using localhost But when I use npoint.io for it it works fine.

Hello, please I have a similar issue, I am running a Thanos Query Frontend locally and I want to add its URL in the datasource plugin, its giving JSON API: Bad Gateway, please how to I convert the URL:http://localhost:10901/ to npoint if it could work, I have attached images of the Datasource Plugin and Thanos URL