Set Up Alert Triggers

note the user interface below is for manufacturing connect version 2 26 0 and later you can add a user alert trigger for edge devices in the triggers section in the alerts module 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 2zmaxafw8faxd bhwsep6 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 note when a google cloud platform (gcp) marketplace deployed manufacturing connect is upgraded (see install / upgrade manufacturing connect docid\ yhwg58leb5hm4g507yeg0 ) from an earlier version to version 2 10 0, metrics based alerts will not function these gcp marketplace deployed manufacturing connect instances must be backed up, reinstalled and restored (see export/import docid\ zot8ip7rkoxfup5ahtqo and install / upgrade manufacturing connect docid\ yhwg58leb5hm4g507yeg0 ) for metrics based alerts to function 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 manufacturing connect, 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 to set up a metrics source from the select alert template drop down list, select an alert template the options are connector disk buffer | integration connector online status | integration dh device online status | device hub dh device data quality | device hub edge device online status | edge device edge device license expiration | edge device edge device free disk space | edge device edge device memory available | edge device edge device cpu idle | edge device for the alert template you've chosen, for each of it's respective fields, enter a respective value 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 9b5tzo8ofqtj9yqthbomz 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 7ixsk58nhrpyc8hj ax73 (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 in manufacturing connect version 2 13 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 manufacturing connect 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 check box to set an active trigger flag (optional) click the dashboard check box to show trigger alerts on dashboard in the description field, enter a description for the trigger in the subject field, select one or more variables in manufacturing connect version 2 13 0 and later, you can enter your preferred text in addition to selected variables in the message field, select one or more variables in manufacturing connect version 2 13 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 from the scope section, select an option all edge devices edge device from the edge device drop down list, select an edge device instance metrics define alerts for expiring api tokens 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