I have blogged about Azure Data Explorer (ADX) integration already a couple of times.
The new ADX database data connection for IoT Hub is a nice addition but appears to be quite static because you can only fill in one (single) table mapping.
ADX also supports dynamic routing (using that same data connection) where the message body is accompanied by application/user properties which tell ADX the table and mapping to use during ingest.
The ultimate goal is to have a solution where one stream of data, with one or more types of messages, is split into multiple tables:
The combination of IoT Hub routing and multiple endpoints should help with that but due to message enrichment limitations, we need to find another way.
A viable solution is the ADX table update policy.
Let’s check it out.Doorgaan met het lezen van “Using ADX table update policies projecting raw messages to target tables”