Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Streaming Analytics job not receiving inputs from IOT hub

I followed a IOT Hub tutorial and got it working. I then created a Stream Analytics job and used the above as an Input (which upon test connection works).

However I do not see any inputs being received. When running a sample test I get the following error:

Description Error code: ServiceUnavailable Error message: Unable to connect to input source at the moment. Please check if the input source is available and if it has not hit connection limits.

I can see telemetry messages being received in the IOT Hub. Any help would be appreciated

like image 342
dataEng Avatar asked Jan 24 '17 20:01

dataEng


People also ask

How do I create a stream analytics job?

On a separate tab of the same browser window or in a separate browser window, sign in to the Azure portal. Select Create a resource in the upper left-hand corner of the Azure portal. Select Analytics > Stream Analytics job from the results list.

Which of the definitions below best describes a tumbling window?

Tumbling windows are a series of fixed-sized, non-overlapping and contiguous time intervals. The following diagram illustrates a stream with a series of events and how they are mapped into 10-second tumbling windows.


2 Answers

Is the stream analytics job running?

I had a similar problem where i wasn't getting any events from stream analytics and i had forgotten to turn it on.

Click on the stream analytics > overview > start

like image 57
yamspog Avatar answered Sep 20 '22 06:09

yamspog


I had the same problem (using Event Hubs in my case). The root cause was that I had too many queries within my job running against the same input. I solved it by splitting my input into several inputs across multiple consumer groups.

From the documentation (emphasis added):

Each Stream Analytics IoT Hub input should be configured to have its own consumer group. When a job contains a self-join or multiple inputs, some input may be read by more than one reader downstream, which impacts the number of readers in a single consumer group. To avoid exceeding IoT Hub limit of 5 readers per consumer group per partition, it is a best practice to designate a consumer group for each Stream Analytics job.

like image 22
Lars Kemmann Avatar answered Sep 21 '22 06:09

Lars Kemmann