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-cluster-metrics-configuration-management.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,6 +66,8 @@ Specifying `--no-wait --debug` options in az cli command will result in the exec
66
66
| METRIC_TO_ENABLE_1 | Optional metric1 that have been chosen to be enabled in addition to the default metrics |
67
67
| METRIC_TO_ENABLE_2 | Optional metric2 that have been chosen to be enabled in addition to the default metrics |
68
68
69
+
Specifying `--no-wait --debug` options in az cli command will result in the execution of this command asynchronously. See [how to track asynchronous operations](howto-track-async-operations-cli.md) for more details.
70
+
69
71
## Retrieving a metrics configuration
70
72
71
73
After a metrics configuration is created, it can be retrieved using a `az rest` command:
@@ -81,9 +83,7 @@ This command will return a JSON representation of the metrics configuration.
81
83
82
84
## Updating a metrics configuration
83
85
84
-
Much like the creation of a metrics configuration, an update can be performed to change the configuration.
85
-
86
-
This command is used to patch properties of the provided metrics configuration of cluster, or update the tags assigned to the metrics configuration.
86
+
Much like the creation of a metrics configuration, an update can be performed to change the configuration or update the tags assigned to the metrics configuration.
87
87
88
88
```azurecli
89
89
az networkcloud cluster metricsconfiguration update \
0 commit comments