Introduce beat version in index and template #3527
Merged
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
ruflin
added
discuss
ruflin
force-pushed
the
index-versioninig
branch
from
ee9787d
to
270de78
Compare
ruflin
force-pushed
the
index-versioninig
branch
from
270de78
to
66eb9ac
Compare
ruflin
force-pushed
the
index-versioninig
branch
3 times, most recently
from
b9b3e43
to
20f5f1f
Compare
ruflin
added
review
and removed
discuss
This adds the beat version to the index and the template. The advantage of this is that an index always has the correct template applied based on the beats version. Currently during upgrade it must be waited until the next day. Only then the new template is applied. Also it helps in case different versions of beats are running in parallel. Each beat puts its data into the correct index.
The index name is now `beatname-%{[beat.version]}-%{+yyyy.MM.dd}` by default.
This should not have any affects on the dashboards or Kibana in general as `beatname-*` still applies to all data. Are there some potential side affects of this?
ruflin
force-pushed
the
index-versioninig
branch
from
20f5f1f
to
32fcdce
Compare
urso
approved these changes
Feb 20, 2017
This was referenced Feb 23, 2017
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.
This adds the beat version to the index and the template. The advantage of this is that an index always has the correct template applied based on the beats version. Currently during upgrade it must be waited until the next day. Only then the new template is applied. Also it helps in case different versions of beats are running in parallel. Each beat puts its data into the correct index.
The index name is now
beatname-%{[beat.version]}-%{+yyyy.MM.dd}by default.This should not have any affects on the dashboards or Kibana in general as
beatname-*still applies to all data. Are there some potential side affects of this?