This
After login, the Admin Notifier displays a banner if any of the filtered events are found so that you can take action on the issues immediately.
This
How Does the Admin Notifier Work?
When certain events are present that could lead to a system outage, the Admin Notifier appears in SL1 for administrator users at login and persists as a banner at the top of the screen until no qualifying events are found. The Admin Notifier monitors your SL1 appliances for the events listed in the table in What Issues Does the Admin Notifier Monitor?
If you are using the classic SL1 user interface, the Admin Notifier has additional functions. See Admin Notifier in the Classic SL1 User Interface.
After logging in to SL1, administrators will see the following modal if qualifying events are found:
Click to continue or click to go to the Events page to see a view filtered by admin events.
The System Warning banner will persist across the user interface until all of the qualifying events have been acknowledged.
To interact with the banner, you can click one of the buttons that appears on the banner:
- Dismiss. Hides the banner for the duration of your session or until another qualifying event is logged. If qualifying events are still present, the banner will reappear upon your next login.
- Snooze. Hides the banner for 15 minutes. If qualifying events are still present after 15 minutes, the banner will reappear.
- View Events. Opens the Events page with a filter applied that shows only the admin events.
Admin Notifier in the Classic SL1 User Interface
The System Warning banner appears as shown below in the classic user interface:
In the classic user interface, you can select events to add to or remove from the System Warning banner. On the Event Policy Manager page (Registry > Events > Event Manager), the Select Action menu on the Event Policy Manager page includes the following options: Enable Admin Banner Warning and Disable Admin Banner Warning for selected events.
The Event Policy Manager page also includes a new Admin Warning column that specifies whether or not an event will be included in the System Warning Banner.
What Issues Does the Admin Notifier Monitor?
The following table includes the events that might appear in the Admin Notifier, the Dynamic Application that triggers the event, the severity of the event, and references that can help you resolve the problem before it causes an outage. Knowledge Base Articles (KBA) are found on the ScienceLogic Support website (https://support.sciencelogic.com/s/knowledge).
| Event Name | Dynamic Application | Severity | Reference |
|---|---|---|---|
| Support: Database Config - License expires in less than 14 days | Support: Database Configuration | Critical | Renew license. See |
| Support: DRBD Proxy License Expiration Eminent | Support: DRBD Proxy License Expiration | Critical | Renew license. See |
| InnoDB Space: Critical Threshold | Support: InnoDB Size | Critical | See Device Thresholds and Retention or |
| Support: SL1 Config - Appliance Not Licensed | Support: SL1 Configuration | Critical | License your SL1 appliance. See |
| Support: MariaDB Config - InnoDB Force Recovery Non-Zero Value | Support: MariaDB Configuration | Critical | See |
| Poller: File system usage exceeded (critical) threshold | Internal | Critical | See |
| Support: Appliance Validation Not Monitored | Support: Appliance Validation | Major | Discover all appliances as devices. |
| Support: Appliance Validation Minimum AIO Requirements Not Met | Support: Appliance Validation | Major | See |
| Support: Appliance Validation Minimum AP Requirements Not Met | Support: Appliance Validation | Major | See |
| Support: Appliance Validation Minimum DB Requirements Not Met | Support: Appliance Validation | Major | See |
| Support: Appliance Validation Minimum DC Requirements Not Met | Support: Appliance Validation | Major | See |
| Support: Appliance Validation Minimum MC Requirements Not Met | Support: Appliance Validation | Major | See |
| Support: API Message Backlog Has Exceeded Threshold | Support: Async Message Backlog Performance | Major | See |
| Support: Syslog Message Backlog Has Exceeded Threshold | Support: Async Message Backlog Performance | Major | See |
| Support: Trap Message Backlog Has Exceeded Threshold | Support: Async Message Backlog Performance | Major | See |
| Support: Cluster Resource Template Outdated | Support: Cluster Configuration | Major | See |
| Support: DNS Resolution - Invalid Response | Support: Database Configuration | Major | See |
| Support: SL1 will run out of space in less than 14 days | Support: DB Space Estimator | Critical | See |
| Mail Backlog: Critical | Support: Mail Backlog | Critical | See |
| Support: MariaDB Config - File per table | Support: MariaDB Configuration | Critical | See |
| Support: MariaDB Connections High - Critical | Support: MariaDB Performance | Critical | See |
| Support: High Rows Behind High | Support: Rows Behind | Critical | See |
| Support: Medium Rows Behind High | Support: Rows Behind | Major | See |
| Siteconfig Check: Differing Variable | Support: Siteconfig Check | Critical | See |
| Siteconfig Check: Missing Variable | Support: Siteconfig Check | Critical | See |
| Support: SL1 Config - Bad Timezone | Support: SL1 Configuration | Critical | Reset timezone to UTC. See |
| Support: SL1 Config - Pause file detected | Support: SL1 Configuration | Critical | The system is not currently collecting any information. See |
| Support: Out of Memory - Process Has Been Killed | Syslog | Major | See |
| Support: MariaDB Error | Syslog | Major | See |