6.4.2
Elasticsearch, Kibana and Logstash 6.4.2
This release adds support for deploying Elasticsearch Kibana and Logstash 6.4.2 to Azure!
Features
#223 Add Logstash to Marketplace UI and ARM template 🌳
Logstash has been added to the Marketplace UI and ARM template. This is an initial implementation, with possibility to expand in future based on feedback and usage. It deploys a single instance of Logstash, with configurable VM SKU, when logstash
is set to Yes
, with the default being No
.
#225 and bc04447 Add support for Elasticsearch, Kibana and Logstash 6.4.1 and 6.4.2 🥇
Support is added for the latest Elastic Stack release, which brings a heap of new goodness including:
- Logstash integration with Azure Monitoring module
- Field aliases
- New Elasticsearch SQL enhancements
- Custom rules for fine tuning machine learning results
amongst others
#230 Enable accelerated networking for supported VM SKUs
Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, greatly improving its networking performance. This high-performance path bypasses the host from the datapath, reducing latency, jitter, and CPU utilization.
This feature enables accelerated networking by default for those VM SKUs that support it, with the ability to override this using specific parameters for
vmMasterNodeAcceleratedNetworking
: for master nodesvmDataNodeAcceleratedNetworking
: for data nodesvmClientNodeAcceleratedNetworking
: for coordinating nodesvmKibanaAcceleratedNetworking
: for KibanavmLogstashAcceleratedNetworking
: for Logstash
#232 Use systemd to configure all of the Elastic Stack
systemd is now used for configuration Elasticsearch, Kibana and Logstash, and removes monit from the template; monit was introduced into the template in its infancy to work around Azure DNS availability on startup. Since that time, DNS is massively improved and systemd is capable of doing all monit is being used for, and is better known and understood.
#226 Add support for FSv2 series VMs 🖥
Compute optimized VM sizes with a high CPU-to-memory ratio
#228 Configure beats_system
built-in user when configuring Security
Allows a cluster to be future Beats ready!
Bug fixes
- #231 Fix issue where Bash special characters in inputs such as passwords would cause deployment failures.
Breaking changes
-
#229 Use resource group to get details for the Azure Repository account, and remove the Azure Storage account key and suffix parameters.
We think this will provide an easier experience; fewer and less sensitive parameters.