none
IoT Hub to ASA: Fields set by IotHub are empty

    Question

  • Hi, I'm using IoTHub as a Data Stream Input to the Stream Analytics Job I have. 

    But recently, I have been getting nothing in the IoTHub property in the output JSON file.

    This is the query that I used:

    SELECT * , IoTHub.ConnectionDeviceId AS deviceId, deviceTs AS id
    INTO [output]
    FROM [input]



    The fields that I was getting were:

    {
      "deviceTs" : 1460643005
      "data": -0.444086,
      "EventProcessedUtcTime": "2016-04-14T22:10:05.7227638Z",
      "PartitionId": 0,
      "EventEnqueuedUtcTime": "2016-04-14T22:10:06.071Z",
      "IoTHub": {
        "MessageId": "e9f00e3500-c2880-65c00-9ddd04538ec0bcd80e1c00",
        "CorrelationId": null,
        "ConnectionDeviceId": "23527c7838a609ee",
        "ConnectionDeviceGenerationId": "635939059828541930",
        "EnqueuedTime": "0001-01-01T00:00:00",
        "StreamId": null
      },
      "deviceId": "23527c7838a609ee",
      "id": "1460643005"
    }



    However, now I am getting:

    {
        "deviceTs" : 1460911792
        "data": "-0.657009",
        "EventProcessedUtcTime": "2016-04-17T16:49:52.8175759Z",
        "PartitionId": 1,
        "EventEnqueuedUtcTime": "2016-04-17T16:49:53.012Z",
        "IoTHub": {
          "IoTHub": {}
        },
        "deviceId": null,
        "id": "1460911792"
      }

    The output was taken from a DocumentDB output. However, I was playing with Azure Blob storage and Table storage as outputs as well.

    Any ideas?


    Thanks!



    • Edited by Irusha Vidanamadura Sunday, April 17, 2016 5:58 PM removed metadata that is created by default in DocumentDB from second JSON.
    Sunday, April 17, 2016 5:02 PM

Answers

All replies

  • Hi

    I am having the same issue.

    It does not affect currently running ASA jobs, but if a job is restarted the error will occur. I have replicated the issue on two different IotHubs both residing in North Europe. 

    The issue began some time after 2:30 pm friday and saturday morning (GMT+1)

    Kind regards, Mark.

    Monday, April 18, 2016 8:37 AM
  • Hi Irusha/Mark,

    The issue has been identified and we're working on addressing it asap. I'll keep you posted on the progress.

    thanks,
    Chetan


    [Disclaimer] This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all.

    Monday, April 18, 2016 1:40 PM
  • Hi folks,

    We've addressed the issue, can you please restart your job(s) to mitigate your issue ?

    thanks,
    Chetan


    [Disclaimer] This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all.

    Monday, April 18, 2016 7:38 PM