See dart-lang/sdk#60540 (comment)

Some users use this command periodically but not enough to get a prompt encouraging filing a bug. It's also difficult to collect info after the fact (and it may not be appropriate to try to debug while you're in the middle of something and the analyzer breaks).

We should have this command automatically record some logs - for example the last traffic from the analyzer and the usual log header info. Each file should be new (with a timestamp in the name) to avoid any overwriting. This way if someone is using this command they may be able to provide or review these log files for possible patterns.

(ideally we'd get the instrumentation log, because it contains watch events and server-side errors.. but I don't think there's a good way to do this).