Hi vadivelan, if you create a custom bash monitor, you could use curl and do whatever checking you want along with specifying a custom user agent (host header is destination, not source). Here's an example to get you started:
Thanks for your reply. the actual requirement is our server team seeing lots of health monitor logs on the server logs, which is coming from F5 SLB source address is the self ip and source host name is null.
our server team required source host name in the header of the health monitor packet. we already create DNS A record for the self ip of the SLB.
is there any workaround to include the source host name as well in the tcp header packet while send the health monitor from SLB to server.