CMDB Health Inclusion Rules Questions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2025 04:01 AM
Xanadu Patch 6, all plugins updated
I'm not having any success with setting up rules in the CI Class Manager. Nothing changes after I set up rules and run the scheduled jobs.
For example, I want to exclude retired CIs so I set up an Inclusion rule on Configuration Item as follows:
Active Record Condition Install Status in (Installed, Pending Install)
I also set up similar Health Inclusion Rules on Configuration Item for Duplicates and Staleness. That is, I only want CIs with Install Status in (Installed, Pending Install) to be included when checking for Duplicates and also for checking for Staleness.
Nothing changes after the scheduled jobs run. I thought that by setting the rules at the top level (i.e. Configuration Item) means the rules apply to all classes.
What am I missing here? How should I be setting this up so that only CIs with Install Status in (Installed, Pending Install) are included?
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2025 06:18 AM
As far as I know, the only inclusion rule set up in CI Class Manager is the one on Configuration Item set up on the Identification Rule page under Inclusion Rule:
I spot checked several other classes under Configuration Item and did not see any other inclusion rule defined but it would be easier to check the table this is stored in rather than checking each class. Do you know what table this is stored in?
These are the only Health Inclusion rules that are defined:
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2025 06:35 AM
Hello @mah1
Yes, Please check on "cmdb_health_config" table for the list of all inclusion rules on all classes.
Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket.
Regards,
Shivalika
My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194
My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2025 06:38 AM
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2025 06:41 AM
Hello @mah1
So, now the conditions and everything here is correct and the scheduled job which are mapped to these metrics are also correct ?
Even after all this is it still displaying incorrect result ?
Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket.
Regards,
Shivalika
My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194
My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2025 06:56 AM
As far as I can tell, the conditions are correct. I'm not aware of any changes made to the scheduled jobs.
The info displayed on the CMDB Workspace appears to be the same as it was before the inclusion rules were created; the scheduled jobs were rerun after the rules were added. That is, the CI Count under Duplicate CIs and the CI Count under Stale CIs are the same as before the inclusion rules were added.
We also edited the staleness rule changing the effective duration from 60 days to 365 days to see if the staleness count would drop but it remained the same.
Thank you