Set Up Alert Triggers

note the user interface below is for litmus edge manager version 2 10 1 and later you can add an alert trigger for edge devices in the triggers section in the alerts module review the following guides for setting up alert triggers create an email alert trigger for connector online status docid\ da gvxuepnyfpatssyhcq create an email alert trigger for devicehub device data quality docid\ keo0ctammo949dtzlgw7v important triggers require an action for notification implementation variables change depending on the source selected before you begin add an action to the action list to receive a notification see alerts docid\ bwq6obkutnzgijbigqpbe for details step 1 select and set up source completing the source section first avoids issues with the variables for the subject and message fields in the trigger section the source is the type of condition needed to trigger an alert to select a source select a source the options are metrics the trigger section's subject and message fields will be hidden and disabled events the trigger section's subject and message fields will be revealed and enabled click the add link to add a new rule the rule table drops down the rule table is dependent on your source selection step 1a set up metrics source select a metrics source to set up an alert that triggers based on metrics collected by litmus edge manager, specifically when the value of a variable is a certain desired value or certain set/interval of values you may create only one metrics rule per alert from the select alert template drop down list, select an alert template and enter a value for each of the respective parameters refer to the following table for more information on each alert template metrics name | source description / purpose parameters trigger condition (create an alert ) connector disk buffer | integration monitor integration docid\ wpqo1fe02tmx3askewqu6 connector disk buffer, which is used when the connector’s throughput is insufficient to handle all defined tags coming from edge devices target value in mb alert delay in seconds when the usage of integration docid\ wpqo1fe02tmx3askewqu6 connector disk buffer is above target value mb for more than alert delay seconds connector online status | integration detect unplanned integration docid\ wpqo1fe02tmx3askewqu6 connector disconnections alert delay in seconds when the integration docid\ wpqo1fe02tmx3askewqu6 connector is offline for more than alert delay seconds devicehub (dh) online status | devicehub detect unplanned disconnections of devicehub (dh) devices alert delay in seconds when the devicehub (dh) device is offline for more than alert delay seconds devicehub (dh) device data quality | devicehub monitor the rate of low quality (i e error) messages a high rate of low quality messages indicate a problem with either the physical device or the device driver target value in msgs/minute alert delay in seconds the rate of low quality messages for the dh device is above target value for more than alert delay seconds edge device online status | edge device detect unexpected disconnections of edge devices alert delay in seconds the edge device is offline for more than alert delay seconds edge device license expiration | edge device detect when the license of an edge device has expired target value in days alert delay in seconds when the license for an edge device is going to be expired in target value days for more than alert delay seconds edge device free disk space | edge device monitor the available disk space of an edge device target value in percentage alert delay in seconds when the free disk space is less than target value percent for more than alert delay seconds edge device memory available | edge device monitor the available memory of an edge device target value in percentage alert delay in seconds when the free ram is less than target value percent for more than alert delay seconds edge device cpu idle | edge device monitor the cpu usage of an edge device target value in percentage alert delay in seconds when the cpu idle is less than target value percent for more than alert delay seconds step 1b set up events source select an events source to set up an alert that triggers when a specific event occurs note the trigger for events in edge devices will only work if the forward events toggle is enabled for more details on events, refer to the events docid\ ons8mkwpvtkc93coorakm documentation to set up an events source from the severity drop down list, select an option all info warning alert from the component drop down list, select an option all cc integrations mp marketplace dh device hub auth auth dm device management from the event id drop down list, select an option options are dependent on the component selected see event id for user alert triggers docid\ gvkc02f1g ko9sruqxdyd (optional) click show event attributes for each of the event attributes, enter a value (optional) in the info field, enter a value repeat with additional new rules by clicking the add new rule button as needed step 2 set up trigger note for litmus edge manager version 2 14 0 and later, you can customize the subject and message of the trigger alert with your preferred text in addition to the variables you can customize the trigger's subject/message contents that will be sent to a recipient the visibility of the subject and message fields are dependent on the source selection from step 1 subject and message variables you can select from the following variables in the trigger subject and message $devicename the name of the associated edge device (for example litmus edge (08 00 23 18\ r5 32) $name the name of the associated connector or devicehub device (for example plc 2) $alertdelay the alert delay parameter configured for the trigger $value the current value associated with the connector or devicehub device that is being monitored (for example connector disk buffer of 98mb) $company the company associated with the edge device for the trigger $deviceid the associated edge device id (for example 9udklweoidslsdd0lksdjfslkd) $project the project associated with the edge device for the trigger $targetvalue the target value configured for the trigger (for example 50mb for connector disk buffer) $componentid the associated component for the event trigger cc integrations, mp marketplace, dh device hub, or auth auth $message the associated event message for the trigger $triggerid the associated trigger id $hostname the associated host name for the trigger $tags the associated tags for the trigger $severity the severity level selected for the trigger info, warning, or alert $triggername the name configured for the trigger $type the associated event type for the trigger $eventid the event id associated with the trigger to set up the trigger in the name field, enter a name for the trigger (optional) click the active checkbox to set an active trigger flag (optional) click the dashboard check box to show trigger alerts on the dashboard in the description field, enter a description for the trigger in the subject field, select one or more variables for litmus edge manager version 2 14 0 and later, you can enter your preferred text in addition to selected variables in the message field, select one or more variables for litmus edge manager version 2 14 0 and later, you can enter your preferred text in addition to selected variables step 3 set up scope you can customize the scope of the user triggers this will determine the applicable edge device(s) that will receive this alert trigger to set up the scope, select an option from the scope section all edge devices edge device from the edge device drop down list, select an edge device step 4 set up action you must create an action to use this section you can select the response action that will immediately occur after the alert is triggered to set up the action select an option from the action list drop down list (optional) select the continuously check box if you have checked continuously , enter a value in the notification period field in minutes click save the alert trigger appears in the trigger list important to continue receiving incident notifications for the same condition, you must resolve the current incident first after clicking resolve incident , a notification will be sent confirming the resolution