You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of #3527, Beat versioning is added in the index template by default:
beatname-%{[beat.version]}-%{+yyyy.MM.dd}
Notes:
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.
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:
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.
Closeselastic#3657
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
As of #3527, Beat versioning is added in the index template by default:
Notes:
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-*
andbeatname-6.0.0-*
beatname
template that applies to allbeatname-*
indexesbeatname-6.0.0
template that applies tobeatname-6.0.0-*
indexes.As a result, the
beatname
template applies forbeatname-6.0.0-*
indexes as well, so we need to set a higher priority to thebeatname-6.0.0
template to overwrite the settings in 5.x.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:
Waiting for #3603 to be merged, so we can do the implementation directly in Go.
The text was updated successfully, but these errors were encountered: