UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce the problem:
Attempt to record and act on HTTP error statuses from outside browser.

What is the expected behavior?
When Chromium is started with --enable-logging, a logging level would exist which outputs HTTP status codes of loaded pages so 40X and 50X errors could be monitored and acted upon by a management script.

What went wrong?
Even when starting Chromium with verbose logging, HTTP status codes are not found in the logs.

Did this work before? No 

Chrome version:   Channel: stable
OS Version: 
Flash Version: 

This would be useful a Chromium kiosks. I'm looking to build Chromium-based kiosks and I would like the ability for my client-side management scripts to detect when a client experiences an HTTP error, as well as timeouts, etc. then report it to the management server.