How agentless DDM improves the CMDB’s effectiveness
Here’s how an agentless auto-discovery and dependency-mapping capability works. The DDM:
- Requires no installations of services or applications on the hosts that it scans
- Scans IT infrastructure for system configuration and application information
- Operates on infrastructure in public and private clouds
- Tracks the flows between systems to capture dependencies
- Runs on a schedule or is triggered by change management workflows
- Enables IT ops to review changes
- Feeds the CMDB with the latest information
- Provides topology maps to visualise flows and dependencies
One important aspect of using DDM is scheduling how frequently to run discovery jobs, scan the infrastructure, and detect changes. Because many services, applications, and databases run on elastic cloud architectures, actively running DDM ensures that the CMDB has accurate, updated information.
IT may also want to trigger DDM in devops automations such as CI/CD pipelines or IaC scripts, or during other IT automation. This option may only work if DDM’s configuration allows running it on the network segments impacted by the changes.
DDM-backed CMDBs are critical for improving ITSM
Integrating an accurate CMDB with ITSM process can help simplify operations and drive improvements in key performance indicators.
Consider change management, the set of controls IT puts in place to track production changes and comply with regulatory requirements. Organisations sometimes have complex forms to fill out to promote a change order and may require presenting them to a change advisory board to review and address risks. IT can simplify the change order forms to reference entities in the CMDB rather than asking people to key them into fields. When the CMDB maps IT systems to business services, approved change orders can trigger communications to impacted end-users.
Incident management teams also have the opportunity to reduce the mean time to resolution when incidents are directly related to CMDB CIs. The direct relationship can help trigger automations to recover from failures or help incident managers identify the correct standard operating procedures in run books.
Analysts can leverage the relationship between CIs and incidents, change orders, and requests to identify trends or prioritise operational improvements. For example, an analyst might seek CIs related to the most frequent incidents or the ones that caused the most significant business impacts.
DDM enables faster, safer IT changes
During the past decade, IT departments have been under pressure to do more with less, support more frequent changes, and ensure higher systems reliability. But speed and efficiency shouldn’t drive reckless behaviour or leave behind poorly documented systems for the next teams to support.
IT leaders have been accustomed to not being able to accurately track IT systems and configurations. Historically, the costs and complexities to maintain a CMDB overshadowed the operational needs and benefits. DDM-powered CMDBs should address this gap and be essential for IT organisations seeking multicloud architectures, automating infrastructure changes, or deploying frequent application changes.