Help: Notifications
© GHIT ApS
DomainScan - Server monitoring
 
   

Notifications are created by DomainScan when noticeable situations occur; such as detection of new devices or users or a scanning error on a device.
Furthermore, one can manually enable other notifications. One example is the event file, which DomainScan can check the size of, and create a notification if the size of the event file is larger than a given value.

Notifications can be seen in this utility, and device or user specific notifications can also be seen in the device or user information windows.

One can also forward notifications to a mail recipient, which can be set up in Mail forwarding.

Overview up


In the overview page, all notifications can be seen.

One can double click on device and user notifications, and the device or user information window will appear.

Notifications from DomainScan (system notifications) cannot be double clicked, and these notifications are marked with a yellow circle.

Tip
One can choose to ignore notifications.

To do so, right click on a notification, and select Ignore

Setup up


Enable notifications
Set whether or not notifications are enabled.

Note
Notifications use license units. See License unit usage for the exact amount.

Notification targets
With this matrix, one can decide where notifications are delivered.

There are three targets:

Information logNotifications are stored internally in the DomainScan database, and can be seen in the information page in the main window.
Event fileNotifications are stored in the event.csv file (as long as the event file option is enabled in setup.
MailNotifications are also sent to one or more mail recipients. Recipients are to be defined in Mail forwarding

Furthermore, notifications are grouped by their origin, and can be one of the following:

Device notificationsNotifications that are created by a device.
User notificationsNotifications that are created by a user.
Domain notificationsNotifications that are created by a domain.
System notificationsNotifications that are created by DomainScan.
OK notificationsNotifications that are created by a Monitor, when an event has been cleared.
Task deadlinesNotifications that are created when a task deadline has been reached.

By default, the entire matrix is checked, but one can set the matrix as one desire.

Mail forwarding up


Here, one can specify one or more mail recipient where notifications are to be sent.
Notifications are sent at the end of each scan cycle, and all notifications are placed in a single mail. An example can be seen below:

Note
Multiple mail recipients must be delimited by a comma, and the mail-server must be defined in Setup.

Example:

Notification

Event time: 2008-12-30 10:02

Message from FileServer01:


Task deadline!

Deadline: 2008-12-12 17:46

The task is assigned to John Doe

 



Notification

Event time: 2008-12-30 10:02

Message from MSMailServer:


Task deadline!

Deadline: 2008-12-19 17:46

The task is assigned to administrator

 



DomainScan. 2008.12.30, 10:07:04


System notifications up


Notify if the service log is larger than
Set this option to let DomainScan check the size of the service log. If the size exceeds the given value, then a Notification will be created.

Notify if the event log is larger than
Set this option to let DomainScan check the size of the event log. If the size exceeds the given value, then a Notification will be created.

Notify when the amount of used license units has reaced # % of available license units
If this option is set, then DomainScan will check if the number of used license units exceeds the given value.

It is particular important to take care of license unit saturation problems, due to the fact that DomainScan will not function properly if all license units are used. For instance; new devices cannot be added to the database or monitors may fail to execute.


  2003 - 2012 GHIT ApS (Formerly GH Software). Contact