针对高速团队的事件管理
IT 事件管理、响应和预防的未来
过去，负责应对技术事件的团队几乎一直是 IT 部门。通常，网络运营中心 (NOC) 的团队会监控系统并对中断做出响应。供应商可能已经构建了软件，但部署和操作则由客户的 IT 运营团队负责。如今，随着云服务激增，供应商构建了软件并进行了部署和运营。
然而，事件管理仍然是 ITSM 的核心实践。而且，IT 在制定指导方针、管理预算以及承担诊断、修复、记录和预防重大事件的各方面都有着悠久的历史。
当然，与科技领域的任何事物一样，过去不一定是未来的预测指标，而目前，事件管理的实践正在发生变化。DevOps、SecOps 和架构团队越来越多地参与其中。新技术和互联产品改变了我们管理事件的方式。为了跟上步伐，思维方式、实践和团队结构也在发生变化。
那么，事件管理如何转变，这对我们的角色、产品、流程和团队的未来意味着什么？
Yet incident management still remains a core ITSM practice. And IT has a long history of developing guidelines, managing budgets, and carrying the full burden of diagnosing, fixing, documenting, and preventing major incidents.
Of course, as with anything in tech, the past is not necessarily a predictor of the future—and currently the practice of incident management is shifting. DevOps, SecOps, and architecture teams are getting more involved. New technologies and interconnected products have changed how we manage incidents. And mindsets, practices, and team structures are changing in order to keep up.
So, how is incident management shifting and what does that mean for the future of our roles, products, processes, and teams?