Well, packages can be signed, packages can be pinned using internal repos, and lists of installed packages (and their versions) can be easily generated.

Packages are also easier to audit and deploy on internal networks than an install script which can change at whim.

In short, I have no guarantee that the bash script or tarball I'm installing via the piped bash method is the script or tarball the authors intended to be installed. I also have no way of installing this on servers without internet access, short of hacking the install script (of course, this matters less since this is monitoring as a service, but as a general principle it still stands).

Oh, you meant "lose control" more as in "have an unmaintainable mess". For some reason I'd only read it as "get 'sploited".

I did also mean "get 'sploited" - in that when someone is used to running curls into elevated shells, they're more likely to accept this from random forum goers as a valid way to troubleshoot problems; not necessarily as a problem for this company.