Configuration Management Databases (CMDB) and application and infrastructure discovery aren't particularly new to most organizations. However, most organizations struggle with end to end discovery and especially keeping their configuration management data and configuration items (CIs) current and accurate.
Good CMDB management is important for a number of reasons. It is a practice which underpins software and hardware asset management. Anyone that has ever suffered through an audit by a vendor wishes they had had better CMDB, Discover and Asset Management practices.
Having good configuration data is also vitally important for end-to-end monitoring. It's a key component of being able to do impact analysis for change management and is required to be able to correlate monitoring alerts. Strong configuration management practices pay for themselves. Unfortunately, it often takes a vendor audit or a prolonged outage to get management visibility and sponsorship to improve organizational configuration management practices.
Organizations actively moving to a hybrid cloud environment and transitioning to Agile practices have found that having good discovery and configuration management practices are enormously important as they seek to determine which applications in their portfolio are suitable (have a technical and business case) for migration to the public cloud or a hybrid cloud environment leveraging application containers. At the application layer, a code level analysis occurs to determine the level of effort to move to the cloud, but the configuration management is critical to understand the total impact in terms of the amount of work required to move and the financial impact or opportunities of moving. Good configuration practices are required to answer these questions: what does this application run on and what will it cost us / save us to move off of it? What hardware can we retire or repurpose? What software assets, licenses or subscriptions can we reclaim? What other assets will a particular configuration change affect? How many times do we see the same issue recur within a specific time period? And answer to more such questions.
The good news is that these are solvable problems. Keyva has years of experience helping organizations implement good change management and configuration management practices. We can mend an ailing CMDB and we can help you leverage the information it contains to the greatest possible effect: from asset management, to end-to-end monitoring, to hybrid cloud and application migration. Call us today to learn more about how you can get the most from your configuration management database.
There are various use cases that fall under configuration management.
- - If you are focused on DevOps pipelines, configuration management becomes imperative to avoid downtimes when application releases cause application downtime.
- - If you are deploying Infrastructure as Code, configuration management helps you detect when additional capacity is needed, so new components can be provisioned on the fly. If you have a large NOC, automated configuration management helps you with event correlation and root cause analysis, so that you can automatically remediate alerts that are caused due to log file overflow, CPU high, memory high, disk space utilization, etc.
- - If you are heavily invested in IT Service Management (ITSM) processes, the configuration management database (CMDB) provides you a single source of truth for all the different types of assets and Configuration Items (Cis) in your environment, and the relationships and dependencies between the different Cis, so that you can make information decisions when approving infrastructure changes.