Could you add setup.exe and mini_installer.exe to the targets to monitor? The latter is the full installer downloaded by clients for new installs, so we certainly want to track it. Tracking setup.exe is good since it occasionally gets bloated by accidental build dependency snafus.

https://cs.chromium.org/chromium/src/chrome/installer/mini_installer/chrome.release?type=cs&q=file:mini_installer/chrome%5C.release&sq=package:chromium&l=1 lists the other binaries that are bundled into the mini_installer. If it's cheap to do so, does it make sense to monitor the sizes of everything independently?

Thanks for checking!

Monitoring updated.

Hi sullivan: It looks like chrome.exe had a regression on Aug 11, growing by 150% (from 991,232 bytes to 2,513,408 bytes) on official builds. This is visible on the dashboard, but was a bug filed for it? If not, is there a way we can get bugs filed automagically for regressions like this? Thanks!

Ah, looks like there was a miscommunication: we were monitoring chrome.dll as per summary and setup.exe and mini_installer.exe per comment 1, looks like we should also add chrome.exe. I have fixed the monitoring so this will trigger alerts in the future.

Awesome! Thanks.