How to Configure Monitors (Proxy)






Set up the health monitoring method and monitor interval for your proxy.

Monitoring Method options include (Note: available options vary by proxy service.)

    • ICMP - Pings the backend.
    • TCP - Opens a TCP connection.
    • HTTP/HTTPS - Makes a HTTP/HTTPS based request to backend.
    • DNS (DNS Cache TCP service only)  If you choose DNS as the Monitoring Method, more options appear, shown in image below:
      • DNS-Monitors.png
  • Monitor Interval - The time interval (in seconds) at which the monitoring method checks the status of the proxy. i.e. Entering 30 here means that the proxy health is checked every 30 seconds.
  • Monitor Send / Receive - Only relevant if choose HTTP/HTTPS monitoring method. The HTTP/HTTPS supports specific requests (Monitor Send) and expects certain values to be received (Monitor Receive). See below Default Send/Receive Options for HTTP/HTTPS monitoring for more details.

How does Proxy Health monitoring work on the back end?

Silverline uses a tiered architecture for our proxy deployments. The Proxy Health Monitoring checks the end-to-end health of this data path. For more details, see Reporting: Proxy Health Monitoring

Where can I see the health reports on all my proxies?

In order to check the end-to-end health of your proxy, navigate to Config > Proxy /App Configuration > Proxy / App Management. For more details, see Reporting: Proxy Health Monitoring


Default Send/Receive Options for HTTP/HTTPS monitoring

Note: Only relevant for some Services (SSL HTTP) and only when the HTTP/HTTPS monitoring method is selected.

The HTTP/HTTPS supports specific requests (Monitor Send) and expects certain values to be received (Monitor Receive). These are the default settings, so if you deploy a new proxy with the Monitor Send and Monitor Receive fields blank, this is what is sent / looked for in the background:





GET / HTTP/1.1\r\nHost: <hostname>\r\nUser-Agent: F5-Silverline-HTTP-Monitor\r\nConnection: Close\r\n\r\n



GET / HTTP/1.1\r\nHost:<hostname>\r\nUser-Agent: F5-Silverline-HTTP-Monitor\r\nConnection: Close\r\n\r\n


 * Please also modify <hostname> to include the real hostname.

These default settings were updated in April 2019. With these defaults in place, a server that is responding with a non-HTTP compliant response or a response code outside 100-499 will be marked as unhealthy.

By default, without any configuration in the Send field, the following HTTP monitor request will be sent:

GET / HTTP/1.0

User-Agent: F5-Silverline-HTTP-Monitor



More information on BIG-IP HTTP and HTTPS application health monitors: K2167: Constructing HTTP requests for use with the HTTP or HTTPS application health monitor


Related Content

Related Configuration Options

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request