Created
March 12, 2014 16:26
-
-
Save rdark/9510600 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# ALERT LOGS: | |
March 02, 2014 17:00 | |
Host Up[03-02-2014 17:23:01] HOST ALERT: a0.webproxy.domain.com;UP;HARD;1;HTTP OK: Status line output matched "HTTP/1.1 200" - 1633 bytes in 4.398 second response time | |
Host Down[03-02-2014 17:22:31] HOST ALERT: a0.webproxy.domain.com;DOWN;HARD;2;CRITICAL - Socket timeout after 10 seconds | |
March 02, 2014 16:00 | |
Host stopped flapping[03-02-2014 16:55:51] HOST FLAPPING ALERT: a0.webproxy.domain.com;STOPPED; Host appears to have stopped flapping (3.8% change < 5.0% threshold) | |
March 02, 2014 15:00 | |
Host started flapping[03-02-2014 15:39:41] HOST FLAPPING ALERT: a0.webproxy.domain.com;STARTED; Host appears to have started flapping (24.2% change > 20.0% threshold) | |
# NOTIFICATION LOGS: | |
a0.webproxy.domain.com N/A HOST UP 03-02-2014 17:23:01 user1_email_only notify-host-by-email HTTP OK: Status line output matched HTTP/1.1 200 - 1633 bytes in 4.398 second response time | |
a0.webproxy.domain.com N/A HOST UP 03-02-2014 17:23:01 user2_email_only notify-host-by-email HTTP OK: Status line output matched HTTP/1.1 200 - 1633 bytes in 4.398 second response time | |
a0.webproxy.domain.com N/A HOST UP 03-02-2014 17:23:01 user3_email_only notify-host-by-email HTTP OK: Status line output matched HTTP/1.1 200 - 1633 bytes in 4.398 second response time | |
a0.webproxy.domain.com N/A HOST DOWN 03-02-2014 17:22:31 user1_email_only notify-host-by-email CRITICAL - Socket timeout after 10 seconds | |
a0.webproxy.domain.com N/A HOST DOWN 03-02-2014 17:22:31 user2_email_only notify-host-by-email CRITICAL - Socket timeout after 10 seconds | |
a0.webproxy.domain.com N/A HOST DOWN 03-02-2014 17:22:31 user3_email_only notify-host-by-email CRITICAL - Socket timeout after 10 seconds |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment