Standard cmdb_ci reference qualifier for Incident table for use with Discovery

Chris Petrone
Tera Expert

I am looking to see if there is a standard practice reference qualifier for the cmdb_ci Dictionary entry for use with Discovery. It is my understanding that you should not show Business Applications, Software, etc in the cmdb_ci. It should be reserved for Servers, Databases, hardware, etc.

1 ACCEPTED SOLUTION

s4scott
Tera Guru

Best practice is to identify the CI Classes that should be used in tickets: Computer, Server, Network, Application Service, etc. and identify them in the CMDB Class Manager as a Principal Class. Then use that Principal Class flag in the reference qualifier for the configuration_item fields on tickets, often in addition to using Operational Status (legacy) or Lifecycle State (current) to filter for active or operational CIs.

Refer to this article for more information: Update the list of classes in the Principal Class filter

View solution in original post

5 REPLIES 5

s4scott
Tera Guru

Best practice is to identify the CI Classes that should be used in tickets: Computer, Server, Network, Application Service, etc. and identify them in the CMDB Class Manager as a Principal Class. Then use that Principal Class flag in the reference qualifier for the configuration_item fields on tickets, often in addition to using Operational Status (legacy) or Lifecycle State (current) to filter for active or operational CIs.

Refer to this article for more information: Update the list of classes in the Principal Class filter

Ok this makes sense. But after selecting the principal classes from the CI Class Manager, how would you then filter it for only those classes on the cmdb_ci field for an Incident?

Looks like it is automatically filtered with a sys property, com.snc.task.principal_class_filter, but my instance seems to be missing this.

Add this query to the reference qualifier for the configuration item field: 
sys_class_nameINjavascript:new PrincipalClass().getPrincipalClasses()