Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| en:dpi:qoe_analytics:qoe_gui:offline_analytics:triggers_and_notifications [2025/11/01 10:40] – elena.krasnobryzh | en:dpi:qoe_analytics:qoe_gui:offline_analytics:triggers_and_notifications [2025/11/01 10:47] (current) – elena.krasnobryzh | ||
|---|---|---|---|
| Line 26: | Line 26: | ||
| Also in this block there is a switch to enable/ | Also in this block there is a switch to enable/ | ||
| - | <note tip> | + | <note tip> |
| ==== Step 2: Select a data source and metrics ==== | ==== Step 2: Select a data source and metrics ==== | ||
| Select a metric and data table. Triggers only work with ready-made tables found in Netflow and Clickstream, | Select a metric and data table. Triggers only work with ready-made tables found in Netflow and Clickstream, | ||
| Line 38: | Line 38: | ||
| For each query, you can create a filter where you can set the value of IP host, subscriber login, etc. For example, you can customize the generation of a report or notification for one specific host, if you set the filter like this: | For each query, you can create a filter where you can set the value of IP host, subscriber login, etc. For example, you can customize the generation of a report or notification for one specific host, if you set the filter like this: | ||
| - | {{ :en:dpi:dpi_components:dpiui:user_guide: | + | {{ :en:dpi:qoe_analytics:qoe_gui:offline_analytics: |
| - | <note tip> | + | <note tip> |
| - | \\ \\ Example of filling out the block for notification about subscribers with cyber threats. Here you need to select the report “Top infected subscribers with botnet traffic”, it has the required metrics for this trigger. In this case, the data for the last 24 hours will be analyzed.\\ {{:en:dpi:dpi_components:dpiui:user_guide: | + | \\ \\ Example of filling out the block for notification about subscribers with cyber threats. Here you need to select the report “Top infected subscribers with botnet traffic”, it has the required metrics for this trigger. In this case, the data for the last 24 hours will be analyzed.\\ {{:en:dpi:qoe_analytics:qoe_gui:offline_analytics: |
| ==== Step 3: Conditions ==== | ==== Step 3: Conditions ==== | ||
| Set conditions – what should happen to the metric to run the trigger. \\ | Set conditions – what should happen to the metric to run the trigger. \\ | ||
| Line 62: | Line 62: | ||
| * Value – assign the required value for the condition. | * Value – assign the required value for the condition. | ||
| - | <note tip> | + | <note tip> |
| \\ In this case, the trigger will go off if the RTT value from the subscriber is greater than or equal to 150000 ms in the table from step 2.\\ \\ Example of filling out the block for alerts about subscribers with cyber threats: | \\ In this case, the trigger will go off if the RTT value from the subscriber is greater than or equal to 150000 ms in the table from step 2.\\ \\ Example of filling out the block for alerts about subscribers with cyber threats: | ||
| - | \\ {{:en:dpi:dpi_components:dpiui:user_guide: | + | \\ {{:en:dpi:qoe_analytics:qoe_gui:offline_analytics: |
| Line 75: | Line 75: | ||
| * “Ok” – the conditions set in the trigger did not work, everything is fine, and no actions needed. | * “Ok” – the conditions set in the trigger did not work, everything is fine, and no actions needed. | ||
| - | <note tip> | + | <note tip> |
| Line 87: | Line 87: | ||
| - Start BotFather with the ''/ | - Start BotFather with the ''/ | ||
| - | - Type ''/ | + | - Type ''/ |
| - | - Enter the name of the bot.\\ {{:en:dpi:dpi_components:dpiui:user_guide: | + | - Enter the name of the bot.\\ {{:en:dpi:qoe_analytics:qoe_gui:offline_analytics: |
| - | - Enter a unique '' | + | - Enter a unique '' |
| - Copy the HTTP API access token from the bot registration message, it looks like this: '' | - Copy the HTTP API access token from the bot registration message, it looks like this: '' | ||
| - | - Paste the copied token into the GUI settings (Administrator → GUI Configuration → Telegram Settings → Telegram bot API token). \\ {{:en:dpi:dpi_components:dpiui:user_guide: | + | - Paste the copied token into the GUI settings (Administrator → GUI Configuration → Telegram Settings → Telegram bot API token). \\ {{:en:dpi:qoe_analytics:qoe_gui:offline_analytics: |
| **Step 2: Get a chat ID for your personal Telegram account via https:// | **Step 2: Get a chat ID for your personal Telegram account via https:// | ||
| Line 109: | Line 109: | ||
| Add the ID from step 2 to the Telegram action in the "Chat ID" field.\\ | Add the ID from step 2 to the Telegram action in the "Chat ID" field.\\ | ||
| - | {{:en:dpi:dpi_components:dpiui:user_guide: | + | {{:en:dpi:qoe_analytics:qoe_gui:offline_analytics: |
| === E-Mail === | === E-Mail === | ||
| Line 116: | Line 116: | ||
| - If you click on the “Template parameters” button (2), it will open a menu with identifiers that can be used to compose the message. | - If you click on the “Template parameters” button (2), it will open a menu with identifiers that can be used to compose the message. | ||
| - | {{:en:dpi:dpi_components:dpiui:user_guide: | + | {{:en:dpi:qoe_analytics:qoe_gui:offline_analytics: |
| For E-mail actions to work, you need to configure SMTP. Go to Administrator → GUI Configuration, | For E-mail actions to work, you need to configure SMTP. Go to Administrator → GUI Configuration, | ||
| Line 125: | Line 125: | ||
| - Clicking on the “Template Options” button (2) opens a menu with identifiers that can be used to compose the message. | - Clicking on the “Template Options” button (2) opens a menu with identifiers that can be used to compose the message. | ||
| - | {{:en:dpi:dpi_components:dpiui:user_guide: | + | {{:en:dpi:qoe_analytics:qoe_gui:offline_analytics: |
| ---- | ---- | ||
| Line 131: | Line 131: | ||
| After creating a trigger, click “Save”. On the “Triggers” dashboard, enable the necessary triggers. If the GUI page has not been refreshed – refresh the page in the browser or click the “Refresh” button. | After creating a trigger, click “Save”. On the “Triggers” dashboard, enable the necessary triggers. If the GUI page has not been refreshed – refresh the page in the browser or click the “Refresh” button. | ||
| - | {{:en:dpi:dpi_components:dpiui:user_guide: | + | {{:en:dpi:qoe_analytics:qoe_gui:offline_analytics: |
| ===== “Triggers and Notification” page elements description ===== | ===== “Triggers and Notification” page elements description ===== | ||
| Line 137: | Line 137: | ||
| This will open the section as shown in the image below. | This will open the section as shown in the image below. | ||
| - | {{:en:dpi:dpi_components:dpiui:user_guide: | + | {{:en:dpi:qoe_analytics:qoe_gui:offline_analytics: |