Following the deployment blog post I made on ES/Kibana/Fluentd, I released new version of Fluentd and Kibana playbooks to support the latests versions of themselves and ElasticSearch. ElasticSearch 1.4 version is ,out which doesn’t changed anything for the deployment. However Kibana requires to enable an ElasticSearch configuration option now, to work properly. I updated the Kibana playbook for it. On its side, Fluentd has the major release 2.0 out and I updated Ansible playbook for the best integration with Debian Wheezy.
First of all I will only talk about open sources solutions. I don’t want to take part of any commercial one. In addition, I will focus on only 4 solutions which seem to me the most used at this time. I will also talk about my history, my level on each one and why I recommend or not that solution. Puppet is in my opinion the most known solution. Because of the marketing they were/are doing, because it was a good alternative compared to the old cfengine.
During the last weeks I started to play with Elasticsearch, Fluentd and Kibana. I made a documentation to help on deploying it easily. As you may know, I’m an Ansible fan, so I made Ansible playbooks to deploy a complete infrastructure (server and clients). They will deploy this kind of architecture: On the client side, Fluentd clients will get syslog and Nginx logs, to send them to the Fluentd server. On the server side, a Fluentd receiver will be there to get data from other Fluentd clients.
In the previous posts, I’ve introduced my Ansible playbooks for kibana and Elasticsearch. You may now be happy to know that I’ve made an Ansible playbook for Fluentd as well. If you still don’t see what those tree ansible playbook can do when they are combined together, you’ll see in the next post :-)
In my last post you’ve seen the Ansible playbook I’ve made for ElasticSearch. I’ve made a new one, but for Kibana which is able to easily manage version upgrade and of course is easy to install and use. You can find my Kibana playbook on GitHub. The next once will of course be related to fluentd :-)
As I’m an Ansible fan, I’ve created a playbook for it available on GitHub and on the Ansible Galaxy. You’ll be able to add additional plugins like Head, Curator, Mavel… I hope you’ll enjoy it.
I recently migrated this server to a new one. New hardware, better performance, less power consumption etc…Thanks Online. I’m already using LXC on my home server and see the benefits for 8 months ago. That’s why I decided to migrate this server to LXC as well. The difference here is that I wanted to migrate my VM from KVM. All my KVM VM are on Debian Wheezy so that was pretty easy.