Forum Discussion

MMacarie's avatar
MMacarie
Frequent Visitor
1 year ago
Solved

How does the IoT Hub work?

I am currently using Fabric for work and I am trying to find ways to have continuous ingestion of data from an IoT Hub. I tried using an Eventstream with the IoT Hub as the source, but then I found o...
Questions
  • Murtaza_Ghafoor's avatar
    Murtaza_Ghafoor
    1 year ago
      • There is only one storage location for messages, within IoT Hub’s event retention.
      • The Event Hub-compatible endpoint does not create a separate Event Hub; it is just an alternate access point to IoT Hub’s event store.

    2. Time Fields Difference

      • EnqueuedTime (from IoTHub structure) represents when the message was received by IoT Hub.
      • EventEnqueuedUtcTime represents when the message was made available for consumers via Event Hub.
      • The slight difference between them is due to IoT Hub’s internal processing and routing delays.

    3. Cost Differences

      • IoT Hub as Source: Higher cost due to IoT-specific metadata and additional processing.
      • Event Hub-Compatible Endpoint: Lower cost as it only provides telemetry and event timestamps, skipping extra IoT Hub metadata.

    4. Background Differences

      • IoT Hub Source: Provides full telemetry + metadata like device identity and connection details.
      • Event Hub-Compatible Endpoint: Provides only telemetry and basic event timestamps, reducing overhead.

    5. Why Both Options?

      • IoT Hub Source: Use when you need rich IoT metadata (device-specific details, routing, etc.).
      • Event Hub-Compatible Endpoint: Use when you need only telemetry with lower overhead and cost.
     
Murtaza_Ghafoor's avatar
Murtaza_Ghafoor
Super User
1 year ago
    • There is only one storage location for messages, within IoT Hub’s event retention.
    • The Event Hub-compatible endpoint does not create a separate Event Hub; it is just an alternate access point to IoT Hub’s event store.

  2. Time Fields Difference

    • EnqueuedTime (from IoTHub structure) represents when the message was received by IoT Hub.
    • EventEnqueuedUtcTime represents when the message was made available for consumers via Event Hub.
    • The slight difference between them is due to IoT Hub’s internal processing and routing delays.

  3. Cost Differences

    • IoT Hub as Source: Higher cost due to IoT-specific metadata and additional processing.
    • Event Hub-Compatible Endpoint: Lower cost as it only provides telemetry and event timestamps, skipping extra IoT Hub metadata.

  4. Background Differences

    • IoT Hub Source: Provides full telemetry + metadata like device identity and connection details.
    • Event Hub-Compatible Endpoint: Provides only telemetry and basic event timestamps, reducing overhead.

  5. Why Both Options?

    • IoT Hub Source: Use when you need rich IoT metadata (device-specific details, routing, etc.).
    • Event Hub-Compatible Endpoint: Use when you need only telemetry with lower overhead and cost.