Hi I’m new with Elasticsearch, i want to export some logs from elastic to grafana so i can create a dashboard.
I followed the instruction of grafana documentation documentation, but i got this error when i try save .
Elasticsearch error: Bad Gateway
Elastic search turns on localhost:9200, the name of the index and the other information are correct, you will find my configuration below
If it is running locally you need to use
I tried with http://localhost:9200 and it did not worked
what do you see when you plug
in your browser? Is elasticsearch install on same server as grafana?
This is the result;
{
“name” : “340369c2e7f8”,
“cluster_name” : “docker-cluster”,
“cluster_uuid” : “Ul_D4OfsRO63r_ZAalTnSw”,
“version” : {
“number” : “7.5.0”,
“build_flavor” : “default”,
“build_type” : “docker”,
“build_hash” : “e9ccaed468e2fac2275a3761849cbee64b39519f”,
“build_date” : “2019-11-26T01:06:52.518245Z”,
“build_snapshot” : false,
“lucene_version” : “8.3.0”,
“minimum_wire_compatibility_version” : “6.8.0”,
“minimum_index_compatibility_version” : “6.0.0-beta1”
},
“tagline” : “You Know, for Search”
}
yes, I’am using both of them on my computer, I use the docker version
A solution to “Elasticsearch error: Bad Gateway” that worked for me:
Both Elasticsearch and Grafana containers need to be on the same network.
If you are using Docker, I advise you to install another container called “Portainer”. It’s a web interface where you can visualize and manage your Docker. From there, you could then very easily change or add a network to a container.
Hello, I’m using docker-compose to run zammad and docker to run grafana, I installed Portainer and I’ve put grafan container in the zammad network, I sill have the same issue “Elasticsearch error: Bad Gateway”, can you help please ?
I resolve this passing host.docker.internal:9200 instead https://localhost:9200
