Host Alert History
Last Updated: Thu Jul 30 21:54:39 CEST 2026
Nagios® Core™ 4.4.6 - www.nagios.org
Logged in as ?
View Status Detail For This Host
View Notifications For This Host
View Trends For This Host
Host 'suse-OBSAPI'

Latest Archive
Latest Archive
Log File Navigation
Thu Jul 30 00:00:00 CEST 2026
to
Present..

File: /var/log/nagios4/nagios.log
State type options:
History detail level for this host:
Hide Flapping Alerts
Hide Downtime Alerts
Hide Process Messages
Older Entries First


July 30, 2026 21:00

Service Critical[2026-07-30 21:53:25] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds
Service Ok[2026-07-30 21:43:24] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI/IPv4;OK;SOFT;3;HTTP OK: HTTP/1.1 200 OK - 21331 bytes in 1.466 second response time
Service Critical[2026-07-30 21:41:23] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI/IPv4;CRITICAL;SOFT;2;CRITICAL - Socket timeout after 2 seconds
Service Critical[2026-07-30 21:39:21] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI/IPv4;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds
Service Ok[2026-07-30 21:37:19] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI/IPv4;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 21331 bytes in 1.314 second response time
Service Critical[2026-07-30 21:35:18] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI/IPv4;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds

July 30, 2026 20:00

Service Ok[2026-07-30 20:03:23] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI;OK;HARD;3;HTTP OK: HTTP/1.1 200 OK - 21331 bytes in 1.193 second response time

July 30, 2026 19:00

Service Critical[2026-07-30 19:53:21] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI;CRITICAL;HARD;3;CRITICAL - Socket timeout after 2 seconds
Service Ok[2026-07-30 19:53:16] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI/IPv4;OK;SOFT;3;HTTP OK: HTTP/1.1 200 OK - 21331 bytes in 1.984 second response time
Service Critical[2026-07-30 19:51:19] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI;CRITICAL;SOFT;2;CRITICAL - Socket timeout after 2 seconds
Service Critical[2026-07-30 19:51:15] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI/IPv4;CRITICAL;SOFT;2;CRITICAL - Socket timeout after 2 seconds
Service Critical[2026-07-30 19:49:17] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds
Service Critical[2026-07-30 19:49:12] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI/IPv4;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds
Service Ok[2026-07-30 19:37:10] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI/IPv4;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 21332 bytes in 1.798 second response time
Service Critical[2026-07-30 19:35:08] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI/IPv4;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds
Service Ok[2026-07-30 19:33:06] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI/IPv4;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 21330 bytes in 1.277 second response time
Service Critical[2026-07-30 19:31:05] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI/IPv4;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds
Service Ok[2026-07-30 19:29:03] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI/IPv4;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 21332 bytes in 1.290 second response time
Service Critical[2026-07-30 19:27:02] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI/IPv4;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds
Service Ok[2026-07-30 19:25:00] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI/IPv4;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 21331 bytes in 1.493 second response time
Service Critical[2026-07-30 19:22:58] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI/IPv4;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds

July 30, 2026 07:00

Service Ok[2026-07-30 07:50:56] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI/IPv4;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 21358 bytes in 0.878 second response time
Service Critical[2026-07-30 07:48:55] SERVICE ALERT: suse-OBSAPI;HTTPS OBSAPI/IPv4;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds