Best way to map database cluster CIs in the CMDB?

[gmm1]

We are designing the CI taxonomy of databases in preparation for loading them into the ServiceNow CMDB, and we've run into some problems figuring out the best way to implement database clusters.   We have multiple types of databases and not all of them are clustered, but Oracle clusters are the most common.   The prevailing examples online seem to use either the "Cluster" CI type or create a new CI type named something like "Database Cluster".   Obviously, either of these solutions would work, but we want to be mindful of setting this up in a way that could prevent us from using features in upcoming releases and integrating with plug-ins, especially in regard to implementing Service Mapping.

Using an Oracle database cluster as an example, looking at the out-of-the box CI classes and relationships, it looks like Database (cmdb_ci_database) and Oracle Instance (cmdb_ci_db_ora_instance) could easily represent the logical database (clustered or not) and running software respectively, by using appropriate attributes (e.g. cmdb_ci_database.clustered & .cluster_type, etc.) and relationships (e.g. cmdb_ci_db_ora_instance Runs on::Runs cmdb_ci_server, cmdb_ci_database Members::Member of cmdb_ci_db_ora_instance, and cmdb_ci_appl Depends on::Used by cmdb_ci_database, etc.).

My questions are essentially 1) Does this type of model make sense? 2) Is there a better way to do it?

[jeremy_perdue]

That makes sense and sounds like you guys are doing right Graham. Best of luck on your implementation!

Best Regards,

Jeremy Perdue, ServiceNow Consultant | Contender Solutions

[munwong]

Hi Graham,

I know it has been about 4 months since your implementation, how did you end up mapping DB clusters in CMDB?

Best regards,
Mun

[richard_selby]

As per above, how did you approach this and what do you think in hindsight?