| Both sides previous revisionPrevious revision | |
| en:dpi:dpi_components:dpiui:user_guide:qoe_analytics:triggers_and_notifications:trigers:start [2022/02/14 15:01] – kuligina | en:dpi:dpi_components:dpiui:user_guide:qoe_analytics:triggers_and_notifications:trigers:start [2023/07/13 13:11] (current) – removed elena.krasnobryzh |
|---|
| ====== Triggers ====== | |
| {{indexmenu_n>1}} | |
| |
| To automate work with reports, use the "Triggers and Notification" menu. The tool can be fine-tuned to automatically inform about events related to a change in the metric of any states recorded in the database based on Clickstream and Netflow flows. | |
| |
| Creating a new trigger occurs in 5 stages: | |
| |
| - Set general trigger information: \\ Name (any unique) \\ Severity (choose severity level: information, warning, medium/high importance) \\ Days of the week (set which days the trigger will work) \\ Check frequency (timeout) between checks after the trigger is fired in minutes) \\ Number of triggers before notification (how many times the event should repeat) \\ Start/end date of the trigger \\ Start/end time of the trigger.\\ | |
| - Requests - in this field we select which metric and from which table to scan: \\ Report (select from tables: Netflow, Clickstream, raw full Netflow, raw full Clickstream; desired value) \\ Period from / to \\ {{ :dpi:dpi_components:dpiui:ugser_guide:qoe_analytics:metrics.png?nolink&600 |}} | |
| - Conditions - what should happen to the metric for the trigger to fire: \\ Relationship (and/or - match with the names of requests for the fulfillment of several conditions at once, or at least one of the specified ones) \\ Name (select one of the created requests) \\ Combinator (not/numeric, not/alphabetic, null value) \\ Operator (select: =, !=, >, >=, <, <=, between, not between.) \\ Value (assign unique value) \\ {{ :dpi:dpi_components:dpiui:ugser_guide:qoe_analytics:conditions.png?nolink&600 |}} | |
| - Error processing. In the fields “If there is no data”, “If there is an error or timeout”, assign a value: create a notification, save the last state, ok. | |
| - Actions. Create E-Mail/HTTP action, notification: \\ E-Mail action - creates a notification and sends it to the selected e-mail address (automatic email about the event can be edited). \\ To configure SMTP: go to MAIN MENU -> ADMINISTRATOR -> DPIUI2 (GUI) SERVER CONFIGURATION -> DPIUI2 (GUI) SERVER CONFIGURATION \\ {{ :dpi:dpi_components:dpiui:ugser_guide:qoe_analytics:configuration.png?nolink&600 |} } \\ Go to the SMTP settings section: SMTP SETTINGS \\ {{ :dpi:dpi_components:dpiui:ugser_guide:qoe_analytics:smtp-settings.png?nolink&600 |}} \\ HTTP action - creates a notification and sends it to the selected ticket- system (automatic event notification can be edited) \\ {{ :dpi:dpi_components:dpiui:ugser_guide:qoe_analytics:notification.png?nolink&600 |}} \\ Notification - creates a notification in DPIUI (automatic event notification can be edited) \\ {{ :dpi:dpi_components:dpiui:ugser_guide:qoe_analytics:notification-setup.png?nolink&600 |}} | |
| |
| After creating the trigger, click "Save". In the "Triggers and notification" window, enable the necessary triggers. If the DPIUI2 page has not been updated, refresh or click on the refresh icon, similar to the action menu. | |
| {{ :dpi:dpi_components:dpiui:ugser_guide:qoe_analytics:triggers.png?nolink&600 |}} | |
