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
Copy file name to clipboardexpand all lines: docs/api/upgrade-assistant/status.asciidoc
+1-15
Original file line number
Diff line number
Diff line change
@@ -31,22 +31,8 @@ The API returns the following:
31
31
"cluster": [
32
32
{
33
33
"message": "Cluster deprecated issue",
34
-
"details": "...",
35
-
"level": "warning",
36
-
"url": "https://docs.elastic.co/..."
37
-
}
38
-
],
39
-
"indices": [
40
-
{
41
-
"message": "Index was created before 6.0",
42
-
"details": "...",
43
-
"index": "myIndex",
44
-
"level": "critical",
45
-
"reindex": true, <1>
46
-
"url": "https://docs.elastic.co/..."
34
+
"details":"You have 2 system indices that must be migrated and 5 Elasticsearch deprecation issues and 0 Kibana deprecation issues that must be resolved before upgrading."
Copy file name to clipboardexpand all lines: docs/osquery/osquery.asciidoc
+1-1
Original file line number
Diff line number
Diff line change
@@ -112,7 +112,7 @@ or <<osquery-map-fields,map ECS fields>>. When you add a saved query to a pack,
112
112
. Click a pack name to view the status.
113
113
+
114
114
Details include the last time each query ran, how many results were returned, and the number of agents the query ran against.
115
-
If there are errors, expand the row to view the details.
115
+
If there are errors, expand the row to view the details, including an option to view more information in the Logs.
116
116
+
117
117
[role="screenshot"]
118
118
image::images/scheduled-pack.png[Shows queries in the pack and details about each query, including the last time it ran, how many results were returned, the number of agents it ran against, and if there are errors]
Copy file name to clipboardexpand all lines: docs/setup/upgrade/resolving-migration-failures.asciidoc
+8-8
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ Migrating {kib} primarily involves migrating saved object documents to be compat
5
5
with the new version.
6
6
7
7
[float]
8
-
==== Resolve saved object migration failures
8
+
==== Saved object migration failures
9
9
10
10
If {kib} unexpectedly terminates while migrating a saved object index, {kib} automatically attempts to
11
11
perform the migration again when the process restarts. Do not delete any saved objects indices to
@@ -21,14 +21,14 @@ If you're unable to resolve a failed migration, contact Support.
21
21
22
22
[float]
23
23
[[upgrade-migrations-old-indices]]
24
-
==== Handle old `.kibana_N` indices
24
+
==== Old `.kibana_N` indices
25
25
26
26
After the migrations complete, multiple {kib} indices are created in {es}: (`.kibana_1`, `.kibana_2`, `.kibana_7.12.0` etc).
27
27
{kib} only uses the index that the `.kibana` and `.kibana_task_manager` aliases point to.
28
28
The other {kib} indices can be safely deleted, but are left around as a matter of historical record, and to facilitate rolling {kib} back to a previous version.
29
29
30
30
[float]
31
-
==== Handle known issues with {fleet} beta
31
+
==== Known issues with {fleet} beta
32
32
If you see a`timeout_exception` or `receive_timeout_transport_exception` error,
33
33
it might be from a known known issue in 7.12.0 if you tried the {fleet} beta.
34
34
Upgrade migrations fail because of a large number of documents in the `.kibana` index,
@@ -45,7 +45,7 @@ For instructions on how to mitigate the known issue, refer to https://github.com
45
45
46
46
47
47
[float]
48
-
==== Handle corrupt saved objects
48
+
==== Corrupt saved objects
49
49
To find and remedy problems caused by corrupt documents, we highly recommend testing your {kib} upgrade in a development cluster,
50
50
especially when there are custom integrations that create saved objects in your environment.
51
51
@@ -87,13 +87,13 @@ The dashboard with the `e3c5fc71-ac71-4805-bcab-2bcc9cc93275` ID that belongs to
87
87
88
88
[float]
89
89
[[unknown-saved-object-types]]
90
-
==== Handle documents for unknown saved objects
90
+
==== Documents for unknown saved objects
91
91
Migrations will fail if saved objects belong to an unknown
92
92
saved object type. Unknown saved objects are typically caused by
93
93
to the {es} index, or by disabling a plugin that had previously
94
94
created a saved object.
95
95
96
-
We recommend using the {kibana-ref-all}/7.17/upgrade-assistant.html[Upgrade Assistant]
96
+
We recommend using the {kibana-ref-all}/7.17/upgrade-assistant.html[Upgrade Assistant]
97
97
to discover and remedy any unknown saved object types. {kib} version 7.17.0 deployments containing unknown saved
98
98
object types will also log the following warning message:
99
99
@@ -110,15 +110,15 @@ Unable to complete saved object migrations for the [.kibana] index: Migration fa
110
110
--------------------------------------------
111
111
112
112
[float]
113
-
==== Handle incompatible settings or mappings
113
+
==== Incompatible settings or mappings
114
114
Matching index templates that specify `settings.refresh_interval` or
115
115
`mappings` are known to interfere with {kib} upgrades.
116
116
This can happen when index templates are defined manually.
117
117
118
118
To make sure the index templates won't apply to new `.kibana*` indices, narrow down the {data-sources} of any user-defined index templates.
0 commit comments