Create a CI reconciliation rule
Create a static or a dynamic CI reconciliation rule.
If both, static and dynamic reconciliation rules exist for the same CI attribute, the dynamic rule has precedence.
Create a static reconciliation rule
A static reconciliation rule specifies class attributes that discovery sources are authorized to update, and prevents unauthorized discovery sources from overwriting the attributes' values. A static reconciliation rule also specifies the prioritization among multiple discovery sources. Without static reconciliation rules, discovery sources can overwrite each other's updates to attribute values.
Before you begin
About this task
Static reconciliation rules are used in conjunction with data refresh rules to determine reconciliation steps for a CI. These rules determine if, when, and by which discovery source a CI can be updated. If multiple discovery sources are authorized to update the same class attributes, assign a priority to each of these discovery sources to prevent them from overwriting each other's updates.
- The lower priority source is the first source updating the CI.
- The CI became stale based on data refresh rules for the CI class. However, a reconciliation rule that applies to all attributes, doesn’t have precedence over a lower priority reconciliation rule that applies to a specific attribute, even if the CI is stale.
- Rule configured for a specific attribute, has precedence over rule set with Apply to all attributes (regardless of priority value).
- Between two rules for the same attribute or between two rules set with Apply to all attributes, the rule that is specific directly for the class has precedence over the derived rule.
- Between two rules for the same attribute or between two rules set with Apply to all attributes at the same class level, precedence is determined by rule priorities.
Information about the last discovery source that updates each attribute is stored in the Data Source History [cmdb_datasource_last_update] table, but only after enabling the reconciliation rule. Therefore, there might be unexpected updates after you enable the rule until the highest priority data source has updated the CI.
Static reconciliation rules affect reconciliation of stale CI attributes. During reconciliation, the information in the Data Source History table is considered along with the data refresh rules for the CI's class, to determine if a CI attribute is stale. A CI attribute is determined to be stale if it was not updated by the latest discovery source to update the CI, within a time period. The time period is specified by the Effective Duration time in the data refresh rule for the class for the discovery source. In this case, if another authorized discovery source, with a lower priority attempts to update the stale CI attribute, the update is allowed.
If there is a dynamic reconciliation rule for the same CI attribute as in a static reconciliation rule, the dynamic rule takes precedence.
Procedure
What to do next
- Select the filter icon and then select:
- Attributes: To show only reconciliation rules for a specific attribute.
- Discovery sources: To show only reconciliation rules for a specific discovery source.
- Select Preview Rule to see per attribute, the precedence order between any discovery sources that are authorized to update that attribute and any dynamic reconciliation rules.
- If CMDB 360 is enabled, you can:
- Select Preview Data to see all attributes for a specific CI. Also, for each attribute, the current CMDB value and discovery sources reported values for the attribute.
- Select Recompute to recompute CI attribute values after changing reconciliation rules.
- Navigate to to see a list view of all definitions of reconciliation rules.
Create a dynamic reconciliation rule
A dynamic reconciliation rule uses CMDB 360 data to choose a value such as the largest value that is reported, for updating a CI.
Before you begin
Role required: sn_cmdb_editor and itil have read access, sn_cmdb_admin and itil_admin (on top) have full access
About this task
If the same CI attribute has both, a static reconciliation rule and a dynamic reconciliation rule, the dynamic reconciliation rule has precedence.
A dynamic reconciliation rule supports several rule types, such as largest reported value and most reported value. When applying a dynamic reconciliation rule, IRE processes the current payload and then examines the CMDB 360 data store to select a value with which to update the CMDB. Depending on the dynamic reconciliation rule type, selecting the appropriate value might not be immediately conclusive. For example, there might not be a single value that is most reported, or for some values, the last discovered timestamp isn't reported. Therefore, when necessary, IRE falls back to examining additional details such as last reported, last discovered, and last updated values to select the most appropriate value.
Procedure
What to do next
- Select the filter icon and then select:
- Attributes: To show only reconciliation rules for a specific attribute.
- Discovery sources: To show only reconciliation rules for a specific discovery source.
- Select Preview Rule to see per attribute, the precedence order between any discovery sources that are authorized to update that attribute and any dynamic reconciliation rules.
- Select Preview Data to see all attributes for a specific CI. Also, for each attribute, the current CMDB value and discovery sources reported values for the attribute.
- Recompute CI attribute values.
- Navigate to to see a list view of all definitions of reconciliation rules.