The alarm that doesn't wake anyone is worse than none at all.
In meinem ersten größeren Projekt waren wir stolz auf unsere Alarme. Wir hatten Hunderte davon. Jede Metrik, die uns eingefallen ist, bekam einen Schwellwert und eine Benachrichtigung. Wir dachten, das sei gründlich. In Wahrheit hatten wir uns eine Umgebung gebaut, in der niemand mehr hinschaute. Der Effekt kam schleichend. Erst überflog man die Alarme noch. Dann klickte man sie weg. Am Ende gab…
Sergey Shinder recounts his experience with alarms in a large project, where numerous alerts were set up but became ineffective due to overuse. He now approaches alarms with caution, only setting them up if he would want someone to take action if it occurred at night. Shinder advises setting alarms for symptoms that users experience, such as latency or error rates, rather than causes like high CPU usage.
He also recommends regularly reviewing alarms to eliminate those that do not lead to action, as ineffective alarms can be counterproductive.
Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.
