Host Alert History
Last Updated: Tue Jul 1 16:37:41 CEST 2025
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-bugzilla'

Latest Archive
Latest Archive
Log File Navigation
Tue Jul 1 00:00:00 CEST 2025
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 01, 2025 16:00

Service Ok[2025-07-01 16:12:51] SERVICE ALERT: suse-bugzilla;HTTPS private bugzillabug;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 8684 bytes in 0.577 second response time
Service Critical[2025-07-01 16:10:50] SERVICE ALERT: suse-bugzilla;HTTPS private bugzillabug;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds

July 01, 2025 15:00

Service Ok[2025-07-01 15:58:48] SERVICE ALERT: suse-bugzilla;HTTPS private bugzillabug;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 8684 bytes in 1.703 second response time
Service Critical[2025-07-01 15:56:46] SERVICE ALERT: suse-bugzilla;HTTPS private bugzillabug;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds

July 01, 2025 14:00

Service Ok[2025-07-01 14:46:00] SERVICE ALERT: suse-bugzilla;HTTPS;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 11101 bytes in 0.432 second response time
Service Critical[2025-07-01 14:44:00] SERVICE ALERT: suse-bugzilla;HTTPS;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 10 seconds
Service Ok[2025-07-01 14:34:44] SERVICE ALERT: suse-bugzilla;HTTPS private bugzillabug;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 8684 bytes in 0.218 second response time
Service Critical[2025-07-01 14:32:44] SERVICE ALERT: suse-bugzilla;HTTPS private bugzillabug;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds

July 01, 2025 12:00

Service Ok[2025-07-01 12:20:42] SERVICE ALERT: suse-bugzilla;HTTPS private bugzillabug;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 8684 bytes in 1.765 second response time
Service Critical[2025-07-01 12:18:40] SERVICE ALERT: suse-bugzilla;HTTPS private bugzillabug;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds

July 01, 2025 11:00

Service Ok[2025-07-01 11:56:38] SERVICE ALERT: suse-bugzilla;HTTPS private bugzillabug;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 8681 bytes in 0.221 second response time
Service Critical[2025-07-01 11:54:38] SERVICE ALERT: suse-bugzilla;HTTPS private bugzillabug;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds

July 01, 2025 08:00

Service Ok[2025-07-01 08:02:36] SERVICE ALERT: suse-bugzilla;HTTPS private bugzillabug;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 8681 bytes in 0.227 second response time
Service Critical[2025-07-01 08:00:36] SERVICE ALERT: suse-bugzilla;HTTPS private bugzillabug;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds

July 01, 2025 06:00

Service Ok[2025-07-01 06:38:34] SERVICE ALERT: suse-bugzilla;HTTPS private bugzillabug;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 8684 bytes in 0.224 second response time
Service Critical[2025-07-01 06:36:34] SERVICE ALERT: suse-bugzilla;HTTPS private bugzillabug;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds

July 01, 2025 05:00

Service Ok[2025-07-01 05:54:32] SERVICE ALERT: suse-bugzilla;HTTPS private bugzillabug;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 8684 bytes in 0.259 second response time
Service Critical[2025-07-01 05:52:31] SERVICE ALERT: suse-bugzilla;HTTPS private bugzillabug;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds

July 01, 2025 04:00

Service Ok[2025-07-01 04:20:29] SERVICE ALERT: suse-bugzilla;HTTPS private bugzillabug;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 8684 bytes in 0.247 second response time
Service Critical[2025-07-01 04:18:29] SERVICE ALERT: suse-bugzilla;HTTPS private bugzillabug;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 2 seconds