Event Start Time | Event End Time | Event Duration | Event/State Type | Event/State Information |
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:56:32 | 0d 16h 56m 32s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
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' |
03-29-2024 00:00:00 | 03-29-2024 17:33:50 | 0d 17h 33m 50s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
03-29-2024 17:33:50 | 03-29-2024 17:48:55 | 0d 0h 15m 5s | HOST DOWNTIME START | Start of scheduled downtime |
03-29-2024 17:48:55 | 03-29-2024 17:58:52 | 0d 0h 9m 57s | SERVICE CRITICAL (HARD) | (No output on stdout) stderr: connect to address 10.3.163.54 port 5666: No route to host |
03-29-2024 17:58:52 | 03-29-2024 19:33:43 | 0d 1h 34m 51s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
03-29-2024 19:33:43 | 03-31-2024 01:39:11 | 1d 6h 5m 28s | HOST DOWNTIME END | End of scheduled downtime |