You won't see ESG vNICs in the Flow Monitoring tool, however, do packet captures on the ESG to see traffic on either side of the connection there and also save as a pcap. Syntax is similar to that of TCP dump with the exception of using underscores where you'd normally have spaces. Section 14 of the Load Balancer Troubleshooting Using the CLI portion of the troubleshooting guide has some examples of the commands with various filters, etc.
As mentioned in Luke's reply, there are some few CLI commands that you can use from NSX Edge
If you want to see the client's IP from NSX Edge CLI, you can try to use these commands
show service loadbalancer table
show service loadbalancer table ipv4_ip_table...
you can also do a debug packet capture in NSX Edge using below commands
debug packet capture interface <interface-name>
debug packet display interface <interface-name>
you can do filter and separate the objects using _ for example:
debug packet display interface vNic_0 host_192.168.110.11_and_host_192.168.110.12Bayu Wibowo | vExpert NSX, VCIX6-DCV/NV, Cisco Champion, AWS-SAA1 person found this helpful
Author of VMware NSX Cookbook http://bit.ly/NSXCookbook
https://nz.linkedin.com/in/bayupw | twitter @bayupw