How to model the Database tracking in CMDB?

kiran-ravin
Tera Contributor

3 weeks ago

Hi All, 

We are currently working on creating a fundamental data model for our CMDB and need your help in creating a data model for Database tracking in CMDB. 

 

Currently we have database in On-prem and cloud with multiple database types such as MS SQL, Oracle, Mango DB, Dynamo DB etc.  I have created a draft data model version based on deployment that consists of database(cmdb_ci_database) and sub classes such a  MSFT SQL  Instance (cmdb_ci_db_mssql_ instance), DynamoDB Table(cmdb_ci_dynamodb_table), Cloud Database (cmdb_ci_cloud_database). 

 

Not sure if this is correct and  if we still need cloud database sub class etc. We wanted a simplified version of it where stakeholders can easily understand and track it in one class. So please share your thoughts.

 

Preview file
800 KB
0 Helpfuls
  • 266 Views
1 REPLY 1

Fabian Kunzke
Mega Sage

2 weeks ago

Hey,

 

so this looks good - with a small exception. Generally i recommend to model infrastructure based on how ServiceNow runs the discovery. This almost always aligns the model with how ServiceNow would do it. For database discovery you can find that here: https://www.servicenow.com/docs/r/xanadu/it-operations-management/itom-visibility/mssql-data-collect...

 

Now, theoretically speaking the only issue is see with your model is the direct link towards databases. I understand that this is tempting, but I would argue against it. I detailed this here: https://www.servicenow.com/community/common-service-data-model/wiimlt-mssql-databases-amp-database-i...

 

Outside of that, you may want to investigate if you want to have an application CI between your application instance and the infrastructure as well. See this article here: https://www.servicenow.com/community/common-service-data-model/wiimlt-the-application-ci/ta-p/348563...

 

But honestly, this looks generally good. All in all I'd just like to see the database link to be cleaned up.

 

Regards

Fabian

0 Helpfuls