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.

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

Increase priority of the 6.0 template to overwrite the 5.x settings #3657

Closed
monicasarbu opened this issue Feb 23, 2017 · 0 comments
Closed
Labels

Comments

@monicasarbu
Copy link
Contributor

monicasarbu commented Feb 23, 2017

As of #3527, Beat versioning is added in the index template by default:

beatname-%{[beat.version]}-%{+yyyy.MM.dd}

Notes:

  1. If two Beats are running of different versions (5.x and 6.0) or we upgrade from 5.x to 6.0, then there are:
    indexes: beatname-* and beatname-6.0.0-*
    beatname template that applies to all beatname-* indexes
    beatname-6.0.0 template that applies to beatname-6.0.0-* indexes.
    As a result, the beatname template applies for beatname-6.0.0-* indexes as well, so we need to set a higher priority to the beatname-6.0.0 template to overwrite the settings in 5.x.

  2. The difference between the template used after upgrading 5.x to 6.0 (master) and the template after a fresh 6.0 (master) installation is the following:

 diff metricbeat-6.0.0-alpha1-2017.02.23-without-upgrade metricbeat-6.0.0-alpha1-2017.02.23
8a9,11
>         "_all": {
>           "norms": false
>         },
4130a4134,4136
>         "_all": {
>           "norms": false
>         },
8260c8266
<         "creation_date": "1487849241372",
---
>         "creation_date": "1487848996929",
8262c8268
<         "uuid": "jYJf-6BJTLST07ZpN8TwMA",
---
>         "uuid": "tv36cO3QQKije38f_xtw_g",

Waiting for #3603 to be merged, so we can do the implementation directly in Go.

ruflin added a commit to ruflin/beats that referenced this issue Feb 24, 2017
This makes sure, in case for example a metricbeat-* and a metricbeat-{beatversion}-* template exist, the more precise one / newer one overloads the older one. This is important for people migrating from 5.x to 6.x.

Closes elastic#3657
monicasarbu pushed a commit that referenced this issue Feb 28, 2017
This makes sure, in case for example a metricbeat-* and a metricbeat-{beatversion}-* template exist, the more precise one / newer one overloads the older one. This is important for people migrating from 5.x to 6.x.

Closes #3657
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant