Cherry-pick #11315 to 7.0: Update schema version in monitoring index name #11320
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Update schema version in monitoring index name * Update tests (cherry picked from commit 55aba20)
ycombinator
requested review from
ph,
jakelandis and
a team
and removed request for
ph
cachedout
reviewed
Mar 20, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #11315 to 7.0 branch. Original message:
Starting 7.0, Metricbeat Stack Monitoring modules should index data into
.monitoring-7-*indices instead of.monitoring-6-*. This PR makes this change.Testing this PR
mage buildin themetricbeatfolder): https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-metricbeat.html.monitoring-7-*indices are being created in Elasticsearch, not.monitoring-6-*indices.