Skip to content
This repository was archived by the owner on Nov 23, 2024. It is now read-only.
/ elasticstack Public archive

preconfigure ELK stack with curator and elastichq

Notifications You must be signed in to change notification settings

effertzdv/elasticstack

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

13 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

My Docker ELK Stack

This a docker-compose collection to run an ELK stack with

  • Logstash
  • Elasticsearch
  • Kibana
  • curator
  • ElasticHQ

Logstash, ES and kibana are the default components. But while running some tests with fast growing syslog files I added curator to keep the number of indices limited and preserve diskspace.

Addtionally I added ElasticHQ - a great tool to manage your ElasticSearch installation.

Most of this repository is based on the excellent work of Anthony Lapenna: https://github.com/deviantony/docker-elk. He made a very good installation and configuration tutorial. Please visit his repo

I did only some tweaks here and there for my personal needs.

Folder for persistent data

Create a volume folder beside(!) the folder containing the docker-compose.yml or change the path in the docker-compose.yml.

installation if you are behind a proxy

build the docker images if you have no direct connection to the internet will fail if you do not define the http_proxy / https_proxy in your Dockerfile:

ENV http_proxy=http://proxyuser:[email protected]:port
ENV https_proxy=http://proxyuser:[email protected]:port

Logstash configuration

The logstash pipeline has some preconfiured inputs und filters:

  • syslog from unifi UAP accesspoints (udp/5142)
  • filebeat from unifi controller log (tcp/5560)
  • syslog from sonicwall TZ und NSA firewalls (udp 5140)
  • filebeat from squid proxy access.log (tcp/5044)
  • syslog from vmware vsphere hosts (udp/514)

The portnumbers refer to to public ports via the docker-compose file. The ports inside the logstash docker image might be different.

curator setup

see actions.yml for details:

Five jobs to keep indices for 14 days

  • unifi-*
  • unifiserver-*
  • vmware-*
  • squid-*
  • sonicwall-*

Add more jobs for new indices. Of course curator can do more then delete the indices.

About

preconfigure ELK stack with curator and elastichq

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages