# @mipsytipsy on Twitter: don’t alert on everything

- **期号**: SRE Weekly Issue #190（2019-10-20）
- **作者**: Charity Majors (@mipsytipsy)
- **链接**: https://threadreaderapp.com/thread/1185384414814990336.html

## 简介

Charity Majors replied to a suggestion to write alerts for everything with her ideas for a better way.

## 正文

![Profile picture](https://threadreaderapp.com/images/avatars/90488576.jpg) 

[@mipsytipsy](https://twitter.com/mipsytipsy)




![Profile picture](https://threadreaderapp.com/images/Twitter_Logo_Blue.png)

The #1 sign that someone does not have observability is this: they lean on alarms for ⭐️EVERYTHING.⭐️

They cannot debug or introspect their systems any other way, so they abuse the FUCK out of monitoring checks and alarms.

[charity.wtf/2019/09/20/lov…](https://charity.wtf/2019/09/20/love-and-alerting-in-the-time-of-cholera-and-observability/)

Sorry if that was a little harsh. Flashbacks. Shudder.

It is NOT EASY trying to cobble together an understanding of a complex system using checks, alarms, dashboards, and your intuition. Sweetheart, I *know*. You do your best

But your systems are getting exponentially more complex. Every dimension is high cardinality with a growing set -- services, apis, instances, containers, endpoints, storage...

It's all growing a lot faster than *that* exponential curve. You cannot subject a team to this barrage of alerts and thresholds.

Or if like they are on call and trying to repro something for a particular user.