Query on Next Hop Routing Rule 'dscy_route_next_hop' , using Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā06-21-2019 06:36 AM
Hi,
We are using Discovery. There are lakhs of records created in 'Next Hop Routing Rule' (dscy_route_next_hop) table.
Due to this, the CMDB health dashboard is low (says duplicates in the CMDB correctness scorecard) and in Duplicate CI's report. How to not show the 'Next Hop Routing Rule' in the Health Dashboard or how to avoid this situation.
Thanks!
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā06-22-2019 11:43 AM
Nik,
Have you set up your Health Inclusion rules via the CI Class Manager? And for duplicates, under the Identification Rule, you can establish the "Health Inclusion Rule (Advanced)" to filter on only those classes that you manage and want to be included in the dashboard.
This is demo data from my PDI and shows that the Printer CMDB class is excluded. The other "Health" > "Health Inclusion Rules" option for the other dashboard metrics.
It's not always straightforward but if you develop a strategy on which classes and potentially which attributes to use, you can create some efficient rules.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā06-23-2019 11:37 PM
Hi Larry,
By doing so (Inclusion Rule (Advanced)) , wouldn't that prevent Discovery from writing to the cmdb for that CI class.
Nik

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā11-07-2019 04:27 AM
Have you got any solution for your issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā11-07-2019 06:42 AM
The solution to this is what is stated above. You need to put in a CMDB Health Inclusion (not a identification inclusion) rule. The filter you can use for this table is where name is not blank which should cause it to return none of those CIs and they shouldn't flag on the dashboard anymore. I would suggest you do this with other tables as well such as the next hop routing rules but the original reply is the proper answer to this.