@@ -22,6 +22,43 @@ Have a question? Read our <<fleet-faq,FAQ>>, or contact us in the
22
22
23
23
Running {agent} standalone? Also refer to <<debug-standalone-agents>>.
24
24
25
+
26
+ [discrete]
27
+ [[troubleshooting-contents]]
28
+ == Troubleshooting contents
29
+
30
+ Find troubleshooting information for {fleet}, {fleet-server}, and {agent} in the following documentation:
31
+
32
+ * <<tsdb-illegal-argument>>
33
+ * <<agents-in-cloud-stuck-at-updating>>
34
+ * <<fleet-server-not-in-kibana-cloud>>
35
+ * <<fleet-setup-fails>>
36
+ * <<fleet-errors-tls>>
37
+ * <<fleet-app-crashes>>
38
+ * <<agent-enrollment-certs>>
39
+ * <<es-enrollment-certs>>
40
+ * <<agent-enrollment-timeout>>
41
+ * <<general-fleet-server-triage>>
42
+ * <<trb-retrieve-agent-version>>
43
+ * <<trb-check-agent-status>>
44
+ * <<trb-collect-agent-diagnostics>>
45
+ * <<not-installing-no-logs-in-terminal>>
46
+ * <<agent-healthy-but-no-data-in-es>>
47
+ * <<fleet-agent-stuck-on-updating>>
48
+ * <<secondary-agent-not-connecting>>
49
+ * <<es-apikey-failed>>
50
+ * <<process-not-root>>
51
+ * <<upgrading-integration-too-many-conflicts>>
52
+ * <<agent-hangs-while-unenrolling>>
53
+ * <<ca-cert-testing>>
54
+ * <<endpoint-not-uninstalled-with-agent>>
55
+ * <<endpoint-unauthorized>>
56
+ * <<hosted-agent-offline>>
57
+ * <<hosted-agent-8-x-upgrade-fail>>
58
+ * <<pgp-key-download-fail>>
59
+ * <<fleet-server-integration-removed>>
60
+ * <<agent-oom-k8s>>
61
+
25
62
[discrete]
26
63
[[tsdb-illegal-argument]]
27
64
== illegal_argument_exception when TSDB is enabled
@@ -264,6 +301,7 @@ to {kib} in prior releases. However, because {fleet-server} is on the edge host,
264
301
result in additional networking setup and troubleshooting.
265
302
266
303
[discrete]
304
+ [[trb-retrieve-agent-version]]
267
305
=== Retrieve the {agent} version
268
306
269
307
. If you installed the {agent}, run the following command (the example is for POSIX
@@ -286,6 +324,7 @@ how you call them. If needed, please refer to <<elastic-agent-installation>>
286
324
for examples of how to adjust them.
287
325
288
326
[discrete]
327
+ [[trb-check-agent-status]]
289
328
=== Check the {agent} status
290
329
291
330
Run the following command to view the current status of the {agent}.
@@ -312,6 +351,7 @@ IMPORTANT: The *{ecloud} agent policy* is created only in {ecloud} deployments a
312
351
does not include the collection of logs of metrics.
313
352
314
353
[discrete]
354
+ [[trb-collect-agent-diagnostics]]
315
355
=== Collect {agent} diagnostics bundle
316
356
317
357
The {agent} diagnostics bundle collects the following information:
0 commit comments