Few things damage productivity as much as waiting. The act of waiting forces us to context switch, disrupts our creative momentum, and eliminates our ability to experiment. Whether we are deploying a new service or troubleshooting a problem, waiting puts a heavy tax on team productivity in IT Operations.
Managing alert noise from monitoring systems like SolarWinds can be tricky and failing to order the noise can cause: Alert fatigue, Decreased MTTR, Missed alerts.
Today we’d like to talk a little about our integration with Pagerduty. We’ll go through some of the benefits of using this product in conjunction with StatusCake and overview the functionalities that are unique to this integration.
What’s surprising to see today is how business operations struggle to get an integrated view of all business metrics. With greater volumes of data being collected, data analysts just can’t keep up with the pace. This state of affairs alone doesn’t hit as hard as the fact that many in data analytics have just come to accept this situation as a norm and simply bear with this daily struggle.
Believe it or not, there is a difference between incident closure and incident resolution. Incident closure ensures a problem has been addressed. Comparatively, incident resolution goes a step further by ensuring an incident is closed and all stakeholders are satisfied with the end results and agree with the incident closure.
