I covered on how to connect an MXChip Devkit to Azure IoT Central and if you haven’t gone through that article you can have a look at it here
In this article, we will look at setting up Rules in Azure IoT Central to monitor the telemetry emitted from the MXChip. This will help trigger actions such as sending an email can automatically be invoked in the event of a device anomaly e.g an increase in Temperature.
Create a Rule
Step 1: Log in to Azure IoT Central App
Step 2: Navigate to Rules menu in the Azure IoT Central App.
Step 3: Click on the New Button to create a new Rule
Step 4: Provide the following parameters
- 1 – Provide a Name to the rule
- 2 – Ensure the Rule is set to “Enable“
- 3 – Select the appropriate device if you have multiple templates.
- 4 – Create the condition by selecting the telemetry type, operator and the value. In my example, my condition will trigger once the temperature value is greater than 27 degrees.
- 5 – Select the Action that should be taken upon triggering the above rule. Currently, there are only 3 Actions available which are
- Webhook: When the conditions of the rule are met, a POST request will be sent to the callback URL you provide. Click on the following link to learn further on how to create a Webhook
- Email: Send an email to a specified list of users when your rule is triggered.
- Azure Monitor Action Groups: Use Azure Monitor action groups to trigger a list of actions including SMS and Voice. Click on the following link to learn further on how to link Azure Monitor Action Groups with Azure IoT Central Alerts.
In summary, you can get started with some great Alerting options with Azure IoT Central especially around the Webhook and Azure Monitor Action Groups, you can create some cool notification functions where the Alerts are created in Dynamics 365 Field Services. So your imagination is the limit 🙂
As always I hope this article will become useful in your Azure IoT journey. Have fun and let me know if you have any questions.