Notifications¶
Reference for the Notifications page of Preferences > Settings...: which events trigger email notifications and their thresholds.
Notifications are sent through the SMTP settings on the Email page; Enable email notifications? must be on.
Image of the Settings dialog, Notifications page, with the check boxes, thresholds and Alerts Error Email(s) field
../../images/admin/settings-notifications.png
Fields¶
| Field | Default | Range | What it does | Config key |
|---|---|---|---|---|
| Webi Real-Time Errors | Off | - | Notifies when the Web Intelligence real-time monitor encounters a problem | webi.rtm.error.notification |
| Notify when one or more cluster node members are offline | Off | - | Notifies when a BusinessObjects cluster node goes offline | alert.cluster.nodes.offline |
| Notify on any MM security changes | Off | - | Notifies when a MetaMiner user is added, deleted or changed | alert.on.any.user.changes |
| Excessive deletions notification threshold: | 3000 | 10 - 5000 | Number of objects deleted in one deletion scan that triggers a notification | deletions.warning.threshold |
| MMS Disk space remaining threshold: | 20 | 1 - 100 | Notifies when free space on the MetaMiner Server installation drive falls below this percentage | disk.space.remaining.pct |
| Alerts Error Email(s) | Empty | - | Sends failed alert notifications only to these addresses. Empty: failures go to the recipients set on each alert. When set, alert recipients defined in the MetaMiner Client never receive failure messages. | - |
Excessive deletions
A spike of deletions can mean content was really removed, or that the MetaMiner account lost access to part of the CMS. Investigate every excessive-deletions notification. On a busy system raise the threshold to avoid frequent notifications.
TODO: confirm Alerts Error Email(s) storage and default
The field's description in the product says empty means alert recipients are used. Product to confirm the stored key and that the field behaves as described in this release.