Tartabit IoT-Bridge Setup Overview

Doc Set: Tartabit Data Pipeline

• Tartabit Data Pipes - Overview    <- you are here
• Setup LNS Service
• Create Post Trigger
• Create Decode Trigger
• Create Save Trigger
• Setup InfluxDB Service

Purpose of this Document Set:

• Tartabit IoT-Bridge as Data Processing Pipeline for Everynet LoRaWAN Network Service (LNS).

Tartabit Data Pipleline Overview

The following diagram provides an overview of the software systems that make up the data pipeline from data source (LoRaWAN Network Server, aka LNS) to the storage container (InfluxDB).

.

This document set provides the details to deploy a data pipeline using Everynet LNS, Tartabit IoT-Bridge, and InfluxDB.

Tartabit Data Pipeline Setup Tasks

To enable the Tartabit Data Pipeline for your application, you need to complete the following configuration tasks on the Tartabit IoT-Bridge.

1. Setup Source Service - LoRaWAN Network Server (webhook)
2. Create Trigger to process HTTP Post
3. Create Trigger for processing Device Payload
4. Create Trigger for saving the Data Record
5. Setup Destination Service - InfluxDB

This diagram provides an overview of the Tartabit IoT-Bridge components that will be setup in this document set.

Setup a Naming Convention

Using a standardized naming convention is critical to providing clarity and simplicity during system management.

Example: redteam-mousetrap-<functions>

• all services and triggers will prefix- with an adminstrative group, e.g. redteam-
• all services and triggers should use an application name to follow the prefix, e.g. mousetrap
• all services and triggers should use a -suffix to name the function provided; i.e. lns, post, decode, save, influx

In this docset, we will be developing the Data Pipeline: usfieldtest-radiobridge.

Goto: Setup LNS