Skip to content

Commit 9eb7b6d

Browse files
committed
Add timestamp note.
1 parent 1462f21 commit 9eb7b6d

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

articles/iot-central/core/concepts-telemetry-properties-commands.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -62,6 +62,16 @@ Don't create telemetry types with the following names. IoT Central uses these re
6262
* `$metadata`
6363
* `$version`
6464

65+
### Telemetry timestamps
66+
67+
By default, IoT Central uses the message enqueued time when it displays telemetry on dashboards and charts. Message enqueued time is set internally when IoT Central receives the message from the device.
68+
69+
A device can set the `iothub-creation-time-utc` property when it creates a message to send to IoT Central. If this property is present, IoT Central uses it when it displays telemetry on dashboards and charts.
70+
71+
You can export both the enqueued time and the `iothub-creation-time-utc` property when you export telemetry from your IoT Central application.
72+
73+
To learn more about message properties, see [System Properties of device-to-cloud IoT Hub messages](../../iot-hub/iot-hub-devguide-messages-construct.md#system-properties-of-d2c-iot-hub-messages).
74+
6575
### Telemetry in components
6676

6777
If the telemetry is defined in a component, add a custom message property called `$.sub` with the name of the component as defined in the device model. To learn more, see [Tutorial: Create and connect a client application to your Azure IoT Central application](tutorial-connect-device.md).

0 commit comments

Comments
 (0)