[Index]

Model: data/Alert

Alerts

Administrators can view alerts at the hierarchy level at which they are logged in, and the levels below that hierarchy. For example, if an alert is raised at the customer level, for example sys.hcs.provider.reseller.customer, then the provider, reseller, and customer administrators can see that alert but not site administrator. A Site administrator doesn't have access to view the alert. All administrators have read and delete permissions to the alerts.

When an alert is raised, the messages or notifications indicator on the Messages button will show this. Clicking the button will show a message 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.

The Alerts list can be viewed and managed on the Admin Portal from the Alerts list view (default menu Administration Tools > Alerts) or by clicking Messages on the top menu bar.

The Alert list is summarized by:

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.

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 the following message is shown upon login or when typing health login, the steps below should be carried out:

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.

Important

Schedules must be set up on all unified nodes. This ensures that they still run in the event of a failover and DR scenario.

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

Model Details: data/Alert

Title Description Details
ID * The unique ID of the alert
  • Field Name: alert_id
  • Type: String
Code * The code of the alert
  • Field Name: alert_code
  • Type: String
Category * The category of the alert
  • Field Name: alert_category
  • Type: String
Severity The severity of the alert
  • Field Name: alert_severity
  • Type: String
  • Choices: ["Error", "Warning", "Info"]
Message The message describing the alert
  • Field Name: alert_message
  • Type: String
Count The number of times this alert has occurred
  • Field Name: alert_count
  • Type: Integer
Latest Alert The last time this alert occurred
  • Field Name: alert_timestamp
  • Type: String
  • Format: date-time