Skip to content

Commit 782c584

Browse files
committed
Remove inline questions for product team prior to publishing
1 parent ed3d3fa commit 782c584

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/iot-hub/iot-hub-non-telemetry-event-schema.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This article provides the properties and schema for Azure IoT Hub n
44
author: kgremban
55
ms.author: kgremban
66
ms.topic: conceptual
7-
ms.date: 06/09/2022
7+
ms.date: 07/01/2022
88
ms.service: iot-hub
99
services: iot-hub
1010
---
@@ -36,12 +36,12 @@ The following system properties are set by IoT Hub on each event.
3636
| -------- | ---- | ---------- | ------------------------- |
3737
| content-encoding | string | utf-8 | $contentEncoding |
3838
| content-type | string | application/json | $contentType |
39-
| correlation-id | string | A unique ID that identifies the event. **NEED MORE DEFINITION! Is this something that can be used to identify events routed to different services? Sometimes it's a GUID and sometime it isn't.** | $correlationId |
39+
| correlation-id | string | A unique ID that identifies the event. | $correlationId |
4040
| user-id | string | The name of IoT Hub that generated the event. | $userId |
4141
| iothub-connection-device-id | string | The device ID. | $connectionDeviceId |
4242
| iothub-connection-module-id | string | The module ID. This property is output only for module life cycle and twin events. | $connectionModuleId |
43-
| iothub-enqueuedtime | number | Date and time when the notification was sent. **DESCRIPTION NEEDED as this is a number not a UTC string: 1653677358153. My best guess is that it's a Unix epoch in milliseconds** In routing queries, use an [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) timestamp; for example, `$enqueuedTime > "2022-06-06T22:56:06Z"` | $enqueuedTime |
44-
| iothub-message-source | string | The event category that identifies the message source. For example, *deviceLifecycleEvents*. | **N/A (tried $messageSource but it didn't work)** |
43+
| iothub-enqueuedtime | number | Date and time when the notification was sent. In routing queries, use an [ISO8601](https://en.wikipedia.org/wiki/ISO_8601) timestamp; for example, `$enqueuedTime > "2022-06-06T22:56:06Z"` | $enqueuedTime |
44+
| iothub-message-source | string | The event category that identifies the message source. For example, *deviceLifecycleEvents*. | N/A |
4545

4646
### Application properties
4747

0 commit comments

Comments
 (0)