You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/iot-operations/manage-mqtt-broker/howto-broker-persistence.md
+19-17Lines changed: 19 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -78,7 +78,7 @@ To configure volume settings using Azure CLI, prepare a Broker configuration fil
78
78
}
79
79
```
80
80
81
-
Then run the [az iot ops create](/cli/azure/iot/ops?view=azure-cli-latest#az-iot-ops-create) command with the `--broker-config-file` flag to deploy IoT Operations:
81
+
Then run the [az iot ops create](/cli/azure/iot/ops#az-iot-ops-create) command with the `--broker-config-file` flag to deploy IoT Operations:
@@ -269,15 +271,15 @@ This setting controls which keys in the internal state store are persisted.
269
271
270
272
# [Azure portal](#tab/portal)
271
273
272
-
:::image type="content" source="media/howto-broker-persistence/data-persistence-state-store.png" alt-text="[Screenshot changing data persistence state store options the Azure portal]":::
273
274
274
275
To configure state store persistence in the Azure portal:
275
276
276
277
1. Navigate to your IoT Operations instance.
277
278
2. Go to **MQTT Broker** > **Data Persistence**.
278
279
3. In the **State Store** section:
279
-
- Select the **Mode**: None, All, or Custom.
280
-
- If Custom is selected, specify state store resources with key types, keys, and dynamic mode settings.
280
+
- Select the **Mode**: None, All, or Custom.
281
+
- If Custom is selected, specify state store resources with key types, keys, and dynamic mode settings.
282
+
:::image type="content" source="media/howto-broker-persistence/data-persistence-state-store.png" alt-text="[Screenshot changing data persistence state store options the Azure portal]":::
281
283
282
284
# [Azure CLI](#tab/azurecli)
283
285
@@ -305,17 +307,18 @@ You can enable or disable the dynamic persistence setting for each data type (re
305
307
306
308
# [Azure portal](#tab/portal)
307
309
308
-
:::image type="content" source="media/howto-broker-persistence/data-persistence-dynamic.png" alt-text="[Screenshot changing data persistence subscriber options the Azure portal]":::
309
310
310
311
To configure dynamic persistence settings in the Azure portal:
311
312
312
313
1. Navigate to your IoT Operations instance.
313
314
2. Go to **MQTT Broker** > **Data Persistence**.
314
315
3. Configure the global MQTT user property settings:
315
-
- Set the **User property key** (default: `aio-persistence`)
316
-
- Set the **User property value** (default: `true`)
316
+
- Set the **User property key** (default: `aio-persistence`)
317
+
- Set the **User property value** (default: `true`)
317
318
4. In each persistence section (Retained Messages, Subscriber Queue, State Store):
318
-
- Set **Dynamic persistence** to enabled to allow clients to request persistence for that data type.
319
+
- Set **Dynamic persistence** to enabled to allow clients to request persistence for that data type.
320
+
321
+
:::image type="content" source="media/howto-broker-persistence/data-persistence-dynamic.png" alt-text="[Screenshot changing data persistence dynamic options the Azure portal]":::
319
322
320
323
# [Azure CLI](#tab/azurecli)
321
324
@@ -331,7 +334,6 @@ Here's an example command Configure subscriber queue persistence for specific cl
331
334
az iot ops broker persist update --resource-group myResourceGroup --instance myAioInstance --name myBroker --persist-mode subscriberQueue=Custom --subscriber-client-ids "factory-client-*" "sensor-gateway-01"--user-key disk-persistence --user-value disk
332
335
```
333
336
334
-
---
337
+
---
335
338
336
339
To learn more about Azure CLI support for advanced MQTT broker configuration, see [Azure CLI support for advanced MQTT broker configuration](https://aka.ms/aziotops-broker-config).
0 commit comments