- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2023 10:02 AM
Hi everyone,
So, we have a case where we have many data sources for the CMDB and we were making some reconciliation rules for Computers. The problem is that Computer and Server classes share some discovery sources but with different priorities, and that's preventing us from creating those rules. I will elaborate on this:
Computer class sources by priority:
- Source A
- Source B
- Source C
- Source D
Server class sources by priority:
- Source D
- Source E
- Source A
I didn't think that would be a problem since Child classes' rule override the parent's ones. But when adding Source A and Source D in the child class I get the following message:
The reconciliation rule is not unique. There is another rule with the same discovery source, overlapping attributes, and condition filter.
To avoid this conflict I'm thinking on simply adding a condition that will always apply for Servers and then to the Computer rules add a different condition that will always apply to computers. On paper that should work, but I guess there's a better, more solid way to do this.
Solved! Go to Solution.
- Labels:
-
Data Foundations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2023 10:10 AM
Apparently, adding the rule to the child class first does the trick. I still need to check if the rules work properly this way.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2023 10:10 AM
Apparently, adding the rule to the child class first does the trick. I still need to check if the rules work properly this way.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2023 08:12 AM
Thank you. Yes, this doesn't really work the way you might expect. Another solution I found is that when there is already an entry on the parent class, you can add a filter on the rule there, like "Class is not [Child Class]". Then you can create a new entry on the particular child class you want, without negatively affecting all the other child classes that might be inheriting the parent rule.
