Skip to content

Commit ec289ab

Browse files
Merge pull request #298127 from bishal41/probe-path
Remove probe path issue from known issue page
2 parents 14e12a9 + d108462 commit ec289ab

File tree

1 file changed

+0
-16
lines changed

1 file changed

+0
-16
lines changed

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

Lines changed: 0 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -127,22 +127,6 @@ MQTT broker resources created in your cluster using Kubernetes aren't visible in
127127

128128
There's currently no workaround for this issue.
129129
130-
### Probe event errors
131-
132-
---
133-
134-
Issue ID: 1567
135-
136-
---
137-
138-
Log signature: `"Path verification failed for probe event with operation type 'Publish'"`
139-
140-
---
141-
142-
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 message `Path verification failed for probe event with operation type 'Publish'` in the diagnostics-probe logs.
143-
144-
There's currently no workaround for this issue.
145-
146130
## Azure IoT Layered Network Management (preview) issues
147131
148132
This section lists current known issues for Azure IoT Layered Network Management.

0 commit comments

Comments
 (0)