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
This command collects logs specific to the node, including system and cluster level diagnostics.
57
+
This command collects logs specific to the node, including system and cluster level diagnostics.
58
58
59
-
For more information on the Send-DiagnosticData command, see [Fallback log collection](disconnected-operations-fallback.md).
59
+
For more information on the Send-DiagnosticData command, see [Fallback log collection](disconnected-operations-fallback.md).
60
60
61
61
1. Upload logs using the **standalone observability tool**.
62
62
@@ -71,7 +71,7 @@ When the appliance VM is connected to Azure, upload host node logs the same way
71
71
72
72
The following diagram shows the key components for log collection in Azure Local disconnected when the appliance VM is connected to Azure:
73
73
74
-
:::image type="content" source="./media/disconnected-operations/on-demand-logs-2/on-demand-components.png" alt-text="Diagram that shows the key components for on-demand log collection in Azure Local disconnected operations." lightbox=" ./media/disconnected-operations/on-demand-logs/on-demand-components-2.png":::
74
+
:::image type="content" source="./media/disconnected-operations/on-demand-logs/on-demand-components.png" alt-text="Diagram that shows the key components for on-demand log collection in Azure Local disconnected operations." lightbox=" ./media/disconnected-operations/on-demand-logs/on-demand-components.png":::
75
75
76
76
Here's what you need to do log collection in a connected disconnected operations scenario.
0 commit comments