The most common distribution type uses HTTP protocol to distribute the data.
For each telemetry message, a new HTTP request is created and sent to your service's HTTP server.
Currently, only additional HTTP headers can be set using the specific configuration.
| Name | Description | Valid values |
|---|---|---|
target_additional_http_headers | Additional HTTP headers sent with each request | JSON object |
Following is an example of configuration JSON where custom headers are used to send a Bearer token with each request.
{
"target_additional_http_headers": {
"X-My-Custom-Id": "12345"
}
}
If your service is equipped with an MQTT Broker Server, you can use the MQTT Client type to connect to your server and publish the data.
| Name | Description | Valid values |
|---|---|---|
mqtt_dist_client_id | MQTT Client ID | Any string |
mqtt_dist_transport | Transport type used to connect to the server | tcp or websockets |
mqtt_dist_tls | Should TLS be used to connect? | true or false |
mqtt_dist_json_datastream_topic | Topic used for sending telemetry messages | Any string |
mqtt_dist_publish_qos_default | QoS parameter of messages sent from the client | Any integer number |
embed_metadata | Adds message metadata like account_visibility or integration_client_id to payload | true or false |
Following is an example of configuration JSON.
{
"mqtt_dist_client_id": "dronetag_0001",
"mqtt_dist_transport": "tcp",
"mqtt_dist_tls": false,
"mqtt_dist_json_datastream_topic": "dronetag/telemetry/{msgtype}",
"mqtt_dist_publish_qos_default": 0
}
{msgtype} in topic nameIf you use Dronetag DUMP format and you'd like to send different types of messages to different topics, you can use the {msgtype} placeholder in the topic name. It will be replaced with the actual message type before sending. For example, if the message type is "UA telemetry", the topic dronetag/telemetry/{msgtype} will become dronetag/telemetry/tele-ua.
Available message types are:
tele-ua - UA telemetry messagestele-operator - Operator telemetry messagestele-system - System telemetry messagesoperation-update - Operation update messagesRefer to the 'Understanding DUMP' page for more information about the message types.
This distribution type uses plain TCP or UDP socket to distribute the data.
| Name | Description | Valid values |
|---|---|---|
embed_metadata | Adds message metadata like account_visibility or integration_client_id to payload | true or false |
Following is an example of configuration JSON
{
"embed_metadata": true
}
Every chapter of this document is a page of the Dronetag help site. Use these addresses to reach the latest version.