otel edits

Author: kgremban

articles/iot-operations/configure-observability-monitoring/howto-configure-observability.md

@@ -6,7 +6,7 @@ ms.author: kgremban
 ms.topic: how-to
 ms.custom:
   - ignite-2023
-ms.date: 02/27/2024
+ms.date: 09/26/2024
 
 # CustomerIntent: As an IT admin or operator, I want to be able to monitor and visualize data on the health of my industrial assets and edge environment.
 ---
@@ -115,6 +115,14 @@ The steps in this section install shared monitoring resources and configure your
      enabled: false
    ```
 
+1. In the `otel-collector-values.yaml` file, make a note of the following values that you'll use when you deploy Azure IoT Operations on the cluster:
+
+   * **fullnameOverride**
+   * **grpc.endpoint**
+   * **check_interval**
+
+1. Save and close the file.
+
 1. Deploy the collector by running the following commands:
 
    ```shell

articles/iot-operations/deploy-iot-ops/howto-deploy-iot-operations.md

@@ -126,8 +126,8 @@ Azure IoT Operations requires a schema registry on your cluster. Schema registry
    | --------- | ----- | ----------- |
    | `--no-progress` |  | Disables the deployment progress display in the terminal. |
    | `--enable-fault-tolerance` | `false`, `true` | Enables fault tolerance for Azure Arc Container Storage. At least 3 cluster nodes are required. |
-   | `--ops-config` | `observability.metrics.openTelemetryCollectorAddress="<FULLNAMEOVERRIDE>.azure-iot-operations.svc.cluster.local:<GRPC_ENDPOINT>` | If you followed the optional prerequisites to prepare your cluster for observability, provide the otel collector address you configured in the otel-collector-values.yaml file. The default values are **fullnameOverride=aio-otel-collector** and **grpc.enpoint=4317**. |
-   | `--ops-config` | `observability.metrics.exportInternalSeconds=<CHECK_INTERVAL>` | If you followed the optional prerequisites to prepare your cluster for observability, provide the **check_interval** value you configured in the otel-collector-values.yaml file. The default value is **check_interval=60**. |
+   | `--ops-config` | `observability.metrics.openTelemetryCollectorAddress="<FULLNAMEOVERRIDE>.azure-iot-operations.svc.cluster.local:<GRPC_ENDPOINT>` | If you followed the optional prerequisites to prepare your cluster for observability, provide the otel collector address you configured in the otel-collector-values.yaml file.<br><br>The sample values used in [Configure observability](../configure-observability-monitoring/howto-configure-observability.md) are **fullnameOverride=aio-otel-collector** and **grpc.enpoint=4317**. |
+   | `--ops-config` | `observability.metrics.exportInternalSeconds=<CHECK_INTERVAL>` | If you followed the optional prerequisites to prepare your cluster for observability, provide the **check_interval** value you configured in the otel-collector-values.yaml file.<br><br>The sample value used in [Configure observability](../configure-observability-monitoring/howto-configure-observability.md) is **check_interval=60**. |
 
 1. Deploy Azure IoT Operations. This command takes several minutes to complete: