Telemetry

Telemetry data is used for asset recovery purposes. To guarantee the highest chance of asset recovery, Notifense requires your application to send real-time and (some) historical telemetry data when an event for an asset is escalated (see Callbacks).

Optionally, you can make use of our telemetry data ingestion service for event generation.

When sending telemetry, all properties of the Telemetry object are optional.

Asset recovery

Telemetry data sent by your application for asset recovery purposes will be stored for 90 days, after which is it automatically deleted. This ensures Notifense can do efficient asset recovery, improve its recovery processes and, when required, report to and collaborate with law enforcement.

To send telemetry data for asset recovery purposes, use the POST /v1/assets/{assetId}/telemetry endpoint.

Event generation

If your application is not capable of creating events in Notifense, you can optionally make use of our event generation service. To do this, your application should send all incoming (real-time) telemetry data to the event generation service, and Notifense will create events using that data.

The ingested telemetry data will be used to keep a "digital shadow" of your asset. A digital shadow is a virtual copy of the state of your asset. This digital shadow is used to generate events whenever telemetry data is processed for this asset.

Other than the digital shadow, Notifense does not store the ingested data sent from your application once it is processed.

For event generation to work properly, assets must be configured with "telemetry rules" to correctly generate certain events. For example, if you want to be able to create the "fuel level low" event, the "fuel level low threshold" value must be specified in the asset's telemetry rules.

Ingestion is billed at the end of every month.

To enable event generation, please contact us at info@notifense.com.

Ingesting telemetry

You can use AMQP or HTTPS to send telemetry data to our event generation service. Notifense uses Azure Event Hub to ingest telemetry data. Use the GET /v1/account/ingestionToken endpoint to request a Shared Access Signature token to authenticate to Event Hub. This ingestion token has a long lifetime.

The event body should be JSON following the TelemetryMessage schema.

Event Hub host name: evhns-nf-prd.servicebus.windows.net

Using an SDK

Microsoft provides multiple client SDKs for connecting to Event Hub. You can find an overview of supported SDKs here.

Using HTTPS

Telemetry should be sent to the publisher endpoint for the telemetry Event Hub. Use the token you acquired from the ingestion token endpoint as the Authentication header value for the HTTP request.

Publisher endpoint: https://evhns-nf-prd.servicebus.windows.net/telemetry/messages

Using AMQP

Telemetry can be sent over AMQP 1.0. Azure Event Hub supports authentication using SASL ANONYMOUS and CBS. For more information, please consult Microsoft's documentation here.