Fine-tune discovering applications based on processes, if the discovery results are not
satisfactory.
Modify default settings for fingerprint-based discovery if this feature does not generate any suggestions or does not generate. In addition, you may also fine-tune the generated suggestions to make them
relevant and useful.
Ensure that the fingerprint-based discovery generates suggestions
Fingerprint-based discovery relies on Predictive Intelligence for generating suggestions for discovery. If the Application Fingerprints dashboard does not display any suggestions, ensure that the Predictive Intelligence is configured correctly.
Before you begin
Confirm
that fingerprint-based discovery remains enabled, since it is enabled by default. To verify, navigate to All > System
Properties > All Properties. Check that the sys_property process.clustering.appfingerprint.enabled property does not appear on the list.
Role required: discovery_admin
About this task
If the Application Fingerprints dashboard does not display any suggestions, perform the following steps. After every action, check if the issue persists.
Procedure
Ensure that Predictive Intelligence is installed and active.
Navigate to System Definition > Plugins.
Search for Predictive Intelligence.
Verify that the Predictive Intelligence plugin is installed.
If Predictive Intelligence is not installed, click the Install button.
Click the Predictive Intelligence tile.
On the Predictive Intelligence form, verify that the Status is Active.
If the status is Inactive, click the Activate/Repair link under Related Links.
Ensure that the scheduled job controlling the fingerprint-based discovery, is enabled and configured correctly.
Navigate to System Definition > Scheduled Jobs.
Select the Applications suggestion - ITOM Autodisco scheduled job from the list.
Ensure that the Active check box is selected.
Check that the discovery frequency is set to one hour as shown in the following example:
Check that the clustering solution responsible for grouping processes into suggestions is active.
Enter ml_solution.list in the Filter navigator field of the Navigation panel.
The ML Solutions tab displays all solutions, including clustering solutions.
Identify clustering solutions by checking the Table column.
The system saves clustering solutions in the Virtual running processes [v_cmdb_running_process] table.
If there are several clustering solutions, identify the latest solution by the timestamp in the Update column.
Alternatively, you can use the number that the system appends to the solution name to identify the latest solution.
Verify that the State value is Solution Complete and Progress is at 100%.
Check that the Application suggestion - ITOM Autodisco transaction is not slow-loading, as described in View and kill active transaction.
If this transaction is running for a long time, kill it.
Fine-tune suggestions for fingerprint-based discovery
Adjust definitions of process-based suggestions before starting discovery. Typically, you need to fine-tune automatically generated suggestions if the accuracy is less than 100%. Predictive Intelligence creates suggestions and provides the accuracy estimate for each suggestion. The lack of accuracy may result in the failure to discover required applications or the discovery of wrong applications in
addition to the correctly discovered applications.
Before you begin
Role required: discovery_admin
Procedure
Navigate to All > Discovery > Home.
Click Application Fingerprints.
The Application Fingerprints dashboard opens.
Navigate to the list of suggestions by one of the following methods:
On the Top Suggestions pie chart, view the top
suggestions arranged by the number of processes making up these
suggestions.
To view only suggestions for application servers, click the
Suggested Application Servers tile. The
filtered list of suggestions for application servers is displayed. This
list is also filtered to display only suggestions whose accuracy is
100%.
Alternatively, click All suggestions. The
unfiltered list of all suggestions is displayed.
In the Application Suggestions list, click the relevant suggestion in the
Suggested Group Name column.
The Application Suggestion form opens.
To change the name used for the fingerprint-based application, enter the preferred name in the Name field.
For example, many applications run java processes and the suggested group name for these groups is java. You may want to assign a name that better describes the application that you want to discover
using this suggestion (for example, java_myweblogic).
To change the name used for the CI class, enter the preferred CI class name in
the Suggested CMDB CI Class field.
To fine-tune the classifier rule, change the regular expressions in the
Suggested Classifier Rule field.
For example, add version information to the regular expression for discovering
a Tomcat application: .*tomcat.*
-Dopss.*version=12.1.3.*
Adjust regular expression used for fingerprint-based discovery
Fine-tune the regular expression in the classifier rule to make discovery results
more precise. Predictive Intelligence extracts regular expressions from processes
and assigns them to classifier rules as part of creating suggestions. If you are not
satisfied with the discovery results or the suggestion accuracy is lower than 100%, modify
the regular expression.
Before you begin
Role required: discovery_admin
Procedure
Navigate to All > Application > Module.
Click Discover Application.
The fingerprint-based discovery finds the application and creates a
CI class, a classifier, and a pattern.
On the Application Suggestions list, click the newly
created process classifier.
The Process Classification form opens.
In the Parameters value field under Condition, notice the regular expression automatically selected by Predictive Intelligence.
In this example, it is ."-DweblogicName=."
Click Padlock icon next to Test with.
Click the Look up icon to select the server on which you want to test additional regular expressions.
The list of all discovered servers opens.
Select the sever that runs the application that you want to discover using
the customized classifier.
The selected server appears in the Test with
field.
Right-click the header of the Process Classification form and select
Save.
The system runs a test and displays the results on the Test results tab at the bottom of the page.
On the Test results tab, check the processes that were discovered using the
regular expressions configured for this classifier.
Adjust the regular expression in the Parameters value field under Conditions.
For example, make it more generic: "weblogic."
Right-click the header of the Process Classification form and select
Save.
The system runs the test again and displays the results on the
Test results tab at the bottom of the page.
On the Test results tab, verify that the fingerprint discovery found the
applications as you expected.
Disable fingerprint-based discovery
By default, the fingerprint-based discovery is enabled. Disable application discovery
based on processes, if Predictive Intelligence does not generate enough
processes.
Before you begin
Role required: discovery_admin
Procedure
Add the system property sys_property process.clustering.appfingerprint.enabled as described in Add a system property.
To disable, enter false in the
Value field.
To enable the fingerprint-based discovery again, change the
Value field to true.
next to Test with.
to select the server on which you want to test additional regular expressions.
The list of all discovered servers opens.