Doesn't F5 offer the functionality to perform active health checks (ping/port/url check) against the resources that are behind it? For example with Nginx+ (software LB) we can configure health checks at regular intervals and if the check fails it would remove that host from the pool (for reference https://www.nginx.com/products/application-health-checks/).
The only failover available for collectors that I know of is collector grouping. This allows your agents to automatically rollover to a new collector when they are disconnected from their original one and provides some agent balancing capabilities as well.
You can check out this page on collector setup for more information. There is a link for collector groups that I would highly recommend:
Yes, you are correct Srikar,
Basically, I am looking for more details on this topic.
What Port / URL can the F5 check to identify when to take the collector out of the pool.
Thanks for your reply.