Health Monitor being sourced from Management interface causing async routing

I have a health monitor that is being sourced from the management interface - this was discovered by accident when i was doing a TCPDUMP on the vlan interface the traffic should have been sourced from.

example

vlan 10 interface on f5 10.0.0.1 destination ip address of device being monitored = 10.0.0.6

when i did a tcpdump on the vlan to troubleshoot a separate problem i didnt see the traffic - i could see other health monitor traffic using the vlan for devices on the subnet and i know the routing and connectivity is working fine.

Wondering what reason there would be for the health monitor not to use the vlan associated with the subne t and use the management ip address to source the health traffic.

FYI the health monitor is working and responding as expected but would just like the traffic to use the correct path - via the connected vlan instead of sending around the world and through various firewalls to reach its destination (lucky the firewalls are permitting the traffic.

Thanks