The latest News and Information on Incident Management, On-Call, Incident Response and related technologies.
Today is day one of the RSA Security Conference in San Francisco, where thousands of security professionals from around the world come together to share new ideas, discuss global security vulnerabilities, and explore the latest technologies in the security industry.
Services are the backbone of our systems. Whether they’re functional microservices or logical components of a traditional application, they are the pieces that make up our businesses. We can’t do the computer thing without services. But who’s responsible for owning a service in your company or organization? The cast of characters involved in the lifecycle of a service is more than just software engineers.
In the past, many organizations grew and managed their own data centers. Some still do. And many are still developing their own automated incident management (aka Autonomous Operations) tools. But as IT grows and becomes evermore complex and fast-moving, the reality of what it means to do so kicks in, and organizations are re-evaluating their strategies.
Exceptional customer service is key in the world of IT, where something could go wrong at any given moment. This level of support equates to business retention, client satisfaction and high success rates and profits. In this post, I’ll introduce a hypothetical scenario, where “MSP Team A” provides 24×7 after-hours support to a valuable client.
451 Research Senior Analyst Nancy Gohring and Moogsoft EMEA CTO Will Cappelli outlined market opportunities and challenges during their instructive webinar “AIOps Predictions 2020.”
Can you trust AIOps tools not to make mistakes? Is there an implementation standard for AIOps? What’s the risk of not adopting AIOps?
When his phone wakes him at two in the morning, operations engineer Andy Pearson knows it’s bad news. There’s a major server problem, and hundreds of client websites are down. Automated monitoring checks detected the outage within seconds, and paged the on-call engineer. This time, it’s Pearson in the hot seat. Pearson quickly confirms the issue is real and, escalates it to his boss, tech lead Lewis Carey.
