srch

Read before posting: Please include this information: What Grafana version are you using? 5.4.2 What datasource are you using? prometheus ...

31.03.2019 · I think my setup or configuration is wrong. I have version 6.0.2 installed on a 64-bit machine running Windows 10 (grafana-6.0.2.windows-amd64). I am accessing the internet via a 4G mobile hotspot, which is my only option. I can run dashboards with TestData, but cannot connect to ANY datasources! The one I need to connect to is InfluxDB. I keep getting ‘Network …

11.12.2017 · I had the same problem and found that changing access from Server to Browser fixes it. It appears that the grafana server if being prevented from accessing the address:port while the browser is not blocked.

Prometheus as data source for Grafana: HTTP Error Bad Gateway ... I am using Amazon Linux on some EC2 instances. I'm using one instance and trying ...

The datasource in Grafana should be http://prometheus:9090 , this should also be created during initial setup.

11.12.2017 · I had the same problem and found that changing access from Server to Browser fixes it. It appears that the grafana server if being prevented from accessing the address:port while the browser is not blocked.

In the HTTP settings of Grafana you set Access to Proxy , which means that Grafana wants to access Prometheus. Since Kubernetes uses an ...

27.05.2019 · You need to make sure that Grafana server (backend) can communicate with your prometheus server when you’re using Access: Server. So a curl from grafana server should be able to reach your prometheus server for example.

Hello I have deployed grafana on openshift, and Prometheus on a xaas server for monitoring Cassandra. I am able to c metrics on my own ...

Grafana HTTP Error Bad Gateway and Templating init failed errors ... Prometheus server, alertmanager grafana can run after set port-forward:

What happened instead? Error with 'HTTP Error Bad Gateway'. I run grafana and prometheus in docker with almost default configuration. after both ...

18.01.2018 · In the HTTP settings of Grafana you set Access to Proxy, which means that Grafana wants to access Prometheus. Since Kubernetes uses an overlay network, it is a different IP. There are two ways of solving this: Set Access to Direct, so the browser directly connects to Prometheus. Use the Kubernetes-internal IP or domain name.

04.02.2021 · I had the same problem and found that changing access from Server to Browser fixes it. It appears that the grafana server if being prevented from accessing the address:port while the browser is not blocked.