Introduction

The following information is the description of system notification in CapaInstaller Management Solution.

At a configurative interval, CMS will scan the database for any potential problems, and create notifications for what is found. An example could be a service that has not updated its status for an hour.

In the lower right corner of the console, an indicator will show how many unsolved notifications exist, and how many of those have been read. It will flash red when new or unread notifications exist.

A notification does not necessarily mean an action needs to be taken. It is merely a tool to help give a better overview of the status of CMS, both recent and historic. It is important to check the timestamp and frequency of notification when trying to determine if it requires attention.

Notification Indicator

Shown in the lower right corner of the console. The number on the left represents the number of unread notifications. The number on the right shows the total unsolved notifications.

System Notification Form

This form will be shown when clicking on the indication icon described above.

e

Notifications in bold are unread. The ones that have been read can be hidden from this list by checking "Hide Read". Similar, solved notifications can be hidden/shown by checking "Hide Solved".

The same issue can be found in several scans of the system if the issue has not been solved since the last scan. When subsequent issues are created as notifications, they are linked to the original notification with a timestamp. The number of subsequent notifications can be seen in the

column and details about them can be seen by double-clicking the notification.
Changing the status will give you an opportunity to add a changelog comment, that can be seen in the bottom half of the notification form.

Right-clicking a notification will give the following options:

Element	Description
Mark as read	This will change the read status of the notification to read.
Mark as unread	This will change the read status of the notification to unread. Will be shown in bold.
Mark as solved	This will change the status of the notification from active to solved.
Delete	This will delete the notification and any that has been linked to it.
Refresh	This will refresh the view.
Show history details	This will open a new form, where more details about the notification can be found, as well as a list of subsequent notifications on the same issue.

Notification History Form

On this form details about the notification can be found, as well as a list of subsequent notifications on the same issue. When determining if two issues should be linked together, three properties are checked: Server, Event, and Type. If these are the same, the issues will be linked and shown here.

From the example above, it can be concluded that the sync service was originally detected as offline at 13.45, and the subsequent 6 systems scans with a 5-minute interval also registered it as offline. If this was read by an administrator at 17.00, he would be able to conclude that the service had been offline for about an hour, before it once again came online at around 14.20.

System Health Replicator Task

The System Health Replicator Task is a new global Replicator task that is configured in System Management. It can be accessed through a menu button below the Help menu. This will open the Global Replicator Tasks form shown below, where a Replicator can be assigned and an interval specified in minutes can be scheduled.

The System Health task is what performs the scan of the system, resulting in notifications of potential problems.