Merge pull request #194105 from kgremban/apr5-opsmon

Retire operations monitoring topics

Author: laurabren

.openpublishing.redirection.iot-hub.json

@@ -1088,6 +1088,16 @@
       "redirect_url": "/azure/iot-hub/iot-hub-device-management-iot-toolkit",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/iot-hub/iot-hub-operations-monitoring.md",
+      "redirect_url": "/azure/iot-hub/monitor-iot-hub",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/iot-hub/iot-hub-migrate-to-diagnostics-settings.md",
+      "redirect_url": "/azure/iot-hub/monitor-iot-hub",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/iot-hub/iot-hub-protocol-gateway.md",
       "redirect_url": "/azure/iot-edge/iot-edge-as-gateway",

articles/iot-hub/TOC.yml

@@ -435,10 +435,6 @@
       href: ./policy-reference.md
     - name: Feature and API retirement
       items:
-        - name: Operations monitoring
-          href: iot-hub-operations-monitoring.md
-        - name: Migrate to Azure Monitor
-          href: iot-hub-migrate-to-diagnostics-settings.md
         - name: TLS 1.0 and 1.1 deprecation
           href: iot-hub-tls-deprecating-1-0-and-1-1.md
         - name: Classic IP filter

articles/iot-hub/iot-hub-create-through-portal.md

@@ -28,8 +28,6 @@ You can change the settings of an existing IoT hub after it's created from the I
 
 **Pricing and scale**: You can use this property to migrate to a different tier or set the number of IoT Hub units. 
 
-**Operations monitoring**: Turn the different monitoring categories on or off, such as logging for events related to device-to-cloud messages or cloud-to-device messages.
-
 **IP Filter**: Specify a range of IP addresses that will be accepted or rejected by the IoT hub.
 
 **Properties**: Provides the list of properties that you can copy and use elsewhere, such as the resource ID, resource group, location, and so on.

articles/iot-hub/iot-hub-devguide-endpoints.md

@@ -58,8 +58,6 @@ The following list describes the endpoints:
   * *Receive file notifications*. This messaging endpoint allows you to receive notifications of when your devices successfully upload a file. 
 
   * *Direct method invocation*. This endpoint allows a back-end service to invoke a [direct method](iot-hub-devguide-direct-methods.md) on a device.
-  
-  * *Receive operations monitoring events*. This endpoint allows you to receive operations monitoring events if your IoT hub has been configured to emit them. For more information, see [IoT Hub operations monitoring](iot-hub-operations-monitoring.md).
 
 The [Azure IoT SDKs](iot-hub-devguide-sdks.md) article describes the various ways to access these endpoints.
 

articles/iot-hub/iot-hub-ha-dr.md

@@ -61,7 +61,6 @@ Both these failover options offer the following recovery point objectives (RPOs)
 | Cloud-to-device messages<sup>1</sup> |0-5 mins data loss |
 | Parent<sup>1</sup> and device jobs |0-5 mins data loss |
 | Device-to-cloud messages |All unread messages are lost |
-| Operations monitoring messages |All unread messages are lost |
 | Cloud-to-device feedback messages |All unread messages are lost |
 
 <sup>1</sup>Cloud-to-device messages and parent jobs do not get recovered as a part of manual failover.

articles/iot-hub/iot-hub-migrate-to-diagnostics-settings.md

@@ -140,7 +140,7 @@ If a device cannot use the device SDKs, it can still connect to the public devic
     `contoso.azure-devices.net/MyDevice01/?api-version=2021-04-12`
 
     It's strongly recommended to include api-version in the field. Otherwise it could cause unexpected behaviors. 
-    
+
 * For the **Password** field, use a SAS token. The format of the SAS token is the same as for both the HTTPS and AMQP protocols:
 
   `SharedAccessSignature sig={signature-string}&se={expiry}&sr={URL-encoded-resourceURI}`
@@ -170,8 +170,6 @@ If a device cannot use the device SDKs, it can still connect to the public devic
 
    `SharedAccessSignature sr={your hub name}.azure-devices.net%2Fdevices%2FMyDevice01%2Fapi-version%3D2016-11-14&sig=vSgHBMUG.....Ntg%3d&se=1456481802`
 
-For MQTT connect and disconnect packets, IoT Hub issues an event on the **Operations Monitoring** channel. This event has additional information that can help you to troubleshoot connectivity issues.
-
 The device app can specify a **Will** message in the **CONNECT** packet. The device app should use `devices/{device_id}/messages/events/` or `devices/{device_id}/messages/events/{property_bag}` as the **Will** topic name to define **Will** messages to be forwarded as a telemetry message. In this case, if the network connection is closed, but a **DISCONNECT** packet was not previously received from the device, then IoT Hub sends the **Will** message supplied in the **CONNECT** packet to the telemetry channel. The telemetry channel can be either the default **Events** endpoint or a custom endpoint defined by IoT Hub routing. The message has the **iothub-MessageType** property with a value of **Will** assigned to it.
 
 ## Using the MQTT protocol directly (as a module)