When working with ServiceNow Discovery and CMDB, one of the main lessons learned in practice is that Discovery should not be treated as an isolated platform feature. In reality, it is a structural component that directly impacts modules such as Hardware Asset Management (HAM), Software Asset Management (SAM), and critical IT governance processes.
Many implementations begin by treating Discovery merely as an infrastructure scanning tool. However, without a well-defined architecture, the result is often a CMDB with inconsistent data, duplicate Configuration Items (CIs), and low historical reliability.
A mature Discovery implementation needs to be aligned with the CMDB architecture, ensuring that the data collected truly supports operational and strategic decisions over time.
Discovery is not just about infrastructure discovery.
A common mistake in ServiceNow projects is enabling Discovery before defining the CMDB data model. When this happens, the tool starts inserting records without clear quality criteria.
To avoid this problem, it is essential to define beforehand:
- Configuration Items Classes
- Required attributes
- Necessary relationships
- Identification strategies
- Data governance rules
Without this structure, the Identification and Reconciliation Engine (IRE) operates without consistent criteria, which can lead to duplicate records or incorrect overwriting of attributes.
The importance of an identification strategy
In more mature corporate environments, identifying a CI (Critical Integrity) doesn't depend on just one attribute. Typically, a combination of technical keys is used to ensure accuracy.
Among the most common identifiers are:
- Hostname
- Serial Number
- UUID
- MAC Address
- Cloud Instance ID
Each of these attributes has validity in specific contexts. For example, the serial number is more reliable for physical hardware, while the instance ID is essential in cloud environments.
A well-defined identification strategy ensures that the IRE is able to correctly reconcile the discovered data., avoiding duplication in the CMDB.
Relationship-oriented discovery
Another critical point is understanding that Discovery should not focus solely on individual CIs. The true value of CMDB emerges when infrastructure components are connected by consistent relationships.
Some fundamental relationships include:
- Runs On – applications running on servers
- Hosted On – virtual machines hosted on hypervisors
- Depends On – dependencies between applications and databases
Without these relationships, CIs become merely isolated records, with little value for impact analysis, change management, or governance.
Continuous governance of CMDB
Even with a well-defined architecture, data quality depends on ongoing governance.
This includes:
- CMDB periodic audits
- Review of identification rules
- Relationship validation
- Monitoring the quality of attributes
This process ensures that Discovery continues to support reliable data over time, even with changes in infrastructure.
Conclusion
ServiceNow Discovery should not be treated merely as an infrastructure discovery mechanism. It is a fundamental component of the CMDB architecture and platform data governance.
When guided by architecture, conscious identification, consistent relationships, and continuous governance, Discovery ceases to be merely a data collector and becomes a tool to support reliable decisions within IT operations.
Article produced by Bruno Ferreira, Technical Director of 4MATT.
Bruno Ferreira began his professional career in Information Technology in 2002. That same year he enrolled in a Computer Science course. He developed his technical skills in Microsoft technologies, delivering complex projects focused on directory services, messaging, and collaboration. In 2012, he began dedicating himself exclusively to the discipline of Software Asset Management (SAM). Having worked in this field for over 10 years, he is strongly committed to helping clients and partners achieve software governance on-premises or in the cloud.
He holds current certifications recognized by leading cloud management platform (CMP) and SAM manufacturers. The training and certification he undertakes annually through IAITAM – International Association of Information Technology Asset Managers – keeps him updated and qualified to manage IT assets in organizations of all sizes and sectors worldwide.
