We're looking for guidance on the best practice for creating a direct CMDB relationship between Cloud Servers (cmdb_ci_server) and Premium Services.
Current Relationship Structure
At present, we do not have a direct relationship between the Cloud Server and the Premium Service CI.
The relationship chain currently looks like this:
Requirement
We would like to understand:
- What is the recommended ServiceNow CMDB approach to establish a direct relationship between a Cloud Server (cmdb_ci_server) and a Premium Service CI?
- Should this relationship be created through:
- CMDB Relationship Rules?
- Service Mapping?
- A custom automation/business rule?
- Is there a standard relationship type that would be appropriate (e.g., Depends on :: Used by, Runs on :: Runs, Consumed by :: Consumes, etc.)?
- Has anyone implemented a similar model where the Cloud Service Account acts as the intermediary, but a direct server-to-service relationship is also required for reporting, impact analysis, or service mapping?
Objective
Our goal is to enable easier impact analysis and reporting by allowing users to navigate directly from the Cloud Server to the associated Premium Service without traversing multiple CI relationships.
Any recommendations, best practices, or implementation examples would be greatly appreciated.
