Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Forward port to master: Monitoring breaking changes plus #7666 #7669

Merged
merged 2 commits into from
Jul 21, 2018
Merged

Forward port to master: Monitoring breaking changes plus #7666 #7669

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7d829eb
Document breaking change in monitoring shcema
Jul 20, 2018
86271e4
Edit breaking changes statement about monitoring schema changes (#7666)
dedemorton Jul 20, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Document breaking change in monitoring shcema 
Situation:
  • Loading branch information
@dedemorton
Dmytro Ilchenko authored and dedemorton committed Jul 21, 2018
commit 7d829eb6ea0e8dfcfd6f48a887c12d3446cdfa9c
4 changes: 4 additions & 0 deletions libbeat/docs/breaking.asciidoc
View file
Open in desktop
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