Event Start Time | Event End Time | Event Duration | Event/State Type | Event/State Information |
05-11-2024 00:00:00 | 05-12-2024 00:00:00 | 1d 0h 0m 0s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
05-12-2024 00:00:00 | 05-13-2024 00:00:00 | 1d 0h 0m 0s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
05-13-2024 00:00:00 | 05-14-2024 00:00:00 | 1d 0h 0m 0s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
05-14-2024 00:00:00 | 05-14-2024 01:33:36 | 0d 1h 33m 36s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
05-14-2024 22:39:18 | 05-14-2024 22:48:48 | 0d 0h 9m 30s | SERVICE CRITICAL (HARD) | CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. |
05-14-2024 22:48:48 | 05-14-2024 23:20:48 | 0d 0h 32m 0s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
05-15-2024 00:00:00 | 05-15-2024 21:51:53 | 0d 21h 51m 53s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
05-15-2024 22:42:52 | 05-15-2024 22:52:49 | 0d 0h 9m 57s | SERVICE CRITICAL (HARD) | (No output on stdout) stderr: connect to address 10.3.163.111 port 5666: No route to host |
05-15-2024 22:52:49 | 05-16-2024 00:00:00 | 0d 1h 7m 11s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |
05-16-2024 00:00:00 | 05-16-2024 01:41:48 | 0d 1h 41m 48s | SERVICE OK (HARD) | PROCS OK: 1 process with command name 'rsyslogd' |