Dynamic IRE
Summarize
Summary of Dynamic IRE
The Dynamic Identification and Reconciliation Engine (Dynamic IRE) is a ServiceNow engine designed to improve the accuracy and efficiency of Configuration Item (CI) identification in the CMDB. It replaces the traditional Static IRE, which relies on manually created identification rules. Dynamic IRE automatically updates identification rules during data ingestion, processes multiple conditions in parallel, and uses a broader set of CI attributes to reduce duplicates and improve match quality.
Show less
Dynamic IRE is applicable exclusively to the Hardware [cmdbcihardware] class and its descendant classes, with options to exclude specific hardware subclasses if needed. Excluded classes continue to use Static IRE.
Key Features
- Automated Identification Rules: Eliminates the need for manual creation and maintenance of IRE rules by updating rules dynamically during data ingestion.
- Improved Matching Logic: Uses parallel algorithms and a larger attribute set to enhance CI matching accuracy and reduce duplicate records.
- Modes of Operation:
- Simulation Mode: Runs Dynamic and Static IRE in parallel to compare results and performance, storing differences for review.
- Committed Mode: Runs only Dynamic IRE for CI identification, with the option to revert to Static IRE without impact.
- Class Exclusion: Allows exclusion of specific hardware subclasses from Dynamic IRE to maintain existing custom rules where necessary.
- Performance Comparison Tools: Provides parity scores and detailed comparison reports (including bar charts and JSON details) to evaluate effectiveness before committing.
Practical Usage and Implementation
- Testing Dynamic IRE: Customers should start by enabling simulation mode on a non-production instance to evaluate effectiveness against Static IRE.
- Reviewing Results: Use the CMDB IRE Output Comparison Items table and visual charts to analyze differences in CI processing and matching accuracy.
- Committing to Dynamic IRE: After satisfactory testing, commit to Dynamic IRE in production by agreement selection or system property configuration.
- Reverting to Static IRE: Switching back is straightforward and does not affect system stability.
Benefits for ServiceNow Customers
- Significantly reduces manual effort in maintaining CI identification rules.
- Improves CI match accuracy, leading to fewer duplicate CIs and a cleaner CMDB.
- Offers a controlled rollout with simulation mode to safely assess impact before full adoption.
- Maintains flexibility by allowing exclusion of certain classes and easy rollback to Static IRE.
Dynamic Identification and Reconciliation Engine (IRE) processes CI identification for maximum accuracy and efficiency and eliminates the need to manually create or maintain rules. Actually, you can't alter any of the algorithms or operations of Dynamic IRE.
When necessary to differentiate, the legacy, manually-driven IRE, is referred to as Static IRE.
Dynamic IRE is a new engine that you can choose to use instead of Static IRE. Dynamic IRE identifies CIs using an improved identification dynamic process and automatically updates its IRE identification rules during ingestion of data payloads.
Dynamic IRE evaluates various conditions within the payload simultaneously by running algorithms in parallel to score potential matches and to accurately determine CI identity across multiple data sources. Compared to Static IRE, on average, Dynamic IRE matches CIs using a larger combination of the CI attributes to improve the chances of finding an optimal match, and by so, reducing the chances for duplicate CIs.
Dynamic IRE is applicable only to the Hardware [cmdb_ci_hardware] class and its descending classes. However, you can configure the system to exclude from Dynamic IRE specific classes descending from the Hardware class.
- Usually identifies CIs more accurately resulting in a reduction of duplicate CIs.
- Eliminates manual configuration and continuous maintenance of IRE process rules.
Modes of operation
- Simulation mode
-
In simulation mode, Dynamic IRE and Static IRE run in parallel so you can experience and compare Dynamic IRE to Static IRE.
In simulation mode, both Static IRE and Dynamic IRE process the payloads, and any differences in processing and outcome are stored in the CMDB IRE Output Comparison Items [cmdb_ire_output_comparison_item] table. Also, after some time of simulations, you can compare the performance of Dynamic IRE to Static IRE.
- Committed mode
- In committed mode, only Dynamic IRE performs IRE processes and Static IRE is turned off. Once in a committed mode, you can switch back to Static IRE without implications.
Exclude classes from Dynamic IRE
There might be reasons for configuring child classes descending from the Hardware class, to be excluded from Dynamic IRE. For example, you might want to exclude a custom class with custom attributes, for which there are IRE rules that are based on those custom attributes. In this situation, it might not be beneficial to apply Dynamic IRE for that class and its descendants. So if Dynamic IRE is enabled, Static IRE is still being used for those excluded classes.
For more information, see Exclude classes from Dynamic IRE.
Simulate and commit to Dynamic IRE
- Use a user role that meets the role requirement: sn_cmdb_user.
- On a non-production instance, navigate to the CI Class Manager.
- In CI Class Manager, select Hierarchy and then select the Hardware class.
- In the Hardware navigation panel, select Identification Rule.
-
In the Dynamic IRE section, select Simulate Dynamic IRE.
- Carefully review the Simulate Dynamic IRE dialog box:
- If you're ready to start a simulation to test Dynamic IRE on a non-production instance, select Simulate Dynamic IRE without selecting 'I have simulated and assessed Dynamic IRE on a sub-production instance, and am now prepared to implement Dynamic IRE on a production instance.'. The simulation runs IRE processes on the Hardware and any descending classes, and then shows a comparison in terms of effectiveness and performance, between Dynamic and Static IRE. Carefully examine this comparison, which can help you determine whether to commit to using Dynamic IRE.
- If you have already completed a simulation, reviewed the results, and are ready to fully use Dynamic IRE with the Hardware class, on a production instance select the agreement and then select Commit to Dynamic IRE.
Alternatively, you can use the glide.identification_engine.dynamic_ire_enabled system property to enable or disable Dynamic IRE, and by so, switching between Dynamic and Static IRE. For more information about this property, see Properties for Identification and Reconciliation.
Switch back to Static IRE
- In CI Class Manager, select Hierarchy and then select the Hardware class.
- In the Hardware navigation panel, select Identification Rule.
- In the Dynamic IRE section, select Simulate Dynamic IRE.
Comparison of the results of Dynamic IRE and Static IRE
In simulation mode, you can see a comparison of the activities and outcome between Dynamic IRE and Static IRE, at a high level and at a record level. Examine the details in this comparison carefully to help you evaluate the effectiveness of Dynamic IRE in your environment before committing to using it.
Bar charts show the difference in CI operations of inserting CIs, updating CIs, and CIs found to be incomplete, between the two methods. Select a bar to show the list of comparison records from the CMDB IRE Output Comparison Items [cmdb_ire_output_comparison_item] table, for the selected bar chart. Those records contain the details about CIs that were processed differently between Dynamic IRE and Static IRE. Select a record to open it and to review the comparison details (in JSON format).
On a record form, you can select Summarize to show an organized and more user friendly presentation of the comparison results, generated by the Now Assist for CMDB IRE comparison record summarization skill.