Docs for all releases
Page History
...
This section represents a built-in tool to monitor statistics and generate alerts, as well as block numbers, codes/code names, destinations, clients, or accounts, if accounts if some conditions are met. The section is presented in a the form of a table with the following columns:
...
Column | Description |
---|---|
ID | Identification number of a factors watcher |
Name | Name of a factors watcher |
Watch Rule | Total number of watch rules within a factors watcher |
Presets | Total amount of traffic rules, created by a factors watcher |
Query | Factors watcher query |
...
Field | Description | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Priority | Define a priority of rules execution if they have a similar Match parameter | |||||||||||
Match | A set of parameters that are used as a basis for checks | |||||||||||
Service | Determine the type of service (e.g., calls, SMSs, data) | |||||||||||
Origin | Type of route to check (Origination/Termination) | |||||||||||
Code Name | Indicate the code name to apply a rule to | |||||||||||
Gateways | Specify the gateway to apply a rule to | |||||||||||
| ||||||||||||
Factors | Enter factors that will be applied to a current rule. Parameters must be listed with a semi-colon “;” as a delimiting symbol. The list of parameters available for usage:
For example, if you enter total_volume > 100, it means that when the total event volume (e.g., call time) count for respective match parameters goes over 100 (here - minutes), the system will create an alert. It's possible to add a factors watcher rule with negative values. For example, total_cost < -10. | |||||||||||
Factors with a reference to the side-by-side reports: You can adjust these factors on your own, using the next formula and pre-existing factors mentioned above: factors_name_1 - value for the first period; factors_name_2 - value for the second period; factors_name_diff - the difference between periods. For example: total_cost_1 (of the 1st period), total_cost_2 (of the 2nd period), total_cost_diff (difference in %).
| ||||||||||||
Action | An action that must be taken if a matched rule is found. There are respective options: Alert, Block Code Name/Account/Client
| |||||||||||
Lock Period | Defines the lockout time in minutes for the analyzed route in case of a block action (0 value means infinite lockout) | |||||||||||
Periodic Lock | If enabled, the rule will expire at the end of a period specified in the Analyze interval of field in the Watcher settings. Please note, that this option has a higher priority than the Expiration Date. | |||||||||||
Expiration Date | Specify the date when the rule must be automatically deleted |
...