Overview

The Linux/SSH Restart Event Monitor connects to a remote server using SSH and checks for records that indicate there was a planned or unplanned system restart.

Use Cases

• Receiving alerts ASAP about planned and unplanned restarts
• Getting notifications when an administrator has added reasons for unplanned restarts

Monitoring Options

This event monitor provides the following options:

Alert with [Info/Warning/Error/Critical] if the device cannot be contacted

Use this option to control the type of notification you'll receive if the event monitor is unable to establish an SSH connection.

Alert with [Info/Warning/Error/Critical] if the device has been restarted (Planned)

Use this option to get notified of planned restarts.

Alert with [Info/Warning/Error/Critical] if the device has been restarted (Unplanned)

Enable this option to get alerted about unplanned restarts.

Alert with [Info/Warning/Error/Critical] when a reason has been entered by an administrator for an unplanned restart

This option will send an alert of your choice if an administrator has added a reason for an unplanned restart.

Alert with [Info/Warning/Error/Critical] if the device has not been restarted since the last check

Use this option to receive an alert if the connected device hasn't been restarted since the last time the event monitor performed a check.

Check Reboot Events by Category: [Hardware/Software/Application/System/Power]

Use this filtering option to only check for reboot events of the category you specify.

Ignore the Reboot Event Category: [Hardware/Software/Application/System/Power]

Use this filtering option to ignore a category of reboot event. If this kind of event occurs, FrameFlow won't alert about it.

Ignore reboot events that happen during maintenance windows

Check this box to ignore reboots that occur during planned maintenance periods.

Authentication and Security

The account used for authentication must have interactive login rights via SSH. Ensure that the '/var/log/journal' directory exists, 'systemd-journald' has correct ownership and permissions, and it's owned by the 'systemd-journal' group."

Protocols

Data Points

This event monitor does not generate any data points.

Back to Library

Sample Output