The Changes in “Change”
Richard Whitehead | May 22, 2014

Change can cause service interruption, but there's a smart way to manage that.

Change can cause service interruption, but there's a smart way to manage that.

A maxim in our industry is that when something stops working, the first question IT support asks is “what did you change?” It’s the right question. Almost 20 years ago, industry analysts reported that the majority of outages were caused by change.

About 10 years ago, I was working on a software solution for trouble-shooting an IP-PBX system. In common with many systems, issues often stemmed from ill-advised changes. This lead to a technique where regular configuration “snapshots” were taken, so when a problem surfaced, a “diff” of the current configuration, compared to a last known good, could be presented to the engineer as part of the ticket.

It was well received, but that was 10 years ago.

  • The velocity of change (and the dimensions of configuration) has increased dramatically
  • The snapshot approach lacks granularity
  • Now, you may not be analyzing changes made by a human in a maintenance window, but changes made by an autonomic system in real-time

Here’s a better approach:

  • Source change notifications
  • Correlate them in real-time with developing situations in the infrastructure

Now that’s 21st Century agility!

This is one of the difficult challenges that Moogsoft AIOps solves today.

Moogsoft is the AI-driven observability leader that provides intelligent monitoring solutions for smart DevOps. Moogsoft delivers the most advanced cloud-native, self-service platform for software engineers, developers and operators to instantly see everything, know what’s wrong and fix things faster.
See Related Posts by Topic:

About the author


Richard Whitehead

As Moogsoft's Chief Evangelist, Richard brings a keen sense of what is required to build transformational solutions. A former CTO and Technology VP, Richard brought new technologies to market, and was responsible for strategy, partnerships and product research. Richard served on Splunk’s Technology Advisory Board through their Series A, providing product and market guidance. He served on the Advisory Boards of RedSeal and Meriton Networks, was a charter member of the TMF NGOSS architecture committee, chaired a DMTF Working Group, and recently co-chaired the ONUG Monitoring & Observability Working Group. Richard holds three patents, and is considered dangerous with JavaScript.

All Posts by Richard Whitehead

Moogsoft Resources

April 8, 2021

A Day in the Life: Sarah the DevOps Engineer and the Beauty of AIOps

March 30, 2021

Coffee Break Webinar Series: Intelligent Observability for SRE

March 24, 2021

Coffee Break Webinar Series: Intelligent Observability for IT Ops

March 23, 2021

A Day in the Life: Intelligent Observability at Work with a Super SRE