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/azure-maps/azure-maps-event-grid-integration.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ Azure Event Grid is a fully managed event routing service, which uses a publish-
24
24
25
25
## Azure Maps events types
26
26
27
-
Event grid uses [event subscriptions](../event-grid/concepts.md#event-subscriptions) to route event messages to subscribers. An Azure Maps account emits the following event types:
27
+
Event Grid uses [event subscriptions](../event-grid/concepts.md#event-subscriptions) to route event messages to subscribers. An Azure Maps account emits the following event types:
The schema for DeviceConnected and DeviceDisconnected events have the same structure. This sample event shows the schema of an event raised when a device is connected to an IoT hub:
27
+
The schemas for DeviceConnected and DeviceDisconnected events have the same structure. This sample event shows the schema of an event raised when a device is connected to an IoT hub:
28
28
29
29
```json
30
30
[{
@@ -81,7 +81,7 @@ The DeviceTelemetry event is raised when a telemetry event is sent to an IoT Hub
81
81
}]
82
82
```
83
83
84
-
The schema for DeviceCreated and DeviceDeleted events have the same structure. This sample event shows the schema of an event raised when a device is registered to an IoT hub:
84
+
The schemas for DeviceCreated and DeviceDeleted events have the same structure. This sample event shows the schema of an event raised when a device is registered to an IoT hub:
85
85
86
86
```json
87
87
[{
@@ -131,7 +131,7 @@ The schema for DeviceCreated and DeviceDeleted events have the same structure. T
131
131
132
132
# [Cloud event schema](#tab/cloud-event-schema)
133
133
134
-
The schema for DeviceConnected and DeviceDisconnected events have the same structure. This sample event shows the schema of an event raised when a device is connected to an IoT hub:
134
+
The schemas for DeviceConnected and DeviceDisconnected events have the same structure. This sample event shows the schema of an event raised when a device is connected to an IoT hub:
135
135
136
136
```json
137
137
[{
@@ -186,7 +186,7 @@ The DeviceTelemetry event is raised when a telemetry event is sent to an IoT Hub
186
186
}]
187
187
```
188
188
189
-
The schema for DeviceCreated and DeviceDeleted events have the same structure. This sample event shows the schema of an event raised when a device is registered to an IoT hub:
189
+
The schemas for DeviceCreated and DeviceDeleted events have the same structure. This sample event shows the schema of an event raised when a device is registered to an IoT hub:
190
190
191
191
```json
192
192
[{
@@ -245,7 +245,7 @@ All events contain the same top-level data:
245
245
| Property | Type | Description |
246
246
| -------- | ---- | ----------- |
247
247
|`id`| string | Unique identifier for the event. |
248
-
|`topic`| string | Full resource path to the event source. This field is not writeable. Event Grid provides this value. |
248
+
|`topic`| string | Full resource path to the event source. This field isn't writeable. Event Grid provides this value. |
249
249
|`subject`| string | Publisher-defined path to the event subject. |
250
250
|`eventType`| string | One of the registered event types for this event source. |
251
251
|`eventTime`| string | The time the event is generated based on the provider's UTC time. |
@@ -261,7 +261,7 @@ All events contain the same top-level data:
261
261
| Property | Type | Description |
262
262
| -------- | ---- | ----------- |
263
263
|`id`| string | Unique identifier for the event. |
264
-
|`source`| string | Full resource path to the event source. This field is not writeable. Event Grid provides this value. |
264
+
|`source`| string | Full resource path to the event source. This field isn't writeable. Event Grid provides this value. |
265
265
|`subject`| string | Publisher-defined path to the event subject. |
266
266
|`type`| string | One of the registered event types for this event source. |
267
267
|`time`| string | The time the event is generated based on the provider's UTC time. |
@@ -293,7 +293,7 @@ For **Device Telemetry** IoT Hub event, the data object contains the device-to-c
293
293
| -------- | ---- | ----------- |
294
294
|`body`| string | The content of the message from the device. |
295
295
|`properties`| string | Application properties are user-defined strings that can be added to the message. These fields are optional. |
296
-
|`system properties`| string |[System properties](../iot-hub/iot-hub-devguide-routing-query-syntax.md#system-properties) help identify contents and source of the messages. Device telemetry message must be in a valid JSON format with the contentType set to JSON and contentEncoding set to UTF-8 in the message system properties. If this is not set, then IoT Hub will write the messages in base 64 encoded format. |
296
+
|`system properties`| string |[System properties](../iot-hub/iot-hub-devguide-routing-query-syntax.md#system-properties) help identify contents and source of the messages. Device telemetry message must be in a valid JSON format with the contentType set to JSON and contentEncoding set to UTF-8 in the message system properties. If this isn't set, then IoT Hub will write the messages in base 64 encoded format. |
297
297
298
298
For **Device Created** and **Device Deleted** IoT Hub events, the data object contains the following properties:
299
299
@@ -303,13 +303,13 @@ For **Device Created** and **Device Deleted** IoT Hub events, the data object co
303
303
|`deviceID`| string | The unique identifier of the device twin. |
304
304
|`etag`| string | A validator for ensuring consistency of updates to a device twin. Each etag is guaranteed to be unique per device twin. |
305
305
|`deviceEtag`| string | A validator for ensuring consistency of updates to a device registry. Each deviceEtag is guaranteed to be unique per device registry. |
306
-
|`status`| string |Whether the device twin is enabled or disabled. |
306
+
|`status`| string |Indicates whether the device twin is enabled or disabled. |
307
307
|`statusUpdateTime`| string | The ISO8601 timestamp of the last device twin status update. |
308
-
|`connectionState`| string |Whether the device is connected or disconnected. |
308
+
|`connectionState`| string |Indicates whether the device is connected or disconnected. |
309
309
|`lastActivityTime`| string | The ISO8601 timestamp of the last activity. |
310
310
|`cloudToDeviceMessageCount`| integer | Count of cloud to device messages sent to this device. |
311
311
|`authenticationType`| string | Authentication type used for this device: either `SAS`, `SelfSigned`, or `CertificateAuthority`. |
312
-
|`x509Thumbprint`| string | The thumbprint is a unique value for the x509 certificate, commonly used to find a particular certificate in a certificate store. The thumbprint is dynamically generated using the SHA1 algorithm, and does not physically exist in the certificate. |
312
+
|`x509Thumbprint`| string | The thumbprint is a unique value for the x509 certificate, commonly used to find a particular certificate in a certificate store. The thumbprint is dynamically generated using the SHA1 algorithm, and doesn't physically exist in the certificate. |
313
313
|`primaryThumbprint`| string | Primary thumbprint for the x509 certificate. |
314
314
|`secondaryThumbprint`| string | Secondary thumbprint for the x509 certificate. |
315
315
|`version`| integer | An integer that is incremented by one each time the device twin is updated. |
0 commit comments