Azure Data Explorer (ADX) is a great data exploration tool for IoT developers building a full IoT solution. This could be a perfect target for the cold path.
As seen in my previous blog post, ADX even offers a native connector for the IoT Hub. This is based on the ‘default EventHub compatible endpoint’ offered by this cloud IoT gateway (optionally the built-in Events endpoint in the routing section of the IoT Hub or using the fallback mechanism).
Most of the documentation regarding this ADX connector is following this ‘happy flow’ where one connector stores incoming IoT telemetry in one ADX table using static routing.
This is a serious limitation where most IoT Hubs ingest multiple types of messages. These will not fit into that single table.
Luckily, the connector also offers the possibility to allow routing to other databases:
Here, we will check out this dynamic routing option and see how this provides much more flexibility.