Deploy ELK stack, ready for production.

Note

All settings are use default value. I re-command you to have at least 3 nodes(8CPUs, 16GB memory, 128GB free disk space) to deploy your ELK cluster.

It's not ready for huge business before doing some tune up.

For test only, you can run vagrant up. You need vagrant, 22GB RAM and 22 CPUs on your single host.

Easy scale and rolling upgrade for ELK stack.
Consul as internal DNS service. Scale your ELK without updating the beats output configuration.
Monit as monitoring service. Auto fix common issue, free you hands.

Elastic version	Ubuntu Server 16.04	CentOS 7
6.5.1	Yes	Yes
6.4.0	Yes	Yes

Name		Name	Last commit message	Last commit date
Latest commit History 287 Commits
danger		danger
deploy_report/keepalived		deploy_report/keepalived
docs		docs
inventories/example		inventories/example
roles		roles
templates		templates
vars		vars
.gitignore		.gitignore
.gitmodules		.gitmodules
00-download_files.yml		00-download_files.yml
01-env_init.yml		01-env_init.yml
02-deploy_consul.yml		02-deploy_consul.yml
03-deploy_redis.yml		03-deploy_redis.yml
04-deploy_kibana.yml		04-deploy_kibana.yml
05-deploy_logstash.yml		05-deploy_logstash.yml
06-deploy_elasticsearch.yml		06-deploy_elasticsearch.yml
07-deploy_monit.yml		07-deploy_monit.yml
08-deploy_beats.yml		08-deploy_beats.yml
09-deploy_search_guard.yml		09-deploy_search_guard.yml
10-deploy_keepalived.yml		10-deploy_keepalived.yml
98-upgrade_elk_cluster.yml		98-upgrade_elk_cluster.yml
99-upgrade_system.yml		99-upgrade_system.yml
LICENSE		LICENSE
README-cn.md		README-cn.md
README.md		README.md
Vagrant.sh		Vagrant.sh
Vagrantfile		Vagrantfile
ansible.cfg		ansible.cfg
apt_sources.list		apt_sources.list
bootstrap-ansible.sh		bootstrap-ansible.sh
hosts.ini.sample		hosts.ini.sample
play-all.yml		play-all.yml
windows.tmux.split4		windows.tmux.split4