Integrations
Integrations refer to the cloud side APIs for Drogue Cloud, which allow your application to access data coming from devices and schedule commands to devices.
Incoming data
Incoming data is streamed to applications in the form of Cloud Events. The message stream may contain telemetry events, as well as some infrastructure events.
The following events may contain additional attributes, not listed here. These are implementation details are should not be relied upon. |
Device events
All regular messages/events a device sends, will end up as a "device event".
Attributes
Attribute | Type | Required | Description |
---|---|---|---|
Standard attributes |
|||
|
String |
X |
Always |
|
String |
X |
Always |
|
String |
X |
A unique event ID. |
|
String |
X |
The channel information. |
|
String (RFC3339) |
X |
The time the event arrived in the system. |
|
String |
X |
The content type of the message. |
|
String |
The schema of the payload, encoded in the format defined in |
|
Extensions |
|||
|
String |
X |
A unique identifier of the Drogue Cloud instance on this connection. |
|
String |
X |
The name of the application the device belonged to. |
|
String |
X |
The unique ID of the application the device belonged to. |
|
String |
X |
The name of the device the event originated from. |
|
String |
X |
The unique ID of the device the event originated from. |
|
String |
X |
The name of the device which delivered the event to Drogue Cloud. |
|
String |
X |
The unique ID of the device which delivered the event to Drogue Cloud. |
UID fields
The |
Sender vs Device
The sender is a device which connected to Drogue Cloud. The "device" is the device the event originated from. If the originating device is also the connected device, both fields will have the same value. Drogue Cloud will also enforce that a device must be listed as gateway, in order to act on its behalf. |
Connection events
When a device connects through a connection oriented protocol (like MQTT), connection events will be issued by Drogue Cloud on behalf of the device.
Only devices which directly connect to Drogue Cloud will issue such events. Devices connected via another device, acting as gateway, do not. |
Attributes
Attribute | Type | Required | Description |
---|---|---|---|
Standard attributes |
|||
|
String |
X |
Always |
|
String |
X |
Always |
|
String |
X |
A unique event ID. |
|
String |
X |
Always |
|
String (RFC3339) |
X |
The time the event was issues. |
|
String |
X |
Always |
Extensions |
|||
|
String |
X |
A unique identifier of the Drogue Cloud instance on this connection. |
|
String |
X |
The name of the application the device belonged to. |
|
String |
X |
The unique ID of the application the device belonged to. |
|
String |
X |
The name of the device the event originated from. |
|
String |
X |
The unique ID of the device the event originated from. |
|
String |
X |
The name of the device which delivered the event to Drogue Cloud. |
|
String |
X |
The unique ID of the device which delivered the event to Drogue Cloud. |
Device registry events
Whenever a change is made to a device in the registry, a "device change event" is sent out.
Attributes
Attribute | Type | Required | Description |
---|---|---|---|
Standard attributes |
|||
|
String |
X |
Always |
|
String |
X |
Always |
|
String |
X |
A unique event ID. |
|
String |
X |
Always |
|
String (RFC3339) |
X |
The time the event was generated. |
Extensions |
|||
|
String |
X |
A unique identifier of the Drogue Cloud instance on this connection. |
|
String |
X |
The name of the application the device belonged to. |
|
String |
X |
The unique ID of the application the device belonged to. |
|
String |
X |
The name of the device the event originated from. |
|
String |
X |
The unique ID of the device the event originated from. |
|
String |
X |
The name of the device which delivered the event to Drogue Cloud. |
|
String |
X |
The unique ID of the device which delivered the event to Drogue Cloud. |