Code Monkey home page Code Monkey logo

elk-with-filebeat-by-docker-compose's Introduction

Hits Linkedin: gnokoheat GitHub gnokoheat

https://github.com/gnokoheat

https://github.com/gnokoheat

elk-with-filebeat-by-docker-compose's People

Contributors

gnokoheat avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

elk-with-filebeat-by-docker-compose's Issues

filebeat error

I'm trying to run your project in docker but it keep raising an error that can not connect to logstash from filebeat. Any ideal for this ?

Screen Shot 2022-11-29 at 18 54 22

Getting the following issue.

➜ elk-with-filebeat-by-docker-compose git:(master) docker-compose up -d

[+] Running 2/11
✘ kibana Error 2.4s
⠼ logstash Pulling 2.4s
✘ elasticsearch Error 2.4s
⠼ filebeat 7 layers [⠀⠀⠀⠀⠀⠀⠀] 0B/0B Pulling 2.4s
⠼ c808caf183b6 Pulling fs layer 0.4s
⠼ 0ad724d0d2e4 Pulling fs layer 0.4s
⠼ 96c1ebfd2ab2 Pulling fs layer 0.4s
⠼ 96df637ea680 Waiting 0.4s
⠼ 77792ec475bc Waiting 0.4s
⠼ c68751b9be58 Waiting 0.4s
⠼ 967522c87331 Waiting 0.4s
no matching manifest for linux/arm64/v8 in the manifest list entries

elasticsearch exited with code 137

First of all, many thanks for making this! 🥳

I cloned the project and run docker-compose up everything seems to be ok until I found the error message:

elasticsearch exited with code 137

I did a quick research and found that it might relate to memory and look at the docker-compose.yml and seems like (if I understand correctly) that you set the maximum memory of elasticsearch to 512mb.

So I wonder if you faced the issue as I described above? and if you could share idea about this problem.

again, thank you very much for making this 👏

Logstash error

Attempted to resurrect connection to dead ES instance, but got an error {:url=>"http://elasticsearch:9200/", :exception=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :message=>"Elasticsearch Unreachable: [http://elasticsearch:9200/][Manticore::ClientProtocolException] elasticsearch:9200 failed to respond"}

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.