From 158d52c9b997451217c11d3a150da47ad5f1c4c1 Mon Sep 17 00:00:00 2001 From: dedemorton Date: Fri, 20 Jul 2018 13:23:38 -0700 Subject: [PATCH] Edit breaking changes statement about monitoring schema changes --- libbeat/docs/breaking.asciidoc | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/libbeat/docs/breaking.asciidoc b/libbeat/docs/breaking.asciidoc index b03c564164e3..7c72ee67579c 100644 --- a/libbeat/docs/breaking.asciidoc +++ b/libbeat/docs/breaking.asciidoc @@ -24,8 +24,12 @@ This section discusses the main changes that you should be aware of if you upgrade the Beats to version 6.3. {see-relnotes} [[breaking-changes-monitoring]] -=== Filebeat monitoring schema changes -Filebeat monitoring data from Filebaet version <6.3.0 could not be sent to an Elasticsearch cluster version >= 6.3.0 due to renaming of `beat.cpu.*.time metrics` to `beat.cpu.*.time.ms`. {see-relnotes} +==== Beats monitoring schema changes + +Starting with version 6.3, the monitoring field `beat.cpu.*.time.metrics` is +renamed to `beat.cpu.*.time.ms`. As a result of this change, Beats shippers +released prior to version 6.3 are unable to send monitoring data to clusters +running on Elasticsearch 6.3 and later. {see-relnotes} [[breaking-changes-mapping-conflict]] ==== New `host` namespace may cause mapping conflicts for Logstash