locked
how can we route messages in iothub? RRS feed

  • Question

  • We are using the simulated device example from the github and it is sending telemetry messages to the iothub without any issues.

    Apart from the telemetry messages, there will be some other messages like custom events. How can we differentiate these kind of messages? Currently all these messages are coming to the same event source and with an event listener we are separating these kind of messages based on a custom tag.

    Our ultimate agenda is to use a time series insights in which we need to get only the telemetry data. Currentlty we are getting both telemetry data and custom events in the time series. How we can restrict this?

    We could find some message routing option in the IoT Hub, in which we have created a new event hub endpoint.  With the test routing option in the same page, we could validate my routing query. But how to apply this to the time series. The time series still capturing both matching and not matching messages.

    Thanks in advance.
    Friday, September 27, 2019 12:28 PM

Answers