The latest News and Information on Incident Management, On-Call, Incident Response and related technologies.
As the year draws to a close, for many of us this is a time to slow down, kick back and look forward to holiday time. For others, the work certainly isn’t done yet. The “S” word comes down to bear. Like it or not, this time of year – it’s all about the Shopping.
It’s time for change – my first insight from GartnerIO, 2018. During my flight to Vegas I remembered that this was probably my 15th visit to a conference in Vegas (but who can really count…after a few, it all starts to blur together). What I do remember though is that, in each of these conferences, there was one very shiny buzzword. The reason I remember this so well is because, while everyone agreed on what the buzzword was, there was no consensus on what that word meant!
According to the ITIL, the framework of best practices for delivering IT services, there is a recommended process flow for how to handle major incidents. Clearly, the IT community would be well served to follow the ITIL’s systematic and professional approach, whose benefits, according to CIO Magazine.
The typical DevOps on-call engineer is responding to alerts, triaging based on service impact, troubleshooting high priority incidents, and taking action to remediate issues. Automation tools like AWS Systems Manager can be a big help in reducing some of the more repetitive work and allowing engineers to focus on the most important tasks.
