System Alerting

Table of Contents

• Overview of Alerting
• Ongoing Alerts
• Transient Alerts

Back to the System Reference Manual Table of Contents

Overview of Alerting

Qorus alerts are situations that require attention from operators. There are two types of alerts:

• Ongoing Alerts
• Transient Alerts

The following system options pertain to alerts:

• alert-fs-full: the percentage above which an alert will be raised due to a full filesystem
• alert-smtp-connection: the name of the user connection for the SMTP server for delivering alert emails
• alert-smtp-enable: flag allowing alert emails to be enabled or disabled at runtime
• alert-smtp-from: source (from) email address for alert emails
• alert-smtp-interval: interval in seconds for grouping and delivering alert emails
• alert-smtp-to: list of email addresses for delivering alert emails
• dsp-warning-timeout: the amount of time in milliseconds for a transient alert to be raised if a connection cannot be allocated from a system datasource pool
• transient-alert-max: maximum number of transient alerts to cache

See also

/api/latest/system/alerts for information about the REST APIs related to Qorus system alerts

Ongoing Alerts

Ongoing alerts represent ongoing problems with the operation of the Qorus server or its interfaces that can be cleared if the underlying problem is resolved.

Transient Alerts

Transient alerts are one-time events that represent problems or potential problems with the operation of the Qorus server or its interfaces.