How to profile .NET application network usage

Question

I have a Windows.NET service that does a lot of network magic (WMI, Ping, etc. - the list is very long). I would like to comment, with the greatest possible ease and detail, how much bandwidth the application uses in total, as well as each part of the code.

Are there any tools that can help me? The Ants profiler, for example, will help me with memory profiling and processor utilization profiling. However, it does not work very much with network profiling. Is there something like ANT for network profiling? If not, what are my options when it comes to getting this information?

thanks

In response to some answers: added to clarify

Regardless of this tool, if it cannot directly refer to the code (which, in my opinion, is impossible), it should be able to run the network traffic used by the process without supervision for tracking days (writing to a file or database). It should be able to directly indicate the process (which the conductor cannot do). Microsoft Network Monitor can do this, but it does a lot more (so much parsing - frame by frame) that it cannot be used due to performance problems (after a few hours of work, I already have a million frames for counting votes. If I try copy the material to Excel or the database, only one copy takes more than 30 minutes).

Actually, it would seem to be such a simple thing, but it’s very difficult for me to find a tool that will do what I want.

Answer 1

You can use the Wireshark utility to capture all packets leaving the machine on which the service is running. You can then filter these packages based on the contents inside it to limit the packages that interest you. Using this information, you can find the indicators you are looking for.

Answer 2

I really like SocketSniff . It connects to one running process and shows all traffic connected by a neighbor. It does not have great decoding like WireShare, but it also removes a lot of noise.

Answer 3

You can try the MS Visual Roundtrip Analyzer (which uses MS Network Monitor ) or, perhaps, only the network monitor itself.