i'm not sure a crosh command would be that useful here, and asking users to gather that for you is kind of a lot of a hassle

can't you just gather the info you need as part of feedback reports ?

I can see your point.  

I think we want to do both, though -- feedback as the primary way we gather information from users in the field about things going wrong, and a crosh hook for developers to be able to have a lower latency way to inspect a given network closer to real-time. 

I anticipate that there's going to be a lot of weird, non-compliant behavior out there from printer manufacturers, and I think we're going to need good tooling to run those issues down.

...and now that I look at the code, I'm also thinking this isn't such a great idea.

What we need visibility into is Chrome state (it's mDNS stack/cache information).  I didn't realize crosh is outside the browser process, so putting this into crosh means we have to do a lot of plumbing work to get the data in the right place.

Going to leave this open while I think about a better way forward, but I suspect we won't do this with crosh directly.

Possibly a chrome:// page would be a better fit.

yeah, crosh is not good for gathering Chrome info at all

you want to look at chrome://net-internals instead

you should still be able to integrate with feedback reports though since Chrome drives that

Yes, that looks like the right place for it.

Also filing a separate bug to track putting useful mdns information into feedback reports.

We decided to go in a different direction for this.