We've been having a few issues with Azure IotHub. I have a stream analytics job listening to an IotHub. My stream analytics job which was working perfectly fine just started showing no input and output. On restart it came up with the following error "Stream Analytics job has validation errors: Querying EventHub returned an error: ProtocolName." Which sort of indicates to me that it can't listen to IotHub anymore. Has anyone else had similar issues?. Help on troubleshooting this would be great.
stream analytics job error
There was an issue with EventHub that has since been addressed which should fix this. If this problem persists, please contact support.
Related
just wondering if i could get some help about azure iot hub and stream analytics.
I'm using this guide to build my simulated device https://learn.microsoft.com/en-us/azure/iot-hub/quickstart-send-telemetry-python
however, whenever i try to extend the json telemetry message to include more key pairs, stream analytics always gives me this error
Source '<unknown_location>' had 1 occurrences of kind 'InputDeserializerError.InvalidData' between processing times '2020-07-14T02:35:47.4125308Z' and '2020-07-14T02:35:47.4125308Z'. Could not deserialize the input event(s) from resource 'Partition: [2], Offset: [806016], SequenceNumber: [1698], DeviceId: [testdevicereal]' as Json. Some possible reasons: 1) Malformed events 2) Input source configured with incorrect serialization format
I've checked my json formatting and it seems fine, any clues?
Deserialization issues are caused when the input stream of your Stream Analytics job contains malformed messages. For example, a malformed message could be caused by a missing parenthesis, or brace, in a JSON object or an incorrect timestamp format in the time field.
Enable resource logs to view the details of the error and the message (payload) that caused the error. There are multiple reasons why deserialization errors can occur. For more information regarding specific deserialization errors, see Input data errors. If resource logs are not enabled, a brief notification will be available in the Azure portal.
Please see Troubleshoot input connections for more details.
all, Can anybody help me with the solution for capturing the malformed json coming from event hub to azure stream analytics.
My use case is : I am getting json records on the event hub i.e. input is event hub -> parsing the json in Azure Stream analytics -> placing the parsed data in azure SQL DWH.
Now whenever the malformed json comes on the eventhub the ASA drops that event and parses only the correct json. I need to capture those malformed event ans report it to the Source application. Could you please let me know how to do this ?
Thanks,
Aditya
Please take a look at this article, seems that it can meet your needs.
When a Stream Analytics job receives a malformed message from an input, it drops the message and notifies you with a warning. Then follow this What caused the deserialization error to find the JSON data with the incorrect format.
We have an IOT application. Application has to detect any sudden changes(anomaly) in the device battery voltage. We were planing on using anomaly function built into stream analytics in azure for accomplishing this task.
When I'm running anomaly function in stream analytics query as follows
SELECT ANOMALYDETECTION(BATTERYVOLTAGE) OVER( LIMIT DURATION(hour, 1))
as anomaly FROM [IotTelemetryStream]
it is returning the following error message:
unexpected error has occurred. Please open a support ticket to investigate and provide the following client request id:_______
But when running the same query after removing anomaly function works fine.
SELECT BATTERYVOLTAGE as anomaly FROM [IotTelemetryStream]
I cannot find any reference for this issue any where on web so any help would be much appreciated and thanks in advance.
Can you please send your email address in a direct message to https://twitter.com/azurestreaming ? We will reach out to you with details after that.
I'm outputting a Stream Analytics job to PowerBI.com. It successfully sends the first 11-100 messages just fine, but after which it fails. In the operational log it says the operation "failed to send events" and is categorized as a "PowerBIOutputAdapterTransientError" without much other information. What are the symptoms of this type of error?
Messages are still going through Event Hubs but all operations seem to be haulted on the PowerBI side.
Looks like this was a transient service issue.
I followed this article to try eventhub with Apache Storm, But when I run the Storm topology it was receiving events for a minute and then it stopped receiving. So I've restarted my program and then it was receiving the remaining messages. Every time I run the program after a minute it couldn't receive from eventhub. Please help me with the possibilities of the issue...
Should I change any configurations at Storm or Zookeeper.
The above jar contains a fix for a known issue in the QPID JMS client, which is used by the Event Hub spout implementation. When the service sends an empty frame (heartbeat to keep connection alive), a decoding error occurs in the client and that causes the client to stop processing commands. Details of this issue can be found here: https://issues.apache.org/jira/browse/QPID-6378