Merge pull request #95562 from vavilla/rules-deep-dive

Added a document describing how rule aggregation, multiple conditions, and rules on edge modules work

Author: TedA-M

articles/iot-central/core/tutorial-monitor-devices.md

@@ -75,4 +75,4 @@ In this tutorial, you learned how to:
 > * Investigate an issue
 > * Remediate an issue
 
-Now that you know now to monitor your device, the suggested next step is to [Add a device](tutorial-add-device.md).
+Now that you know now to monitor your device, the suggested next step is to [Add a device](tutorial-add-device.md).

articles/iot-central/preview/howto-configure-rules.md

@@ -0,0 +1,50 @@
+---
+title: Configure rules and actions in Azure IoT Central | Microsoft Docs
+description: This how-to article shows you, as a builder, how to configure telemetry-based rules and actions in your Azure IoT Central application.
+author: vavilla
+ms.author: vavilla
+ms.date: 11/11/2019
+ms.topic: conceptual
+ms.service: iot-central
+services: iot-central
+manager: philmea
+---
+
+# Configure rules (preview features)
+
+[!INCLUDE [iot-central-pnp-original](../../../includes/iot-central-pnp-original-note.md)]
+
+*This article applies to operators, builders, and administrators.*
+
+Rules in IoT Central serve as a customizable response tool that trigger on actively monitored events from connected devices. The following sections describe how rules are evaluated.
+
+## Select target devices
+
+Use the target devices section to select on what kind of devices this rule will be applied. Filters allow you to further refine what devices should be included. The filters use properties on the device template to filter down the set of devices. Filters themselves don't trigger an action. In the following screenshot, the devices that are being targeted are of device template type **Refrigerator**. The filter states that the rule should only include **Refrigerators** where the **Manufactured State** property equals **Washington**.
+
+![Conditions](media/howto-configure-rules/filters.png)
+
+## Use multiple conditions
+
+Conditions are what rules trigger on. Currently, when you add multiple conditions to a rule, they're logically AND'd together. In other words, all conditions must be met for the rule to evaluate as true.  
+
+In the following screenshot, the conditions check when the temperature is greater than 90 and the humidity is less than 10. When both of these statements are true, the rule evaluates to true and triggers an action.
+
+![Conditions](media/howto-configure-rules/conditions.png)
+
+## Use aggregate windowing
+
+Rules evaluate aggregate time windows as tumbling windows. In the screenshot below, the time window is five minutes. Every five minutes, the rule evaluates on the last five minutes of data. The data is only evaluated once in the window to which it corresponds.
+
+![Tumbling Windows](media/howto-configure-rules/tumbling-window.png)
+
+## Use rules with IoT Edge modules
+
+A restriction applies to rules that are applied to IoT Edge modules. Rules on telemetry from different modules aren't evaluated as valid rules. Take the following as an example. The first condition of the rule is on a temperature telemetry from Module A. The second condition of the rule is on a humidity telemetry on Module B. Since the two conditions are from different modules, this is an invalid set of conditions. The rule isn't valid and will throw an error on trying to save the rule.
+
+## Next steps
+
+Now that you've learned how to configure a rule in your Azure IoT Central application, you can:
+
+> [!div class="nextstepaction"]
+> [Analyze your data on the fly](howto-create-analytics.md)

articles/iot-central/preview/media/howto-configure-rules/conditions.png

@@ -71,6 +71,8 @@
           href: howto-version-device-template.md
         - name: Manage your devices
           href: howto-manage-devices.md
+        - name: Configure rules
+          href: howto-configure-rules.md
         - name: Analyze your device data
           href: howto-create-analytics.md
         - name: Add tiles to your dashboard