Achieving Real-Time Visibility and On-the-Fly Analysis of Telemetry Data for Wind Turbines
Question
As part of your industrial IoT solution, you have 10 wind turbines equipped with several sensors.
All of these sensors send thousands of telemetry data to an IoT hub.
You have built a solution which provides real-time visibility, on-the-fly analysis of key data for the operations staff.
For troubleshooting and further analysis purposes, you decide to use the Connections and Device telemetry logs and send them to the Log Analytics via diagnostic settings in the IoT hub.
Is that sufficient to achieve your goal?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B.Correct Answer: A.
Option A is CORRECT because while resource logs are generated automatically, in order to make them available for later use, a diagnostic setting must be configured in the IoT Hub for redirecting data into one of the three destinations: Log Analytics, Event hubs, Storage account.
No automatic log collection takes place.
Option B is incorrect because resource logs (like Connections and Device telemetry) are generated automatically by Azure resources, in order for them to be collected, you need to configure a diagnostic setting in the IoT Hub.
So, the correct answer is: Yes.
Diagram:
![Home > contoso-sample-hub >
Diagnostics setting &
EE Seve X Discard Delete ©) Provide feedback:
[A diagnostic setting specifies lst of categories of platform logs and/or metrics that you want to collect fom a resource, and one or more:
destinations that you would stream them to. Normal usage charges for the destination will occur. Learn more about the different log
categories and contents of those logs
Disgnestic setting name *
Category desis Destination deta
og Ey Send to Log Analytics
GD connections Subscription
intemal use v
1 cevicetelemetny
Log Analytics workapace
0 czocommanse [[contoso-tampe-hub-lasworkspace (eanwalus] a]
Ty devietentiyoperons Darcie so storage acount
FeUplosdOperations
O ievncaconers [1 steam to an evert hub
i seutes
1 oactwinopertons
1 caotwinoperatons
1 twinqueries
[1 sovsoperations
1 ovrectmetnods
1 oietioutearacing
CO configurations
(1 eviesteams
By Ainesis](https://eaeastus2.blob.core.windows.net/optimizedimages/static/images/Microsoft-Azure-IoT-Developer-(AZ-220)/answer/imgckeditor_40.png)
References:
The solution of using Connections and Device telemetry logs and sending them to the Log Analytics via diagnostic settings in the IoT hub can provide some benefits, but it may not be sufficient to achieve all the goals for troubleshooting and analysis purposes.
The Connections log provides insights into the communication between the devices and the IoT hub. It includes information about the connection status, the time taken for connections, the error messages, etc. This log can be useful for monitoring the health of the IoT hub, identifying connectivity issues, and diagnosing errors.
The Device telemetry logs contain the telemetry data sent by the devices to the IoT hub. It includes information about the device ID, timestamp, message type, and payload. This log can be useful for monitoring the telemetry data, identifying anomalies, and detecting issues with the devices or the data.
Sending these logs to Log Analytics via diagnostic settings in the IoT hub can provide a central location to store and analyze the logs. It can enable real-time monitoring, alerting, and visualization of the data.
However, depending on the complexity of the industrial IoT solution and the troubleshooting needs, this solution may not be sufficient. For example, if the issues are related to the network, the infrastructure, or the application, the logs from other sources such as the virtual machines, the gateways, or the services may be required. In such cases, additional diagnostic settings may need to be configured to collect the relevant logs.
Moreover, the analysis of the logs may require advanced tools and techniques such as machine learning, anomaly detection, or root cause analysis. These tools may need to be integrated with the Log Analytics or used separately to gain deeper insights into the data.
In summary, while using Connections and Device telemetry logs and sending them to the Log Analytics via diagnostic settings in the IoT hub can provide some benefits for troubleshooting and analysis purposes, it may not be sufficient for all scenarios. The solution needs to be tailored to the specific needs of the industrial IoT solution and may require additional logs, tools, and techniques.
