Event Start Time | Event End Time | Event Duration | Event/State Type | Event/State Information |
03-23-2024 00:00:00 | 03-24-2024 00:00:00 | 1d 0h 0m 0s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
03-24-2024 00:00:00 | 03-25-2024 00:00:00 | 1d 0h 0m 0s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
03-25-2024 00:00:00 | 03-26-2024 00:00:00 | 1d 0h 0m 0s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
03-26-2024 00:00:00 | 03-27-2024 00:00:00 | 1d 0h 0m 0s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
03-27-2024 00:00:00 | 03-27-2024 16:39:24 | 0d 16h 39m 24s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
03-27-2024 16:39:24 | 03-27-2024 16:49:01 | 0d 0h 9m 37s | HOST DOWNTIME START | Start of scheduled downtime |
03-27-2024 16:49:01 | 03-27-2024 16:56:32 | 0d 0h 7m 31s | SERVICE CRITICAL (HARD) | (No output on stdout) stderr: connect to address 10.3.166.30 port 5666: No route to host |
03-27-2024 16:56:33 | 03-27-2024 17:09:01 | 0d 0h 12m 28s | HOST DOWNTIME START | Start of scheduled downtime |
03-27-2024 17:09:01 | 03-27-2024 18:39:19 | 0d 1h 30m 18s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
03-27-2024 18:39:19 | 03-27-2024 19:17:13 | 0d 0h 37m 54s | HOST DOWNTIME END | End of scheduled downtime |
03-28-2024 00:00:00 | 03-28-2024 01:55:48 | 0d 1h 55m 48s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |