Forum Discussion

Sorin_Rusnac_86's avatar
Sorin_Rusnac_86
Icon for Nimbostratus rankNimbostratus
Apr 07, 2008

custom http monitor

Hi

 

 

I am hoping somebody can help me in this fourm on this issue.

 

 

I am trying to setup a custom HTTP monitor that will send an email with a node is down. So if the HTTP monitor is set on a node in the pool and if http is down it will mark the node down as it does now but also send a an email via SMTP or something to an address saying that http failed on specified node.

 

 

Can you give me some examples how to do this and do I need to configure the F5 OS for a relay or smtp server and how do I do that?

 

 

 

Thanks so much for all the help
management
monitoring
  • Sorin_Rusnac_86's avatar
    Sorin_Rusnac_86
    Icon for Nimbostratus rankNimbostratus
    Mar 10, 2009
    Thanks for the reply, one other issue I have it I need to do a custom HTTP monitor that will check for "service unavailable" on each node in the pool and if it receives that from a node it marks it as down and then sends the email which node is down. Can anybody help or shed some light? Thanks
  • Deb_Allen_18's avatar
    Deb_Allen_18
    Historic F5 Account
    Mar 11, 2009
    You would simply configure a monitor based on the HTTP template, with the test page in the Send string and "service unavailable" as the Receive string, then follow the procedure in the doc linked above to enable email notification.
  • hoolio's avatar
    hoolio
    Icon for Cirrostratus rankCirrostratus
    Mar 11, 2009
    Does the pool member respond with a 200 to a normal monitor request? Does it respond with a 200 when it sends the service unavailable message? The service unavailable message is typically sent with a 503 status code. If your app uses a 200 response for service unavailable, you could configure one monitor that makes a request and looks for "200 OK" in the response and a second "reverse" monitor which marks the pool member up if the response does not contain "service unavailable":

     

     

     
 monitor reverse_monitor { 
    defaults from http 
    reverse 
    recv "service unavailable" 
    send "GET /monitor_page.html HTTP/1.1\r\nHost: \r\nConnection: Close\r\n" 
 } 
 monitor reverse_monitor { 
    defaults from http 
    recv "200 OK" 
    send "GET /monitor_page.html HTTP/1.1\r\nHost: \r\nConnection: Close\r\n" 
 }

     

     

    If the app responds with a 503 status for service unavailable you can just use a single monitor which sends a monitor request and expects a 200 OK response back in order to mark the pool member up.

     

     

    Aaron

     

    Aaron