The latest News and Information on Incident Management, On-Call, Incident Response and related technologies.
As a business owner or manager, you understand the importance of efficient operations and effective communication, particularly after hours. You want to equip your on-call engineers with all the information they need to resolve a ticket when not at their desk. If you are using ConnectWise to manage your service tickets – here is some great addition to help with your after hours alerting.
IT operations teams are challenged to keep pace with the rapid speed of digital transformation. As companies use more cloud-based apps, increase agile deployments, and develop new microservices-based applications, they add layers and complexity to their technology stacks, making life increasingly challenging for ITOps performance.
When it comes to managing services effectively, terms like SLA, SLO, and SLI are often thrown around like confetti at a parade. They’re in meetings, in documents, and even in casual office conversations. But if you’re new to the field or simply haven’t had the chance to dig into these acronyms, they can feel like a bewildering alphabet soup. And they can’t be missing on an uptime monitoring blog such as ours! So, what do these terms really mean?
You've just made it through a particularly tough incident. It was a short outage affecting a subset of customers, so not exactly the end of the world, but bad enough that it involved multiple people across a number of teams to resolve. Either way, the incident was well managed, and the dust has settled. Now what? Most guidance would say that putting together a post-mortem document is a good idea, given the severity of the incident. You've also done this, so what's next?
