66
Log To Syslog
- Record notifications to system logs; the Verbosity of notifications can be configured.
Logging
– Records notifications to server logs; the
Verbosity
of notifications can be configured. For this feature to
work correctly, you must enable logging in the ERA Server (
Tools
>
Server Options
>
Logging
).
The notification format can be edited in the
Message
box in the bottom section of the Notification Manager main
window. In the text you can use special variables, using this syntax:
%VARIABLE_NAME%
. To view the list of available
variables, click
Show me options
.
Server_Last_Updated
– Last update of the server
Primary_Server_Name
Rule_Name
Rule_Description
Client_Filter
– Client filter parameters
Client_Filter_Short
– Client filter settings (in short form)
Client_List
– List of clients
Triggered
– Date of the most recent notification sent (repeats excluded)
Triggered Last
– Date of the most recent notification sent (repeats included)
Priority
– Notification rule priority
Log_Text_Truncated
– Log text that activated the notification (truncated)
Task_Result_List
– List of finished tasks
Parameters
– Rule parameters
Last_Log_Date
– Date of the last log
License_Info_Merged
– License information (summary)
License_Info_Full
– License information (full)
License_Days_To_Expiry
– Days left until expiration
License_Expiration_Date
- nearest expiration date
License_Clients_Left
– Free slots in the current license for clients to connect to the server
License_Customer
- license customer (merged)
Actual_License_Count
– Number of clients currently connected to the server
Virus_Signature_Db_Version
- Latest virus signature database version
Pcu_List
- Latest Program Component Update list
The last parameter to be specified is time and date. Activation of the rule can be delayed to a time period ranging from
one hour to three months. If you wish to activate the rule as soon as possible, set the
Activation after
drop-down
menu to
ASAP
. The Notification Manager is activated every 10 minutes by default, so if you select
ASAP
, the task
should run within 10 minutes. If a specific time period is selected from this menu, the action will automatically be
performed after the time period has elapsed (provided that the rule condition is met).
The
Repeat after every…
menu allows you to specify a time interval after which the action will be repeated. However,
the condition to activate the rule must still be met. In
Server
>
Advanced
>
Edit Advanced Settings
>
ESET Remote
Administrator
>
Server
>
Setup
>
Notifications
>
Interval for notification processing (minutes)
you can specify the
time interval in which the server will check and execute active rules.
The default value is 10 minutes. We do not recommend decreasing it, since this may cause significant server slowdown.
By default, the Notification Manager window contains predefined rules. To activate a rule, select the check box next to
the rule. The following notification rules are available. If they are activated and the rule conditions are met, they
generate log entries.
More than 10% of primary clients are not connecting
– If more than 10 percent of clients have not connected to
the server for more than a week; the rule runs ASAP.
More than 10% of primary clients with critical protection status
– If more than 10 percent of clients generated
a Protection status critical warning and have not connected to the server for more than a week; the rule runs ASAP.
Primary clients with protection status warning
– If there is at least one client with a protection status warning that
has not connected to the server for at least one week.
Primary clients not connecting
– If there is at least one client that has not connected to the server for more than
one week.
Primary clients with outdated virus signature database
– If there is a client with a virus signature database two or
more versions older than the current one and has not been disconnected from the server for more than one week.
Primary clients with critical protection status
– If there is a client with a critical protection status warning that has
not been disconnected for more than one week.
Primary clients with newer virus signature database than server
– If there is a client with a newer virus signature