Log browser errors and network traffic during Angular e2e (protractor) tests

I have two sizable Angular 7 CLI applications with good e2e coverage. Around the same time, both applications started to intermittently timing out at the start of the tests, most reliably on the AppVeyor build server. Incidentally, I can also get it to repro locally.

The basic logs just say that the tests timed out at a certain step, which isn't really useful. I suppose some kind of API call or Angular feature isn't reliable at the moment, but I don't know which one.

How can I increase verbosity for ng e2e to the max? The more output the better at this point, but at the least I'm looking for:

• The browser's network traffic (e.g. is some API giving 500s? or unreachable?)
• The browser errors (i.e. stuff you'd see in the console)

Ideally I'd increase verbosity and enable extra logging with just a flag on the command line, or a setting in e.g. the protractor.conf file - but at this point I'm also willing to install additional packages if needed.

I've checked the Angular CLI e2e docs but it doesn't mention "verbosity" or "log". I've glanced over the protractor example (?) config linked on the protractor website as a reference, but couldn't find anything either.