When I run docker compose up -d all the containers start like they should but my Logstash container is not able to connect to my ES Cluster.

Emitrr cost

"The amount of hair I lose in the shower doesn’t seem proportional to the amount I actually have on my head (a lot vs a little). My body hair is darker and courser than it ever was before. I’m much more of a lightweight these days; I cannot drink or smoke like I used to. I’m a lot more sensitive to foods (spicy foods, dairy, gluten) than ever before. Getting old is a privilege, but it also kinda sucks."

I'm able to authenticate using elastic/changeme as the creds when I try accessing the ES cluster from the webui and get the following response:

Ringover

Podium

Fwiw, I had some connection issues when I was initially setting up my docker services as well. I had ended up switching from container names to hosts => ["https://tasks.elasticsearch:9200"] which apparently uses some docker internal networking to reference the container services since I couldn't connect via _app.

But since you are using https you will have to provide the ca certificate as @stephenb mentioned or set ssl_verification_mode to none in the elasticsearch output.

If you move past using docker-compose for it and making services of the stack it might be something to try if you have networking issues again.

"I’m 52 and a woman. When I bring in groceries, I can no longer put the grocery bags on my forearms. A grocery bag with four standard-size cans of soup leaves a perfect bruise matching the bag handles on my forearm. I’ve lightly bumped my arm on the edge of something, tore my skin, and bled like a stuck pig."

Emitrr competitors

Emitrr reviews

I would think the are all on the local docker network... its is possible since the first uses 9200 the others use 9201 9202 etc

"I’ve had microfractures in my foot and a broken fibula from a fall that would’ve just meant a bruised butt in anyone else. This happened the minute I started getting into my 'waning years.'"

Using localhost means that Logstash will try to connect to an Elasticsearch instance running on the same machine/container, which is not your case since they are on different containers.