Forum Discussion
- hooleylistCirrostratusHi Thales,
- George_Watkins_Historic F5 AccountThales,
- Thales_92506NimbostratusThanks for the help.
Regular monitors goes only to 5,120 bytes, so i need to create an EAV (External Application Verification) for this task.
How do i do this?
Thanks.
As far as I'm aware, the 5120 byte limit is not user-configurable. You could use an external monitor instead:
http://devcentral.f5.com/wiki/AdvDesignConfig.codeshare.ashx ->
http://devcentral.f5.com/wiki/AdvDesignConfig.HTTPMonitor_cURL_BasicGET.ashx
Aaron
Another thing to consider is writing a separate script that lives on your origin web servers that is a wrapper for a number of tests performed on the application. I've done this in the past so that the BIG-IP health monitor can be as simple as possible while leaving the logic in a script on the webservers. You can also build some caching into the test script as well to prevent overloading your backend with excessive requests from health monitors.
-George
For now i´ll try the EAV monitor. I´m not so familiar with server scripts.
In this example (http://devcentral.f5.com/wiki/AdvDesignConfig.HTTPMonitor_cURL_BasicGET.ashx), if i put my request at the URI and the string i expect at the RECV, will it work without the 5,120 bytes limit?
Thanks.