- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-29-2022 03:38 AM
I am trying to run discovery from my own instance on a process that is suggested from application finger printing. When I try to run discovery on a suggested application I get this message:
Failed to create pattern Error: There is no CI Type table: u_cmdb_ci_java_homegrown for group java_homegrown
This is my instance: twilsonsandiegodemo.service-now.com
Any thoughts?
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-29-2022 07:15 AM
Application fingerprinting are just suggestions of groupings based on the process data discovered when normal discovery runs. (typically LSOF and Netstat data).
To discover the application you have to create an application from the fingerprint. And three things will happen.
1. The table name you inputted on the form will be created if it is not an existing table.
2. A classifier will be created based on the ML group.
3. A pattern will be created.
Review the classifier and the pattern. As the pattern will be a generic stub and you will need to modify the identification section as well as any naming modifications you want to produce. I would recommend sticking with a application@host definition in the pattern but you may need to do something different based on your situation.
Also take advantage of the test harness on the classifier to ensure you are getting the right results back. You can add a few servers that you know the application / process exists on and when you save the form the test results will show up in the test tab.
Once you run discovery on a host you should see a new relationship of Runs::Runs on for the application on the server.
Hope this helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-29-2022 05:45 AM
Hi,
Check whether you have the table 'u_cmdb_ci_java_homegrown' in your instance. if not then create that table do the fingerprint
Regards,
Vivek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-29-2022 07:15 AM
Application fingerprinting are just suggestions of groupings based on the process data discovered when normal discovery runs. (typically LSOF and Netstat data).
To discover the application you have to create an application from the fingerprint. And three things will happen.
1. The table name you inputted on the form will be created if it is not an existing table.
2. A classifier will be created based on the ML group.
3. A pattern will be created.
Review the classifier and the pattern. As the pattern will be a generic stub and you will need to modify the identification section as well as any naming modifications you want to produce. I would recommend sticking with a application@host definition in the pattern but you may need to do something different based on your situation.
Also take advantage of the test harness on the classifier to ensure you are getting the right results back. You can add a few servers that you know the application / process exists on and when you save the form the test results will show up in the test tab.
Once you run discovery on a host you should see a new relationship of Runs::Runs on for the application on the server.
Hope this helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2022 01:19 AM
Hi Team,
I am trying to load demo data for the Order Status service and nothing I am trying is loading, I am evening running the Recompute sub-flow you told me about. Could you have a look at it for me please as I have two demos I need that for today. This is my instance: tywilsonsandemo.service-now.com
