Skip to content

Commit

Permalink
Document breaking change in monitoring shcema
Browse files Browse the repository at this point in the history 
Situation:
  • Loading branch information
Dmytro Ilchenko committed Jul 20, 2018
1 parent 412850b commit a44f804
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions libbeat/docs/breaking.asciidoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down

1 comment on commit a44f804

@dilchenko
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, I meant to document the commit, but instead clicked Ctrl+Enter and GH committed the thing.

Situation:
2 x 6.3.1 clusters, sending ES monitoring data to another 6.3.1 cluster. Filebeat version 6.2.1 sending data to another 6.2.3 ES cluster. We decide to send filebeat monitoring data to the same monitoring 6.3.1 cluster, it fails like https://discuss.elastic.co/t/no-xpack-monitoring-for-metricbeat/136573 which is due to #6449. We cannot downgrade the monitoring cluster, because then the monitoring data from 2 x 6.3.1 will fail, and because cloud does not support downgrades. So simply to send monitoring data to another cluster, we are forced to upgrade Filebeat across the whole infrastructure.

This is very much a breaking change!

Please sign in to comment.