I really like working on ElasticSearch, so powerful, so easy to use, so scalable and so high available. I’ve found a very interresting book I bought on it.
It will help you to start with ElasticSearch and answer a lot of question you may have regarding the product. If you want to buy it, take a look there.
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.
My use case is specific but not isolated. When I’m at work, I’m connected to my VPN at home. I have a specific DNS at home for my domain in deimos.lan and this is very useful to avoid me to remind all the IP of the services I have.
Sometimes, I want to connect to a home service from the VPN, but my bookmarked links have my home DNS which are unknown from the DNS at work.
Ubiquiti brings software that are easy to install on Windows and Mac OS. However as it is strongly recommended to let this software always up, it’s preferable to have a Linux version to run it in a container or a virtual machine. That’s why I decided to install it for a powerstrip mPower on Debian inside LXC.
The documentation is very poor, that’s why I made this one for those who want to do like me.