Scroll down for the author’s photo and bio. Time series databases like InfluxDB index data by time. They are efficient at recording constant data streams like server metrics, application monitoring, sensor reports, or any other data containing a timestamp. The structure makes analyzing change over time a breeze. This tutorial will show you how to set up InfluxDB with a sample Ruby application.
Buckle up, this one isn’t short…but I’m hoping it will be thoroughly informative! This post is about Telegraf as a consumer of MQTT messages in the context of writing them to InfluxDB. If you are interested in and unfamiliar with Telegraf, you can view docs here. Unsure if Telegraf aligns with your needs? I make a case for it in the Optimizing Writes section of this blog post. It may also help to have an understanding of Line Protocol, InfluxDB’s default accepted format.
When it comes to writing data to InfluxDB, you have a lot of options. You can: The last bullet is the most powerful and flexible way of maintaining and managing your fleet of IoT devices. That architecture offers you several advantages including: Architecture drawing of the last bullet. Sensors write data to an OSS instance of InfluxDB at the edge which in turn write data to InfluxDB Cloud.
