Integrating Influx Alerting with Event-driven Architecture

Business Case In a project where numerous time series from IoT devices are stored, the following architecture is in place: A Kafka broker that holds the measurements obtained from the IoT devices. A simple sink connector that writes the measurements to the InfluxDB database for historical storage. A legacy backend service for process configuration, which uses MySQL for saving configurations. To ensure that the measurements are being stored in the time series database, we want to create an alerting mechanism that can notify the user if data from an “active” IoT device stops arriving at the database.