Switching from Probe-based Discovery to Pattern-based Discovery
This procedure is relevant only for customers who upgrade to Jakarta or later releases and want to begin using patterns for horizontal discovery.
New instances of Jakarta or later do not require this procedure.
Beginning with the Jakarta release, you can use horizontal discovery patterns to find new configuration items (CIs). Patterns provide a simpler and more intuitive way to debug and troubleshoot discovery compared with legacy probes and sensors.
Probe-based discovery and pattern-based discovery use different mechanisms of saving data in the CMDB. Using both discovery methods together may result in duplicate data in the CMDB. In addition, pattern-based discovery relies on relationships, while the legacy probe-based discovery uses references.
For detailed information about the difference between probe-based and pattern-based horizontal discovery, refer to the product documentation.
The platform provides default scripts that create relationships for CI types that you want to discover with patterns instead of probes. You can create relationships for these CI types:
- Load Balancers
Enable the pattern and disable the probes.
Navigate to Discovery Definition > CI Classification and select a relevant CI classification, such as UNIX.
On the Classifications page for this CI type, select the specific classification, such as Linux.
Select the Triggers probes tab.
Locate the Horizontal Pattern in the list and change the Active setting to true.
Set the Active setting for the probes to false.
NOTE: For probes in the Linux family or Windows, keep the ADM Probe and Install Software Probe active (Active="true").
Create relationships for CI types that you want to discover using patterns by clicking the relevant migration module under Pattern Designer in the Navigation pane. For example, click Migrate Load Balancer to Pattern for CIs belonging to the load balancer CI type.
Check out the migration scripts to identify the scripts that you want to use under System Definition > Script Includes. Typically, migration script names start with the word "Fix" and contain the word "Pattern", for example, "FixWindowsModelForPatterns".
- Click the name of the relevant script and note the first operation that it contains.
- Navigate to System Maintenance > Scripts - Background.
- In the Run script pane, enter the script class for calling the operation that the migration script uses. For example,
- Click Run script.