docker-autoheal VS docker-elk

autoheal

Have you tried autoheal? It's a Test Driven Design-based "auto"-gpt. It iterates on your code until the tests you've created (or created via chatGPT) are passing. I have had mixed results, but I think having tests serves as a good north star for an agent to work toward.

Hello guys, I often have this issue where a container B uses the network of a container A and container A fails at some point. Also I have many dumb containers that will just fail on their own without being restarted. I tried the nice willfarrell's autoheal but it does not support dependencies. I did not want to migrate my setup to some k3s or something that would be way overkill for what I want.

I use autoheal and have the healthcheck below in my docker compose. I also have uptime-kuma monitoring the web page availability for alerting and Tautulli monitoring remote access availability.

As a workaround for this you could use autoheal to automatically restart the kuma container when it becomes unhealthy.

I useautoheal and i try to have a useful healthcheck on all my containers. It is only lacking any kind of notification if a container is unhealthy and is being restarded.

I've figured a workaround by adding a healthcheck to the docker-compose and running an autoheal container, but I just can't quite figure out why I need it in the first place.

Make sure to implement health hecks, so containers restart automatically when your vpn connection drops. Docker doesn't restart unhealthy containers automatically, but you van use autoheal for that. Also use the health status in the depends_on to make sure the containers start in the correct order (start the *arr containers after the vpn is running for example).

Hello everyone! I am trying to get started with ELK and I am facing a very frustrating situation. I am trying to use the stack with Docker Compose. I have tried 2 versions: https://github.com/deviantony/docker-elk and also https://www.elastic.co/blog/getting-started-with-the-elastic-stack-and-docker-compose but they both have the same problem. I inspected the Docker container logs and I get some weird errors:

The waters are further muddied since I started out trying to spin up a docker instance https://github.com/deviantony/docker-elk but I found the config for docker is setup with a different layout, for example with logstash there is no conf.d directory, and pipelines are layed out differently, making it more challenging to use web examples. Overall I've tried many config examples and all have failed.

This is the github project conainer I'm trying to create a stack with: https://github.com/deviantony/docker-elk

Here's a quick way to get your hands into an elasticstack using docker-compose: https://github.com/deviantony/docker-elk

Essentially I've got 2 sets of standard JSON files that I'm trying to ingest into a dockerized ELK stack. The first set was downloaded cloudflare logs, standard line separated JSON data, tried to use Filebeat to ingest and it kept prefixing the JSON data with some dumb ECS event data, basically exactly what this post describes if its easier to see in pics. All of the cloudflare data was nested within the event.original field and would not get mapped. But once I tried to use just logstash directly, it was fine and mapped correctly and no more event data.

i use the elk into the docker,using the docker-elk compose , the logstash logs shows that it is reciving the logs:

It depends on what you want to get out of visualizing your logs. I use the combination of Elastic + Logstash + Kibana (ELK Stack) on docker to visualize things like

I did end up kinda Frankensteining this project and docker-elk. Basically took out the entire etc/pfelk directory from pfelk project and added the pipelines/dashboard/groks etc to docker-elk. This works really will for me since I have several other devices that aren’t OPNSense that I wanted ingested to ELK.