The network log may contain personally identifying information like
IP addresses, URLs, and cookies.
You can edit the log to obscure information if you like, but sometimes it
is relevant to the bug.
Ideally you would have this tool running before you reproduce the
bug.
If that isn't possible (perhaps the bug happens unpredictably), then the
next best thing is to load chrome://net-internals/ as soon as you can
after the problem has occurred.
How it works
While this page is open, it will capture the network events that are
happening in Chrome. You can view that in real-time by going to the
Requests tab.
Once you close this window, the data it had captured is discarded.
Chrome keeps around a small buffer of network events for the
most recent requests. That way if you open chrome://net-internals/
shortly after encountering a problem, you can still find the relevant
data.
These passively captured events are less accurate however, and will
be prefixed in the log with (P).
Input a URL which failed to load, and then click the button to run some
tests for why it failed.