UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to reproduce the problem:
1. Deploy a (bespoke) kiosk Chrome app to a managed Chrome device
2. Wait for app to crash/go wrong
3. Try figuring out what's gone wrong!

What is the expected behavior?
When testing/running a bespoke Chrome app in the Chrome browser locally (be that on Windows, macOS, Linux or Chrome OS), if the app crashes, you can alt-tab (or equivalent) and pop open the Chrome console - to see exactly what's happened.

You can't do the same when the app is deployed in the field to managed Chrome endpoints. (You can try implementing your own logging, but sometimes that breaks and you don't know why, so you can't even harden the logging logic.)

What we really want is the ability to connect to Chrome devices' console remotely, exactly as described on the following page, but on production devices deployed in the field in verified boot mode:
https://connect.googleforwork.com/docs/DOC-17654

It is unrealistic to have a fleet of production devices in developer mode, and for intermittent/rare issues, you won't always be able to reproduce the issue on one or two test devices in the lab.

If there is some reason that providing real-time remote debugging isn't possible (technical or security), can we at least have the ability to upload the last 24 hours of the Chrome console on-demand using a button in the Chrome admin console? (If not to Chrome admin console-managed storage, to a GCS or S3 bucket.)

What went wrong?
You can't figure out what's gone wrong.

Did this work before? N/A 

Chrome version: 57.0.2987.137  Channel: stable
OS Version: 
Flash Version: Platform: 9202.60.0 (Official Build) stable-channel veyron_mickey