The weakest link in most digital networks is the person sitting in front of the screen – the defining feature of the Internet of People (IoP). Because that’s where, through cunning and manipulative tactics, unsuspecting recipients can be tricked into opening toxic links. Little do they know, however, they’ve unwittingly opened the gates to digital catastrophe. Of course, I have nothing against people. In fact, some of my best friends are people!

The ‘Internet of Things’ was first coined to help people understand the concept of digital appliances that could communicate with an app or central hub. If you’ve been to CES at any point in the last decade, you could see many examples on the show floor, such as connected weight scales or a connected fridge. But these early examples of ‘connected’ tech felt more gimmicky than useful, and were largely contained to the consumer electronics industry.

At re:Invent this year, AWS announced its new digital twin service, AWS IoT TwinMaker (in preview), which allows users to create digital twins of real-world systems like buildings, factories, industrial equipment, and production lines. Using a digital twin to monitor and improve operations for a physical system requires ingesting data from IoT sensors, process instruments, cameras, and enterprise systems, and curating and associating data from these disparate sources.

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.

Canonical and Advantech have collaborated to help enterprises accelerate Edge AIoT Applications with Ubuntu 20.04 LTS certified on the EPC-U3233, powered by an 8th Gen Intel® Core™ i series processor. This compact fanless embedded PC facilitates data-intensive computing in IoT edge applications.

December 14, 2021: Canonical and Xilinx Inc. announced today the publication of Ubuntu images optimised for Xilinx Zynq UltraScale+ evaluation boards and the production-ready Kria System-on-Modules (SOM). The companies are collaborating to bring enterprise-grade Linux to the world of adaptive SoCs to accelerate the development of new software-defined devices across all IoT verticals.

The Internet of Things (IoT) is a term that describes the increasingly sophisticated ecosystems of online, connected devices we share our world with. The slightly odd name refers to the fact that the first iteration of the internet was simply a network of connected computers. As the internet grew, phones, office equipment like printers and scanners, and industrial machinery were added to the internet.

With rising unit shipments and hardware spending, 2021 will go into the record books as a critical year in the ever-increasing adoption of connected devices. Ubuntu – the modern, open-source Linux operating system for the enterprise server, desktop, and cloud – is rapidly becoming the de-facto standard for Internet of Things ( IoT) devices.

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.

If you have worked in the automation sector for some time, it is likely you have come across or at least heard of PTC Kepware. They provide one of the largest connectivity suites for automation devices such as PLC’s easing the bridge between the OT (Operation Technology) and IT (Information Technology) world. The best part? You can store, transform and visualize this data using InfluxDB. This blog post will take you through the different ways of connecting your Kepware instance to InfluxDB.