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: articles/operator-nexus/howto-configure-cluster.md
+14-1Lines changed: 14 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -150,7 +150,7 @@ az networkcloud cluster deploy \
150
150
--name "$CLUSTER_NAME" \
151
151
--resource-group "$CLUSTER_RESOURCE_GROUP" \
152
152
--subscription "$SUBSCRIPTION_ID" \
153
-
--no-wait --debug
153
+
--no-wait --debug
154
154
```
155
155
156
156
> [!TIP]
@@ -167,6 +167,19 @@ provided through the Cluster's rack definition. Based on the results of these ch
167
167
and any user skipped machines, a determination is done on whether sufficient nodes
168
168
passed and/or are available to meet the thresholds necessary for deployment to continue.
169
169
170
+
> [!IMPORTANT]
171
+
> The hardware validation process will write the results to the specified `analyticsWorkspaceId` at Cluster Creation.
172
+
> Additionally, the provided Service Principal in the Cluster object is used for authentication against the Log Analytics Workspace Data Collection API.
173
+
> This capability is only visible during a new deployment (Green Field); existing cluster will not have the logs available retroactively.
174
+
175
+
By default, the hardware validation process writes the results to the configured Cluster `analyticsWorkspaceId`.
176
+
However, due to the nature of Log Analytics Workspace data collection and schema evaluation, there can be ingestion delay that can take several minutes or more.
177
+
For this reason, the Cluster deployment proceeds even if there was a failure to write the results to the Log Analytics Workspace.
178
+
To help address this possible event, the results, for redundancy, are also logged within the Cluster Manager.
179
+
180
+
In the provided Cluster object's Log Analytics Workspace, a new custom table with the Cluster's name as prefix and the suffix `*_CL` should appear.
181
+
In the _Logs_ section of the LAW resource, a query can be executed against the new `*_CL` Custom Log table.
182
+
170
183
#### Cluster Deploy Action with skipping specific bare-metal-machine
171
184
172
185
A parameter can be passed in to the deploy command that represents the names of
0 commit comments