Elasticsearch Logstash config for ELK stack explained On my previous blog post about installing ELK stack without sudo access[1] one of the commentator asked me about explaining the Logstash config in more detail. For ease of reference the Logstash
Elasticsearch Install ELK stack without sudo access Recently, on my blog post on installing ELK stack on Ubuntu/Debian I was asked if it was possible to have ELK stack running on a server without sudo access. I admit it's
Logstash Send stats to Graphite via Logstash We have some stats being calculated and logged in our logs and we wanted to plot graphs via our already running Graphite service. There are two ways to approach this issue. You can
Logstash Logstash Shipper / Forwarder Once you have the ELK stack installed, you can then ship/forward your logs to the redis database on the ELK stack. Once your logs are on the redis database, the logstash on
Logstash Install Logstash shipper on RedHat 5.4+ Installing Logstash on older versions of RedHat can be a real pain. If you are struck with the familiar LoadError: Could not load FFI Provider: (NotImplementedError) FFI not available: null then follow on!
ubuntu Install ELK Stack on Ubuntu/Debian How to install ELK and configure it on your server (Ubuntu/Debian)? You can follow the steps below to install and configure Elasticsearch-Logstash-Kibana (ELK) stack on Ubuntu/Debian server. If you are familiar
Elasticsearch Why ELK stack Problem statement: You have different applications feeding into each other. Debugging an issue requires logging into each individual box to look at the logs. With small number of apps/boxes it's not an