Skip to content
This repository has been archived by the owner on Mar 30, 2023. It is now read-only.

7.0.0
Compare
Choose a tag to compare
@russcam russcam released this 02 May 23:06
· 97 commits to master since this release
7.0.0
246b907

Elasticsearch, Kibana and Logstash 7.0.0

This release adds support for deploying Elasticsearch Kibana and Logstash 7.0.0 to Azure!

Features

#275 Add Elastic Stack 7.0.0 🥇

This release adds Elastic Stack 7.0.0 to the template, with 7.0.0 now the default version. 7.0.0 comes with a heap of new features, including:

New Kibana design and navigation

The most prominent change is a switch to a new global navigation, which introduces a constant header to switch Kibana spaces, display breadcrumbs, and initiate user actions like change password or logout.

elastic_stack_700

Zen2 Cluster Coordination

Zen2 is a completely new cluster coordination layer for Elasticsearch, which is faster, safer, and easier to use. If you're interested in more details, the Zen2 blog post is a great read! The ARM template handles configuring zen2 for Elastic Stack 7.0.0 in addition to still configuring the original zen coordination layer for older versions.

Nanosecond precision

A migration from Joda-Time to the official Java time API in JDK 8 within the core of Elasticsearch, now provides better precision to accurately store and sequence data, useful in cases where data is collected at high frequencies.

plus many more. Check out the release blog post for more details..

#275 Set up passwords for apm_system and remote_monitoring_user built-in user accounts

As the Stack grows, so has the built-in user accounts used by Stack components. In addition to configuring passwords for elastic, kibana, logstash_system and beats_system built-in user accounts, the ARM template will allows you to set passwords for apm_system and remote_monitoring_user built-in user accounts. apm_system is used by the APM server to send APM data to Elasticsearch, and remote_monitoring_user is used by MetricBeat to send data.

Breaking Changes

#275 Remove es_read user account

Since the initial template deployment, an es_read user account has been configured as part of the deployment. The value of configuring this account on deployment has diminished over time, given how easy it is to configure users as a post-deployment step, using either the API or Users view in Kibana. For this reason, and to make way for apm_system and remote_monitoring_user built-in user account configuration, this account is no longer configured. If you'd like to add it as a post-deployment step, the following curl requests against the cluster will do so

# create the user role
curl -XPOST "<base uri>/_security/role/user" -u "elastic:<elastic superuser password>" -H 'Content-Type: application/json' -d'
{
    "cluster": ["monitor"],
    "indices": [{
        "names": ["*"],
        "privileges": ["read", "monitor", "view_index_metadata"]
    }]
}'

# create the es_read user
curl -XPOST "<base uri>/_security/user/es_read" -u "elastic:<elastic superuser password>" -H 'Content-Type: application/json' -d'
{
    "password":"<password for es_read>",
    "roles":["user"]
}'
Assets 2
Loading