From f4b47b0028357ce14b1fec3cc0934e0e69c5c787 Mon Sep 17 00:00:00 2001 From: Dmytro Ilchenko Date: Fri, 20 Jul 2018 15:42:47 -0400 Subject: [PATCH] Document breaking change in monitoring shcema Situation: --- libbeat/docs/breaking.asciidoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/libbeat/docs/breaking.asciidoc b/libbeat/docs/breaking.asciidoc index 7b9f5030c7c..b03c564164e 100644 --- a/libbeat/docs/breaking.asciidoc +++ b/libbeat/docs/breaking.asciidoc @@ -23,6 +23,10 @@ See the following topics for a description of breaking changes: 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} + [[breaking-changes-mapping-conflict]] ==== New `host` namespace may cause mapping conflicts for Logstash