CMDB Dashboard Completeness

[Brad Kallmeyer1]

Trying to understand how the "Completeness"   works with the Dashboard. We have 5 fields that are mandatory on the base configuration table (cmdb). However some of our classes these fields are not a required item and have a dictionary override on them. When we run everything with the dashboard these items are showing up as missing mandatory fields.

Question is when the jobs run at what table level are they running against? Anyway to get these items to not show up as failures in Completeness, it appears the dictionary override isn't the answer.

[VivekSattanatha]

Hi Bradley,

Usually, it will run from lower to upper class tables. So you should also configure it from lower to upper class in CMDB schema. Suppose if you give 5 fields mandatory for your base table then it will reflect all the tables which are extended from it. You cannot really sure those 5 fields will be there on all tables. So you should not configure like that. What you should do for an example, if you want to track 5 fields in server table then set those five fields in the server table and in the base table just keep name only as mandatory.

I set it up little bit different way for one of my customers. It is like the for the base CMDB table I set name only as a mandatory field. Then I selected some 7 fields mandatory for Server table, 5 fields for Netgear table, 3 fields mandatory for hardware table, 4 fields mandatory for Database instance table and 5 fields for Business service table. By this way, I can able to track all my mandatory fields without false information. Also, I made it sure whatever fields I choose for a table, those fields are reflected in the extended tables.

Regards,

Vivek

Based on the impact hit like, helpful or correct

[Brad Kallmeyer1]

We have Managed By, Owned By & Support Group as Mandatory on all several CI classes. When the system was setup these were set as mandatory on the base configuration item (CMDB) table, so all classes get these. If I take turn these to false, then I'm assuming a you would have to do a dictionary override rule on the the class table you want them for (Example: Server).

Is this how you accomplished it?

[VivekSattanatha · Accepted solution]

Hi Bradley,

Yes, you are right... Next-hop routing rule is one table which is extended is from CMDB base table only. When you give mandatory fields for CMDB base table it will inherit to all the tables extended from it. But you do not need to have Managed By, Owned By & Support Group fields has to be mandatory for the routing table.

If I have to select Managed By, Owned By & Support Group these fields as mandatory then I would select Hardware table.

Regards,

Vivek

Based on the impact hit like, helpful or correct

[Swap5]

HI Vivek,

I want my orphan rule only to run for some specific classes. Is this possible?

This is what I am trying :