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-27-2024 20:29:39 | 03-27-2024 20:38:59 | 0d 0h 9m 20s | HOST DOWNTIME START | Start of scheduled downtime |
03-27-2024 20:38:59 | 03-27-2024 20:48:59 | 0d 0h 10m 0s | SERVICE CRITICAL (HARD) | (No output on stdout) stderr: connect to address 10.3.163.105 port 5666: Connection refused |
03-27-2024 20:48:59 | 03-27-2024 22:29:33 | 0d 1h 40m 34s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
03-27-2024 22:29:33 | 03-28-2024 00:00:00 | 0d 1h 30m 27s | 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' |
03-29-2024 00:00:00 | 03-31-2024 01:39:11 | 2d 1h 39m 11s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |