Skip to main content

CMDB: The Beating Heart of IT Management

If you’ve followed my recent articles for APMdigest — on why you need application-aware network performance management (AA-NPM) tools a few weeks ago and, more recently, on why you need to integrate IT operations management and service management — perhaps you’ve already guessed where I’m heading. The more effectively we can integrate management tools at every level and the more effectively we can manage the delivery of IT as a service to our constituents, the more value we add to the enterprise and its mission.

At the same time, the further we enlarge those circles to encompass and integrate infrastructures that were previously disconnected, the greater the number of elements we need to incorporate, monitor and manage. It’s not just servers and storage systems — it’s everything from switches and routers to firewall appliances, to passive devices like printers, power and cooling systems, and more. It’s the mouse and the keyboard attached to each PC in the business; it’s the cell phone and the tablet that walked in — BYOD! — with an employee just this morning.

And we haven’t even touched on software or actual business processes.

I don’t think I need to go on; you know how complex and chaotic the broader infrastructure can become. We need something that ties all these disparate pieces together, a focal point that connects all these different physical and virtual assets and that fundamentally understands how all the different pieces of the IT puzzle fit together.

That’s where the configuration management database (CMDB) fits in. It’s not simply one more tool on par with every other tool in the world of IT management — that CMDB is dead! In today’s demanding environment, CMDB is the beating heart of a dynamic IT infrastructure, the element that connects all the assets involved in the delivery of everything from business services to the end-user experience. It must be understood as such — and deployed as such — for IT to deliver the higher levels of service it strives to deliver.

The Single Source of Truth

During the Gartner I&O summit last summer, an IT director from a large insurance company said to me, “We have so many tools doing multiple jobs in managing the IT infrastructure that I have lost the idea of a single version of truth.”

It’s easy to understand how this gentleman could say this: IT in a large company involves thousands — if not millions — of assets and processes interacting at once. If only small portions of that broader IT infrastructure are integrated then it is impossible to gain access to a single source of truth. There are simply too many barriers that stand in the way.

With a properly built and fully populated CMDB, though, those barriers begin to fall down. Not only would such a CMDB recognize all the IT and non-IT assets, all the processes and all the SLAs within the enterprise, it would recognize the relationships between these assets, processes and more. Put another way, if you looked up a physical asset in the CMDB as I’m describing it, not only would you learn about its physical characteristics — who manufactured it and when, what’s inside of it, how it’s licensed and more — you would also learn what role it plays in the delivery of any business service that touches it. You could see what flags it raised as well as when and where it exceeded or missed performance marks identified by the QoS levels and SLAs attached to services.

Moreover, you would see how that asset is connected to other assets within both the enterprise and the service delivery environment — and begin to understand how a change in the performance of one asset ripples through to other assets to affect the performance of an entire service. That level of visibility and insight is required for you to achieve real, effective change management in your organization.

In short, a CMDB that is properly designed and fully populated with information about the assets, processes, relationships and dependencies can be the single source of information from which actionable insights can arise about the state of the broad service delivery environment. And with that information, you can respond appropriately to deliver the best possible service to your clients.

Not There … Yet

So, one has to ask: If a CMDB is this great, why are we still having problems integrating these complex service delivery infrastructures? The simple answer is that few CMDB implementations are mature enough to provide the right balance of integration, support, ease of deployment, and cost-justification.

Many CMDB offerings are still vendor-specific, so they will only discover the assets that have been built by (or are supported by) a given vendor. Other CMDB implementations are more vendor-neutral but lack the tools to discover all the different types of assets that may be in use in a given environment. They may be able to detect a wide range of servers and network appliances, for example, but perhaps they cannot see the power and cooling systems installed in the server racks themselves. Still others require a prohibitive investment of time to configure and populate. Many are hugely expensive to acquire and maintain.

But this will change. Vendors may need to be pushed, but as IT organizations set higher expectations of vendor CMDB offerings — because they understand the critical role that a CMDB can play in integrating all aspects of a well-managed service delivery environment — then vendor offerings will evolve to overcome the issues described above. You should expect — even demand — more than you can get today: more integration, more federation, more robust relationship mapping between assets, better tools for visualizing actionable information, more extensive reporting and more insightful dashboards.

As for the integrated AA-NPM tools and integrated operational and service management tools that we talked about at the beginning of this series? They will integrate with the CMDB to provide even greater insights into activities, trends and anomalies in the service delivery network. With these deep connections into the CMDB itself, you will be able to use these tools to deliver the highest levels of service both to end users and the clients whose applications you support.

ABOUT Suvish Viswanathan

Suvish Viswanathan is the senior analyst, Unified IT, at ManageEngine, a division of Zoho Corp.

Hot Topics

The Latest

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

CMDB: The Beating Heart of IT Management

If you’ve followed my recent articles for APMdigest — on why you need application-aware network performance management (AA-NPM) tools a few weeks ago and, more recently, on why you need to integrate IT operations management and service management — perhaps you’ve already guessed where I’m heading. The more effectively we can integrate management tools at every level and the more effectively we can manage the delivery of IT as a service to our constituents, the more value we add to the enterprise and its mission.

At the same time, the further we enlarge those circles to encompass and integrate infrastructures that were previously disconnected, the greater the number of elements we need to incorporate, monitor and manage. It’s not just servers and storage systems — it’s everything from switches and routers to firewall appliances, to passive devices like printers, power and cooling systems, and more. It’s the mouse and the keyboard attached to each PC in the business; it’s the cell phone and the tablet that walked in — BYOD! — with an employee just this morning.

And we haven’t even touched on software or actual business processes.

I don’t think I need to go on; you know how complex and chaotic the broader infrastructure can become. We need something that ties all these disparate pieces together, a focal point that connects all these different physical and virtual assets and that fundamentally understands how all the different pieces of the IT puzzle fit together.

That’s where the configuration management database (CMDB) fits in. It’s not simply one more tool on par with every other tool in the world of IT management — that CMDB is dead! In today’s demanding environment, CMDB is the beating heart of a dynamic IT infrastructure, the element that connects all the assets involved in the delivery of everything from business services to the end-user experience. It must be understood as such — and deployed as such — for IT to deliver the higher levels of service it strives to deliver.

The Single Source of Truth

During the Gartner I&O summit last summer, an IT director from a large insurance company said to me, “We have so many tools doing multiple jobs in managing the IT infrastructure that I have lost the idea of a single version of truth.”

It’s easy to understand how this gentleman could say this: IT in a large company involves thousands — if not millions — of assets and processes interacting at once. If only small portions of that broader IT infrastructure are integrated then it is impossible to gain access to a single source of truth. There are simply too many barriers that stand in the way.

With a properly built and fully populated CMDB, though, those barriers begin to fall down. Not only would such a CMDB recognize all the IT and non-IT assets, all the processes and all the SLAs within the enterprise, it would recognize the relationships between these assets, processes and more. Put another way, if you looked up a physical asset in the CMDB as I’m describing it, not only would you learn about its physical characteristics — who manufactured it and when, what’s inside of it, how it’s licensed and more — you would also learn what role it plays in the delivery of any business service that touches it. You could see what flags it raised as well as when and where it exceeded or missed performance marks identified by the QoS levels and SLAs attached to services.

Moreover, you would see how that asset is connected to other assets within both the enterprise and the service delivery environment — and begin to understand how a change in the performance of one asset ripples through to other assets to affect the performance of an entire service. That level of visibility and insight is required for you to achieve real, effective change management in your organization.

In short, a CMDB that is properly designed and fully populated with information about the assets, processes, relationships and dependencies can be the single source of information from which actionable insights can arise about the state of the broad service delivery environment. And with that information, you can respond appropriately to deliver the best possible service to your clients.

Not There … Yet

So, one has to ask: If a CMDB is this great, why are we still having problems integrating these complex service delivery infrastructures? The simple answer is that few CMDB implementations are mature enough to provide the right balance of integration, support, ease of deployment, and cost-justification.

Many CMDB offerings are still vendor-specific, so they will only discover the assets that have been built by (or are supported by) a given vendor. Other CMDB implementations are more vendor-neutral but lack the tools to discover all the different types of assets that may be in use in a given environment. They may be able to detect a wide range of servers and network appliances, for example, but perhaps they cannot see the power and cooling systems installed in the server racks themselves. Still others require a prohibitive investment of time to configure and populate. Many are hugely expensive to acquire and maintain.

But this will change. Vendors may need to be pushed, but as IT organizations set higher expectations of vendor CMDB offerings — because they understand the critical role that a CMDB can play in integrating all aspects of a well-managed service delivery environment — then vendor offerings will evolve to overcome the issues described above. You should expect — even demand — more than you can get today: more integration, more federation, more robust relationship mapping between assets, better tools for visualizing actionable information, more extensive reporting and more insightful dashboards.

As for the integrated AA-NPM tools and integrated operational and service management tools that we talked about at the beginning of this series? They will integrate with the CMDB to provide even greater insights into activities, trends and anomalies in the service delivery network. With these deep connections into the CMDB itself, you will be able to use these tools to deliver the highest levels of service both to end users and the clients whose applications you support.

ABOUT Suvish Viswanathan

Suvish Viswanathan is the senior analyst, Unified IT, at ManageEngine, a division of Zoho Corp.

Hot Topics

The Latest

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...