[Index]

Model: data/Alert

Alerts

An Alert list can be exposed on the GUI by adding the data/Alert model to the administrator menu. This will enable an administrator to inspect the list of alert messages.

The Alert list is summarized by:

• ID: A reference to the source of the alert. Alerts with the same ID and code will update the count of this alert as well as the last time that the alert occurred. This means that a single alert is shown on the list for each alert with the same ID and code.
• alert code: an error or warning code associated with the alert
• alert category: A specific category to which the alert belongs, for example: "Device Change Notification Collector".

Administrators can also filter alerts by any of these fields.

When features are enabled to send alert messages, these are recorded in the list. Each alert also has such properties as a severity (Error, Warning or Info), the number of times that the same alert has been raised and the time stamp of the last alert instance. See: Field Reference for data/Alert.

When an alert is raised, the Notifications indicator on the main user interface will show this. Clicking the Notifications button will show a message in red that alerts have been raised: "There are one or more alerts. Click here to view them." When clicking on this message, the user is directed to the list of alert messages.

Alert messages can be inspected and then acted upon by the administrator. If an issue that raised the alert has been resolved, the administrator can delete the alert from the list. If no alerts are present in the list, no notification is shown.

Enable Database Scheduling

If any of the following messages are shown upon login or when typing health login, the steps below should be carried out:

• CACHE DATABASE MAINTENANCE NOT SCHEDULED
• TRANSACTION DATABASE MAINTENANCE NOT SCHEDULED

For general information on scheduling, see: Scheduling.

For considerations and guidance on frequency of the schedule to set up for your system. see the System Maintenance section of the Best Practices Guide.

• For cache database maintenance:

  With for example a schedule name dbcache:

  schedule add dbcache voss trim-cache

  See also Database Commands

  Typing health login at the command line will now not show the CACHE DATABASE MAINTENANCE NOT SCHEDULED message.

  The schedule instance can be modified, for example every 24 hours:

  schedule time dbcache every 24 hours

• For transaction database maintenance:

  With for example a schedule name dbtxn:

  schedule add dbtxn voss transaction archive 7

  or

  schedule add dbtxn voss transaction delete 7

  Note that transaction archiving also deletes transactions. For further details, see Database Commands for Transaction Management

  Typing health login at the command line will now not show the TRANSACTION DATABASE MAINTENANCE NOT SCHEDULED message.

  The schedule instance can be modified, for example weekly on Sunday:

  schedule time dbtxn weekly 0

Used to inform admin users when a note-worthy event takes place on the system

Model Details