Elasticsearch has common thread defaults for bulk requests. If you need to tune or gap certain problems, you can change the thread and thread pool size settings in elasticsearch.yml. In general it is not recommended to tweak anything! Use it at your own risk!
This post demonstrates the usage of the Cardinality feature.
X-Pack Alerting aka Elasticsearch Watcher can run distributed in a Elasticsearch cluster.
Metricbeat as docker container, is a decent monitoring solution to monitor other docker containers in conjunction with Elasticsearch and Kibana. Additionally metricbeat can monitor the docker system itself. You might run into some problems, which I would like to share.
I have two ramp up for two data-centers each a Apache Kafka cluster. Maintaining the cluster with the Kafka Manager GUI by Yahoo is pretty comfortable. Since both data-centers are protected by firewall, a web-proxy must forward it for my remote access.
If you are using X-Pack Monitoring you have a good overview of your Kibana performance. Sometimes it is necessary to know more. Packetbeat can monitor your http traffic between Kibana and the Elasticsearch node.
X-Pack Reporting allows to automate and generate daily reports on pre-existing dashboards or visualizations in Kibana. To keep security tight I have created a reporting user. The first run with the reporting user gave me some mystery. Reporting complained Dashboard with id 'AWLOnWVZLaWygeBEGxLJ' not found. I did some digging and found the reason, which I am going to elaborate about in this post.
Using Python on Windows is not my first choice but if you have to, here are some recipes how to use pip behind a proxy. This post assumes that you are using CNTLM as running proxy.