Exclude CI's from Health Metrics

lucr
Kilo Expert

Hi,

We want to use the new CMDB Health dashboards for managing our CMDB. However within our company we do not delete CI's but give them a status of "Removed". Of course these CI's become stale over time or don't have the appropriate relations.

So my question is How can we exclude these CI's from the Health Collection Jobs.

I've looked and searched but cannot find it. First I thought the conditional field on the job could help us but that field only determines when the job is run not on which CI's.

Also tried to find the script include that handles the logic but i cannot find it.

Any help would be appreciated.

Kind Regards,

Luc

1 ACCEPTED SOLUTION

Hi Catherine,



We did not find a OOB solution to filter out certain CI's. Even got ServiceNow PS involved in the question but till this day no actual solution.



Did experiment with some business rules. The following one does its work. But does not cleanup after the CI is changed. So also create a business rule on the cmdb_ci that removes all cmdb_health_result after a certain condition is changed. This one is async rule.



Created a business rule on:


cmdb_health_result


Before business rule that will check for a certain condition on the CI reference field (dot-walked) and if true aborted the action so no insert.



I know it is not the nicest of solutions..



Greets,


Luc


View solution in original post

7 REPLIES 7

Deepa Srivastav
Kilo Sage

I am not very sure but can you apply filter on state field?



Mark Correct if it solved your issue or hit Like and Helpful if you find my response worthy.


Thanks,
Deepa


Hi Deepa - I haven't found a way to add any filters to the "Completeness" metric . Have you been able to find a way to do this?


catherine_rober
Giga Contributor

Hey lucr - I know it's been a while since you posted this. Did you find a solution to this? I have the same question.


Hi Catherine,



We did not find a OOB solution to filter out certain CI's. Even got ServiceNow PS involved in the question but till this day no actual solution.



Did experiment with some business rules. The following one does its work. But does not cleanup after the CI is changed. So also create a business rule on the cmdb_ci that removes all cmdb_health_result after a certain condition is changed. This one is async rule.



Created a business rule on:


cmdb_health_result


Before business rule that will check for a certain condition on the CI reference field (dot-walked) and if true aborted the action so no insert.



I know it is not the nicest of solutions..



Greets,


Luc