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-baremetal-run-read.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,8 +83,8 @@ For a command with multiple arguments, provide as a list to `arguments` paramete
83
83
84
84
These commands can be long running so the recommendation is to set `--limit-time-seconds` to at least 600 seconds (10 minutes). Running multiple extracts might take longer that 10 minutes.
85
85
86
-
This command runs synchronously. If you wish to skip waiting for the command to complete, specify the `--no-wait --debug` options. See [how to track asynchronous operations](howto-track-async-operations-cli.md) for more details.
87
-
86
+
This command runs synchronously. If you wish to skip waiting for the command to complete, specify the `--no-wait --debug` options. For more information, see [how to track asynchronous operations](howto-track-async-operations-cli.md).
Copy file name to clipboardExpand all lines: articles/operator-nexus/howto-cluster-metrics-configuration-management.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ az networkcloud cluster metricsconfiguration create \
48
48
> * The default metrics collection interval for standard set of metrics is set to every 5 minutes. Changing the `collectionInterval` will also impact the collection frequency for default standard metrics.
49
49
> * There can be only one set of metrics configuration defined per cluster. The resource is created with the name `default`.
50
50
51
-
Specifying `--no-wait --debug` options in az cli command results in the execution of this command asynchronously. See [how to track asynchronous operations](howto-track-async-operations-cli.md) for more details.
51
+
Specifying `--no-wait --debug` options in az cli command results in the execution of this command asynchronously. For more information, see [how to track asynchronous operations](howto-track-async-operations-cli.md).
52
52
53
53
### Metrics Configuration elements
54
54
@@ -66,7 +66,7 @@ Specifying `--no-wait --debug` options in az cli command results in the executio
66
66
| METRIC_TO_ENABLE_1 | Optional metric1 that is enabled in addition to the default metrics |
67
67
| METRIC_TO_ENABLE_2 | Optional metric2 that is enabled in addition to the default metrics |
68
68
69
-
Specifying `--no-wait --debug` options in az cli command results in the execution of this command asynchronously. See [how to track asynchronous operations](howto-track-async-operations-cli.md) for more details.
69
+
Specifying `--no-wait --debug` options in az cli command results in the execution of this command asynchronously. For more information, see [how to track asynchronous operations](howto-track-async-operations-cli.md).
70
70
71
71
## Retrieving a metrics configuration
72
72
@@ -96,7 +96,7 @@ az networkcloud cluster metricsconfiguration update \
96
96
97
97
The `collection-interval` can be updated independently of `enabled-metrics` list. Omit fields that aren't being changed.
98
98
99
-
Specifying `--no-wait --debug` options in az cli command results in the execution of this command asynchronously. See [how to track asynchronous operations](howto-track-async-operations-cli.md) for more details.
99
+
Specifying `--no-wait --debug` options in az cli command results in the execution of this command asynchronously. For more information, see [how to track asynchronous operations](howto-track-async-operations-cli.md).
100
100
101
101
## Deleting a metrics configuration
102
102
@@ -108,6 +108,6 @@ az networkcloud cluster metricsconfiguration delete \
108
108
--resource-group "<RESOURCE_GROUP>"
109
109
```
110
110
111
-
Specifying `--no-wait --debug` options in az cli command results in the execution of this command asynchronously. See [how to track asynchronous operations](howto-track-async-operations-cli.md) for more details.
111
+
Specifying `--no-wait --debug` options in az cli command results in the execution of this command asynchronously. For more information, see [how to track asynchronous operations](howto-track-async-operations-cli.md).
Copy file name to clipboardExpand all lines: articles/operator-nexus/howto-configure-cluster.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -155,7 +155,7 @@ az networkcloud cluster deploy \
155
155
--no-wait --debug
156
156
```
157
157
158
-
This command runs synchronously. If you wish to skip waiting for the command to complete, specify the `--no-wait --debug` options. See [how to track asynchronous operations](howto-track-async-operations-cli.md) for more details.
158
+
This command runs synchronously. If you wish to skip waiting for the command to complete, specify the `--no-wait --debug` options. For more information, see [how to track asynchronous operations](howto-track-async-operations-cli.md).
0 commit comments