Event Start Time | Event End Time | Event Duration | Event/State Type | Event/State Information |
04-21-2024 00:00:00 | 04-22-2024 00:00:00 | 1d 0h 0m 0s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
04-22-2024 00:00:00 | 04-23-2024 00:00:00 | 1d 0h 0m 0s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
04-23-2024 00:00:00 | 04-24-2024 00:00:00 | 1d 0h 0m 0s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
04-24-2024 00:00:00 | 04-25-2024 00:00:00 | 1d 0h 0m 0s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
04-25-2024 00:00:00 | 04-25-2024 01:01:20 | 0d 1h 1m 20s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
04-26-2024 00:00:00 | 04-26-2024 20:02:17 | 0d 20h 2m 17s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
04-26-2024 20:02:17 | 04-26-2024 20:08:47 | 0d 0h 6m 30s | HOST DOWNTIME START | Start of scheduled downtime |
04-26-2024 20:08:47 | 04-26-2024 20:18:47 | 0d 0h 10m 0s | SERVICE CRITICAL (HARD) | (No output on stdout) stderr: connect to address 10.3.169.120 port 5666: Connection refused |
04-26-2024 20:18:47 | 04-26-2024 22:02:02 | 0d 1h 43m 15s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
04-26-2024 22:02:02 | 04-30-2024 21:34:06 | 3d 23h 32m 4s | HOST DOWNTIME END | End of scheduled downtime |