Notification Configuration |
To configure notifications on anti-virus network events 1.Select the item in the main menu of the Control Center. In the opened window, select in the control menu. 2.Notifications are configured separately for each Control Center administrator. The name of the administrator whom notifications are displayed is given in the field. To configure notifications for another administrator, click and select the administrator in the opened window. 3.At initial setup, one default notifications blocks (profiles) is added for the main administrator. If the administrator notification list is empty, click in the section. 4.To enable notifications sending, set the switch on the left of the notifications block header to the corresponding position: —notifications sending for this block is enabled. —notifications of this block are not sent. 5.In this section, you can create several notifications blocks (profiles), e.g., for the different sending methods. To add one more block, click on the right of the notifications block settings. At the bottom of the page, one more notifications block will be added. Configuration of different notifications blocks as their templates texts is performed independently. 6.In the field, specify the name of added notifications block. This name is used, e.g. in configuration of the in the Server schedule. Further, to edit the header, click it and type necessary name. If you have more than one notification blocks, when you click the header text, the drop-down list with headers of existing notifications blocks will be prompted. 7.To configure notifications sending, select necessary type for notifications sending from the drop-down list: •Dr.Web Agent—send notifications via the Agent protocol. •Email—send notifications on email. •Push-notifications—send push notifications to Dr.Web Mobile Control Center. This option is available in the drop-down list only after Dr.Web Mobile Control Center has been connected to this Dr.Web Server. •SNMP—send notifications via the SNMP protocol. •Web console—send notifications for viewing in the Web console. Settings description for each type of notifications sending is given in this section below. 8.In the notifications list, set the flags next to those notifications that will be sent according to the send method of current notifications block. 9.For the Server notifications sending, the predefined set of text messages is provided.
To configure concrete notification, do the following: a)To switch into editing mode of the notifications settings, click on the section header. b)To change notifications settings, click a notification you want to edit. Notification template will be opened. If necessary, edit the text of notification to send. In the notification text you can use template variables (in braces). To add variables, use drop-down lists on the message header. When a message is being generated, the system replaces template variables with a certain text, which depends upon its current parameters. The list of available variables is given in the document, in p. Appendix D3. The Parameters of the Notification System Templates. c)For email notifications, you are provided to add arbitrary user-defined fields in the additional section, in the template editor for each notification (see step ). Headers must be formed according to the RFC 822, RFC 2822 standards and must not match with fields defined in the email standards. Particularly, the RFC 822 standard guarantees that specification does not contain headers started with X-, thus it is recommended to set the names in the following format: Х-<header-name>. For example: X-Template-Language: English. d)For notifications from the subsection, you can set the list of stations on the events on which notifications will be send. In the template editing window, in the tree, select groups of stations to monitor events and send corresponding notifications. To select several groups, use ctrl or shift. e)To exit the notification editing mode, click on the section header.
10.After editing, click to apply all specified changes. Notifications via the Agent Protocol
For notifications via the Agent protocol, specify the following parameters: •In the section, specify the settings for notifications resends performed by Dr.Web Server when failed to send a message: ▫—the number of retries performed by Dr.Web Server when failed to send a message. Default is 10. ▫—period in seconds after which Dr.Web Server repeats the attempt to send a message. Default is 300 seconds. •—identifier of a station to which notifications must be send. You can view station identifier in the stations properties. •—send the test message according to the specified settings of notification system. For notifications on email, specify the following parameters: •In the section, specify the settings for notifications resends performed by Dr.Web Server when failed to send a message: ▫—the number of retries performed by Dr.Web Server when failed to send a message. Default is 10. ▫—period in seconds after which Dr.Web Server repeats the attempt to send a message. Default is 300 seconds. •—email addresses of notifications receivers. Only one email address of a receiver per each field. To add one more receiver field, click . To remove the field, click .
•—send the test message according to the specified settings of notification system. For Push notifications which are sent to Mobile Control Center, specify the following parameters: •In the section, specify the settings for notifications resends performed by Dr.Web Server when failed to send a message: ▫—the number of retries performed by Dr.Web Server when failed to send a message. Default is 10. ▫—period in seconds after which Dr.Web Server repeats the attempt to send a message. Default is 300 seconds. •—send the test message according to the specified settings of notification system. Notifications via the SNMP Protocol For notifications via the SNMP protocol, specify the following parameters: •In the section, specify the settings for notifications resends performed by Dr.Web Server when failed to send a message: ▫—the number of retries performed by Dr.Web Server when failed to send a message. Default is 10. ▫—period in seconds after which Dr.Web Server repeats the attempt to send a message. Default is 300 seconds. •In the section, specify the settings for notifications resends performed by SNMP subsystem when failed to send a message: ▫—the number of retries performed by SNMP subsystem when failed to send a message. Default is 5. ▫—period in seconds after which SNMP subsystem repeats the attempt to send a message. Default is 5 seconds. •—entity that receives SNMP request. For example, IP address or DNS name. Only one receiver per each field. To add one more receiver field, click . To remove the field, click . •—entity that sends SNMP request. For example, IP address or DNS name (must be able to be solved by DNS server). If the sender is not set, defaults are: “localhost” for Windows and “” for UNIX. •—SNMP community or context. Default is public. •—send the test message according to the specified settings of notification system.
Notifications Displayed in the Web Console For notifications displayed in the Web console, specify the following parameters: •In the section, specify the settings for notifications resends performed by Dr.Web Server when failed to send a message: ▫—the number of retries performed by Dr.Web Server when failed to send a message. Default is 10. ▫—period in seconds after which Dr.Web Server repeats the attempt to send a message. Default is 300 seconds. •—time period for storing a notification starting from its receiving. 1 day is by default. After specified period, notification is marked as outdated and deleted according to the task in the Server schedule settings. For notifications that received by this sending method, you can specify unlimited storing time in the Web Console Notifications section. •—send the test message according to the specified settings of notification system. |