At least when the on call rotation is small I think it’s useful tracking incident counts to predict burnout. Worst incident I had at prev company was getting pulled out of movie date to fix some dumb app bug I had fixed + flagged when I was on call 5 weeks ago
-
-
-
Alerts aren’t equivalent to incidents though, only in PagerDuty’s weird data model. One is a signal and the other is an actual impactful issue. Either way, counting alert frequency is definitely extremely important.
- Još 1 odgovor
Novi razgovor -
-
Novi razgovor
-
-
agree. SEV Counts are not helpful product quality metrics. They’re lagging. Metrics around count of failed cust. transaction is leading
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
This is great, thanks.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Thanks :)
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I… recently started trying to compare cross team incident counts for my own curiosity. But I should probably not. Thanks!
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I am struggling with the zero tolerance to measurement of absolute incidents. I am in violent agreement that we should not be incentivising less of them -- but I worry about the opposite. Measurement might allow identifying those "too quiet" areas. /1
-
That is, in my experience a lack of reports does not indicate a lack of issues but rather a lack of investigation following. As well, even in the case there haven't been any issues teams knowledge of the system fades over time. /2
- Još 1 odgovor
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.