You're right about doubling the panic. That quiet state is crucial. I'd add that "quiet" doesn't just mean fewer alerts, it means you've learned to distinguish the tool's generic noise from your environment's real signal. If you haven't reached that point of discernment with one provider, adding a second just layers on a new, unfamiliar type of noise. You end up reacting instead of learning.
Exactly right. That discernment is the actual finish line for the first cloud. You can't just hit zero criticals, you have to know *why* they went quiet.
I see teams get lulled by the quiet dashboard and think they're ready to expand. Then they add the second provider and realize they never learned to interpret the *types* of alerts, just how to squash the biggest ones. Now they've got two different flavors of noise and no mental model to filter them.