Denise Dubie
Senior Editor

Change, configuration and release management catch on

Opinion
May 16, 20072 mins

* Majority of application performance problems and network downtime can be attributed to some configuration change or error

It has become common knowledge that when systems go down, applications stall and networks fail it’s usually due to unknown, undocumented or unauthorized changes to network and systems configurations — and not because of technology failures.

In fact, it has been estimated by numerous industry watchers that up to 80% of application performance problems and network downtime can be attributed to some configuration change or error. And because of that, IT managers need to get on board and put proper policies and tools in place around change, configuration and release management, Gartner says.

The industry research firm in late 2006 surveyed close to 100 people at its Data Center Conference in Las Vegas about their use of change, configuration and release management tools and technologies. The results show that IT managers’ efforts today remain separate and unequal among the three IT disciplines, which will provide optimum results going forward. And Gartner found that IT organizations want to purchase tools before standardizing processes to address these issues — another potential pitfall of successful change, configuration and release management initiatives.

For example, about one-third of respondents said they are using technical domain configuration management tools. Another 22% said they have domain configuration tools as well as IT change management efforts under way. And some 17% had technical domain configuration tools, an IT change management initiative and a manual configuration repository. Ten percent said they have a configuration management database, or CMDB, in addition to configuration and IT change management tools and about 20% also had release management in place.

The results show that IT organizations are thinking about putting these tools in place, but Gartner notes a maturing of approaches and processes must take place for enterprise companies to reap the real rewards of this trio of technologies.

“Change, configuration and release management can only be executed with limited success as solo initiatives,” a Gartner report reads. The research firm writes that IT organizations must form “a team to approach all three of these processes in a coordinated manner” and to ensure success “IT organizations must invest in process policies and standards … before acquiring tools for process automation.”

Denise Dubie

Denise Dubie is a senior editor at Network World with nearly 30 years of experience writing about the tech industry. Her coverage areas include AIOps, cybersecurity, networking careers, network management, observability, SASE, SD-WAN, and how AI transforms enterprise IT. A seasoned journalist and content creator, Denise writes breaking news and in-depth features, and she delivers practical advice for IT professionals while making complex technology accessible to all. Before returning to journalism, she held senior content marketing roles at CA Technologies, Berkshire Grey, and Cisco. Denise is a trusted voice in the world of enterprise IT and networking.

More from this author