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: asciidoc/troubleshooting/collecting-diagnostics-for-support.adoc
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,8 @@ ifdef::env-github[]
13
13
:warning-caption: :warning:
14
14
endif::[]
15
15
16
+
include::../edge-book/versions.adoc[]
17
+
16
18
When contacting SUSE Support, providing comprehensive diagnostic information is crucial.
17
19
18
20
.Essential Information to Collect
@@ -42,11 +44,11 @@ When contacting SUSE Support, providing comprehensive diagnostic information is
42
44
* *For SL Micro*: Check the https://documentation.suse.com/sle-micro/5.5/html/SLE-Micro-all/cha-adm-support-slemicro.html[SUSE Linux Micro Troubleshooting Guide] documentation on how to gather system information for support with `supportconfig`.
43
45
* *For RKE2/Rancher*: Check the https://www.suse.com/support/kb/doc/?id=000020191[The Rancher v2.x Linux log collector script] article to run The Rancher v2.x Linux log collector script.
44
46
45
-
* *For Edge (Nessie)*: Nessie is a powerful diagnostic tool designed to collect logs and configuration data from SUSE Edge environments. It gathers comprehensive information from both the host system and Kubernetes clusters, making it invaluable for troubleshooting and support.
47
+
* *For Edge (Nessie)*: Nessie {version-nessie}is a powerful diagnostic tool designed to collect logs and configuration data from SUSE Edge environments. It gathers comprehensive information from both the host system and Kubernetes clusters, making it invaluable for troubleshooting and support.
46
48
** Nessie has two "modes" a kubernetes mode and a system mode.
47
49
*** To collect logs from a SUSE Edge cluster, run (provided that you have access to the kubeconfig file locally):
0 commit comments