[heartbeat][docs] Add note about ensuring correct index settings for …

…uptime (elastic#31146) * [heartbeat][docs] Add note about ensuring correct index settings for uptime Goes hand in hand with elastic/kibana#129312 . Currently, when upgrading the stack, users who have a settings saved object will not see new heartbeat data in typical situations due to their index pattern being stuck on `heartbeat-7*`. * Update upgrading.asciidoc * Update libbeat/docs/upgrading.asciidoc Co-authored-by: Lucas F. da Costa <[email protected]> * Update libbeat/docs/upgrading.asciidoc Co-authored-by: DeDe Morton <[email protected]> Co-authored-by: Lucas F. da Costa <[email protected]> Co-authored-by: DeDe Morton <[email protected]>
kush-elastic · May 2, 2022 · 7ad56bd · 7ad56bd
1 parent 2f5a282
commit 7ad56bd
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/libbeat/docs/upgrading.asciidoc b/libbeat/docs/upgrading.asciidoc
@@ -37,6 +37,9 @@ We recommend that you fully upgrade {es} and {kib} to version 8.0
 before upgrading {beats}. The {beats} version must be lower than or equal to the
 {es} version. {beats} cannot send data to older versions of {es}.
 
+If you use the Uptime app in {kib}, make sure you add `heartbeat-8*` and `synthetics-*` to *Uptime indices*
+on the {observability-guide}/configure-uptime-settings.html[Settings page]. The first index is used by newer versions of {beatname_uc}, while the latter is used by {fleet}.
+
 If you're on {beats} 7.0 through 7.16, upgrade the {stack} and {beats} to
 version 7.17 *before* proceeding with the 8.0 upgrade.