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
To learn how to manage data export by using the IoT Central REST API, see [How to use the IoT Central REST API to manage data exports.](../core/howto-manage-data-export-with-rest-api.md)
19
+
To learn how to manage data export by using the IoT Central REST API, see [How to use the IoT Central REST API to manage data exports.](../core/howto-manage-data-export-with-rest-api.md).
20
20
21
21
## Set up a Blob Storage export destination
22
22
@@ -96,7 +96,7 @@ To create the Blob Storage destination in IoT Central on the **Data export** pag
96
96
97
97
1. Select **Save**.
98
98
99
-
If you don't see data arriving in your destination service, see [Troubleshoot issues with data exports from your Azure IoT Central application](troubleshooting.md).
99
+
If you don't see data arriving in your destination service, see [Troubleshooting in Azure IoT Central](troubleshooting.md).
100
100
101
101
# [Connection string](#tab/connection-string)
102
102
@@ -311,4 +311,4 @@ The following example shows an exported audit log message received in Azure Blob
311
311
312
312
## Next steps
313
313
314
-
Now that you know how to export to Blob Storage, a suggested next step is to learn [Export to Service Bus](howto-export-to-service-bus.md).
314
+
Now that you know how to export to Blob Storage, a suggested next step is to learn how to [Export IoT data to Service Bus](howto-export-to-service-bus.md).
Copy file name to clipboardExpand all lines: includes/iot-central-data-export-message-properties.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,21 +5,21 @@
5
5
author: dominicbetts
6
6
ms.service: azure-iot-central
7
7
ms.topic: include
8
-
ms.date: 05/22/2023
8
+
ms.date: 04/25/2025
9
9
ms.author: dobett
10
10
ms.custom: include file
11
11
---
12
12
13
13
#### Message properties
14
14
15
-
Telemetry messages have properties for metadata as well as the telemetry payload. The previous snippet shows examples of system messages such as `deviceId` and `enqueuedTime`. To learn more about the system message properties, see [System Properties of device-to-cloud IoT Hub messages](../articles/iot-hub/iot-hub-devguide-messages-construct.md#system-properties-of-device-to-cloud-messages).
15
+
Telemetry messages have properties for metadata and the telemetry payload. The previous snippet shows examples of system messages such as `deviceId` and `enqueuedTime`. To learn more about the system message properties, see [System properties of device-to-cloud messages](../articles/iot-hub/iot-hub-devguide-messages-construct.md#system-properties-of-device-to-cloud-messages).
16
16
17
17
You can add properties to telemetry messages if you need to add custom metadata to your telemetry messages. For example, you need to add a timestamp when the device creates the message.
18
18
19
19
The following code snippet shows how to add the `iothub-creation-time-utc` property to the message when you create it on the device:
20
20
21
21
> [!IMPORTANT]
22
-
> The format of this timestamp must be UTC with no timezone information. For example, `2021-04-21T11:30:16Z` is valid, `2021-04-21T11:30:16-07:00` is invalid.
22
+
> The format of this timestamp must be UTC with no timezone information. For example, `2021-04-21T11:30:16Z` is valid, while `2021-04-21T11:30:16-07:00` is invalid.
Copy file name to clipboardExpand all lines: includes/iot-central-data-export-setup.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
author: dominicbetts
6
6
ms.service: azure-iot-central
7
7
ms.topic: include
8
-
ms.date: 05/22/2023
8
+
ms.date: 04/25/2025
9
9
ms.author: dobett
10
10
ms.custom: include file
11
11
---
@@ -29,12 +29,12 @@ Now that you have a destination to export your data to, set up data export in yo
29
29
30
30
| Data type | Description | Data format |
31
31
| :------------- | :---------- | :----------- |
32
-
| Telemetry | Export telemetry messages from devices in near-real time. Each exported message contains the full contents of the original device message, normalized. |[Telemetry message format](#telemetry-format)|
33
-
| Property changes | Export changes to device and cloud properties in near-real time. For read-only device properties, changes to the reported values are exported. For read-write properties, both reported and desired values are exported. |[Property change message format](#property-changes-format)|
| Device template lifecycle | Export published device template changes including created, updated, and deleted. |[Device template lifecycle changes message format](#device-template-lifecycle-changes-format)|
37
-
| Audit logs | Logs of user-initiated updates to entities in the application. To learn more, see [Use audit logs to track activity in your IoT Central application](../articles/iot-central/core/howto-use-audit-logs.md)|[Audit log message format](#audit-log-format)|
32
+
| Telemetry | Export telemetry messages from devices in near-real time. Each exported message contains the full contents of the original device message, normalized. |[Telemetry format](#telemetry-format)|
33
+
| Property changes | Export changes to device and cloud properties in near-real time. For read-only device properties, changes to the reported values are exported. For read-write properties, both reported and desired values are exported. |[Property changes format](#property-changes-format)|
| Device template lifecycle | Export published device template changes including created, updated, and deleted. |[Device template lifecycle changes format](#device-template-lifecycle-changes-format)|
37
+
| Audit logs | Logs of user-initiated updates to entities in the application. To learn more, see [Use audit logs to track activity in your IoT Central application](../articles/iot-central/core/howto-use-audit-logs.md)|[Audit log format](#audit-log-format)|
38
38
39
39
1. Optionally, add filters to reduce the amount of data exported. There are different types of filter available for each data export type:
Copy file name to clipboardExpand all lines: includes/iot-central-data-export.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
author: dominicbetts
6
6
ms.service: azure-iot-central
7
7
ms.topic: include
8
-
ms.date: 05/22/2023
8
+
ms.date: 04/25/2025
9
9
ms.author: dobett
10
10
ms.custom: include file
11
11
---
@@ -23,7 +23,7 @@ For example, you can:
23
23
> When you turn on data export, you get only the data from that moment onward. To retain more historical data, turn on data export early. To manually export data from times when data export was turned off, see [How to use the IoT Central REST API to query devices](../articles/iot-central/core/howto-query-with-rest-api.md).
24
24
25
25
> [!NOTE]
26
-
> In some circumstances it could take up to 60 seconds for the messages to be exported. This time is measured from when IoT Central receives the message from the underlying IoT hub to when the message is delivered to the destination endpoint.
26
+
> In some circumstances, it could take up to 60 seconds for the messages to be exported. This time is measured from when IoT Central receives the message from the underlying IoT hub to when the message is delivered to the destination endpoint.
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments