![windows monitor network traffic per process windows monitor network traffic per process](https://i0.wp.com/www.alphr.com/wp-content/uploads/2019/04/fing.jpg)
Graphs are also available if you've got the relevant package installed (I don't on this machine) and the output will allow you to eyeball, by destination, where your traffic is going to (and coming from), along with the headline figures which will give you, in a roundabout way, what you're looking for. This expert will process whatever data you throw at it, AFTER it's been filtered (so to do this, you'd open up a capture file, apply your filters to isolate say firefox.exe, and then invoke the expert) and give you an output that looks a bit like this: That allows you to filter back to a certain target group, but unless you're feeling particularly masochistic and you enjoy reading frame headers, you want to get the NMTopUsers expert and aggregating it to something a bit more readable (NMTopUsers) IPv4.SourceAddress = 64.34.119.12 // traffic coming from IPv4.Address = 64.34.119.12 // traffic in both directions to (Conversation.ProcessName = "firefox.exe" and Conversation.ProcessId = 3824) // only look at firefox process 3824 The filter language is documented within the help, and it's got some decent canned examples, but just so you can see without downloading the package some examples would be: Conversation.ProcessName = "iexplore.exe" // restrict your examination to iexplore.exe You can apply filters to the data you've captured in order to trim down what you're looking at like say, knocking out certain IP addresses,protocols, or even particular processes (or even conversations if you wanted.). Filtering it all back so you don't go insane.
![windows monitor network traffic per process windows monitor network traffic per process](https://techtalk.gfi.com/wp-content/uploads/2015/05/Fiddler-1024x636.png)
It's probably better to just have a quick play rather than me wasting a mountain of words explaining, but in short - it's going to log every little bit of network traffic that it can - that's what's being displated in the middle pane. Opening up the application will then break it down into conversations, which you could further go into. It can a bit overwhelming at first, I'll admit, but mainly I'd draw your eye to the left hand side box which will show you all the processes it's captured as generating network traffic.
![windows monitor network traffic per process windows monitor network traffic per process](https://venturebeat.com/wp-content/uploads/2020/04/IMG_3032D-e1587505051722.jpeg)
Windows monitor network traffic per process windows#
I'm just performing a capture now while typing out this answer, and to add some variety into the mix - checking for windows updates, and running IE to fetch some files - but as you can see from the screenie here:
![windows monitor network traffic per process windows monitor network traffic per process](https://1gbits.com/uploads/tinymce/Suno/2021/02/04/601c1ab10acbe-resource-monitor-network-panel.png)
(It's also kinda fun seeing where your data goes.) Introducing: Microsoft Network Monitor 3.4 Straight up though - it won't give you precisely what you're after (a per-application level log) but it will give you the ability to slice the data up to get at that information, if you're feeling creative. If you can't find anything you're happy with application-wise, a heavyweight (but oh-so-satisfying-when-you-work-it-out) solution would be to do some network monitoring with Microsoft Network Monitor (v3.4 right now) which would then give you the ability to slice n dice things as you wanted?