Please include more information in the bug report (what was your setup (in what context?)), what did you do? What did you do? What happened instead?

Removing component Infra>Client>ChromeOS>Test since we don't look at these bugs directly.
Matt: Can you redirect these bug reports to the correct component? How are these being filed?

These are reported by mqg@ for moblab. THe account chasing.a.test@gmail.com is an account she created and is signed into on her moblab. If she encounters a problem, she files a bug report on the device using that account.

If possible, I would like to be able to measure how much time moblab loses network connection during the day. Is there a tool for that, Matt? 

Just to be clear - are you asking for a way to measure the disconnects from the moblab to the internet or from moblab to the DUT ?

There are some networking tools installed on moblab - but nothing specifically designed to monitor connections.

Use the crash reporter to track shill crashes. Some details in this bug comment https://issuetracker.google.com/issues/80230722#comment15

You can also write your own script to run on moblab and keep track of network connection

There is already an upstart job that checks for network connection
https://chromium.git.corp.google.com/chromiumos/platform/moblab/+/6db314c8e75233625739bcab9fd0f284a5534553/src/upstart_init/moblab-internetcheck.conf
Logs would be /var/log/bootup/moblab-internetcheck.log

This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.