Urgent: Problem with CMDB Health Inclusion Rules

[Nitin15]

I have configured a Health Inclusion on "Linux Server" class as I only want to have calculations run for this class. 

Still when I go to "cmdb_health_result" table I can see result for all sort of classes. Computer, printer, ip, switch etc. 

And I am sure I don't have inclusion rules configured for those. 

[jimmillet]

Still not understanding the "inclusion".  I am at Madrid and setting up the CMDB Completenesss Scorecard, and I have set up the inclusion rules on "all the classes I care about" (mainly server, network, database instance, and 'middleware' applications). But it looks like the denominator shown on the dashboard is the "entire CMDB"!!! I would've expected to only see the count of the classes I marked with inclusion rule!

We have default value for "Status" (install_status) to be "Pending Install" and then only move the classes we care about to "Installed" status. So as a test, I just went to top of tree (Configuration Item) and set inclusion rule here to be "Status = Installed" and clicked execute now on the dashboard job. But whenever I click execute now on that job it never seems to update the dashboard until the 2am nitely scheduled run.

I saw in other posts that default behavior is to include "all" CI's and you had to "opt out" to exclude CI's that you did not want. I'll let you know if my update worked, but really curious how other people have set this up to only look at classes they "care" about.

Thanks,

Jim

[amititp]

Few other ways you can adopt your criteria is via Parent Class ( H/W ) Rule with filter to LINUX Type only. In addition, you can use Groups to have Health filter via Group of Server Class.

[jimmillet]

Here is the answer to the issue I was facing. I did not fully appreciate that you had to opt-out any CI class you did not care about. All I had done previously was add the Health inclusion rule conditions to the classes I cared about, but that included all the other classes in the various other branches of the CI class hierarchy. So I had to go up to the top of the tree (at Configuration Item (cmdb_ci) level) and add an inclusion rule that would exclude all the classes I don't care about, and then combined with the inclusion rules I already had in place at the lower levels gave me the denominator that I needed.