Skip to content

Commit 857ff4b

Browse files
Merge pull request #298010 from bishal41/X509-WebUI
Remove X.509 web UI issue from known issue page
2 parents b66a58c + 1867df1 commit 857ff4b

File tree

2 files changed

+1
-18
lines changed

2 files changed

+1
-18
lines changed

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

Lines changed: 0 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -357,23 +357,6 @@ Log signature: N/A
357357
358358
When you create a data flow, you can specify a schema in the source configuration. However, deserializing and validating messages using a schema isn't supported yet. Specifying a schema in the source configuration only allows the operations experience to display the list of data points, but the data points aren't validated against the schema.
359359
360-
### X.509 secret incorrectly encoded in operations experience web UI
361-
362-
---
363-
364-
Issue ID: 8841
365-
366-
---
367-
368-
Log signature: N/A
369-
370-
---
371-
372-
<!-- TODO: double check -->
373-
When you create an X.509 secret in the operations experience, the secret is created with incorrectly encoded data.
374-
375-
To work around this issue, create the [multi-line secrets through Azure Key Vault](/azure/key-vault/secrets/multiline-secrets), then select it from the list of secrets in the operations experience.
376-
377360
### Connection failures with Azure Event Grid
378361
379362
---

articles/iot-operations/troubleshoot/troubleshoot.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ A deployment can fail if the cluster doesn't have sufficient resources for the s
6868
> Setting the replica count to one can result in data loss in node failure scenarios.
6969
7070
> [!TIP]
71-
> Setting lower sharding, workers, or memory profile values lowers the broker's capacity to handle message load. Before you deploy to production, test your scenario with the MQTT broker configuration, to ensure the broker is can handle the maximum expected load.
71+
> Setting lower sharding, workers, or memory profile values lowers the broker's capacity to handle message load. Before you deploy to production, test your scenario with the MQTT broker configuration, to ensure the broker can handle the maximum expected load.
7272
7373
To learn more about how to choose suitable values for these parameters, see [Configure broker settings for high availability, scaling, and memory usage](../manage-mqtt-broker/howto-configure-availability-scale.md).
7474

0 commit comments

Comments
 (0)