Merge pull request #290124 from PatAltimore/patricka-release-aio-ga

Add diagnostic probe topic known issue

Author: prmerger-automator[bot]

articles/iot-operations/manage-mqtt-broker/howto-broker-diagnostics.md

@@ -6,7 +6,7 @@ ms.author: patricka
 ms.topic: how-to
 ms.service: azure-iot-operations
 ms.subservice: azure-mqtt-broker
-ms.date: 11/04/2024
+ms.date: 11/07/2024
 
 #CustomerIntent: As an operator, I want to configure diagnostics so that I can monitor MQTT broker communications.
 ---
@@ -62,6 +62,8 @@ Then, deploy Azure IoT Operations using the `az iot ops create` command with the
 az iot ops create ... --broker-config-file <FILE>.json
 ```
 
+The self-test diagnostics probe publishes messages to the `azedge/dmqtt/selftest` topic. You shouldn't publish or subscribe to this topic as it's used for internal diagnostics. For more information, see [Known Issues](../troubleshoot/known-issues.md#mqtt-broker).
+
 To learn more, see [Azure CLI support for advanced MQTT broker configuration](https://aka.ms/aziotops-broker-config) and [Broker examples](/rest/api/iotoperations/broker/create-or-update#examples).
 
 ## Next steps

articles/iot-operations/troubleshoot/known-issues.md

@@ -6,7 +6,7 @@ ms.author: dobett
 ms.topic: troubleshooting-known-issue
 ms.custom:
   - ignite-2023
-ms.date: 10/22/2024
+ms.date: 11/07/2024
 ---
 
 # Known issues: Azure IoT Operations
@@ -31,6 +31,8 @@ This article lists the known issues for Azure IoT Operations.
 
 - Deployment might fail if the **cardinality** and **memory profile** values are set to be too large for the cluster. To resolve this issue, set the replicas count to `1` and use a smaller memory profile, like `low`.
 
+- Don't publish or subscribe to diagnostic probe topics that start with `azedge/dmqtt/selftest`. Publishing or subscribing to these topics might affect the probe or self-test checks resulting in invalid results. Invalid results might be listed in diagnostic probe logs, metrics, or dashboards. For example, you might see the issue *Path verification failed for probe event with operation type 'Publish'* in the diagnostics-probe logs.
+
 ## Azure IoT Layered Network Management (preview)
 
 - If the Layered Network Management service doesn't get an IP address while running K3S on Ubuntu host, reinstall K3S without _trafeik ingress controller_ by using the `--disable=traefik` option.