Discovery is not triggering application patterns after Application Dependency Mapping probe( ADM)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2023 06:30 PM
Hi,
I have an issue with discovery. Discovery completed after finishing Application Dependency Mapping probe( ADM probe) step.
both patterns it launched are from Unix classy and the patterns it did not launch are application patterns.
following are the steps it went through:
shazzam
JavascriptProbe
MultiProbe(UNIX - Classify)
HorizontalDiscoveryProbe(linux pattern)
HorizontalDiscoveryProbe(UNIX Cluster - veritas pattern)
I dont see any errors in discovery.
adding @VivekSattanatha
SSHCommand
MultiProbe(ADM)
- Labels:
-
Discovery
-
Orchestration (ITOM)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2023 09:53 PM - edited 06-27-2023 09:53 PM
Hi @venkat101 ,
Which application patterns it did not trigger?
OOB do we have classifier and pattern created for that application?
Thanks
Venky
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-28-2023 06:13 AM
All custom patterns.
Yes, classifier is created and working.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2023 09:54 PM
HI @venkat101 ,
I trust you are doing great.
- Verify Discovery Probe Execution: Confirm that the necessary probes were executed during the discovery process. You mentioned the following probes were launched:
- Shazzam
- JavascriptProbe
- MultiProbe (UNIX - Classify)
- HorizontalDiscoveryProbe (Linux pattern)
- HorizontalDiscoveryProbe (UNIX Cluster - Veritas pattern)
Ensure Probe Configurations: Check if the configuration of the probes involved in the discovery process is correctly set up. Ensure that the probes are configured to capture application patterns as well.
Review Application Patterns: Review the application patterns defined in the system. Verify that they are correctly configured and associated with the relevant CI (Configuration Item) classes.
Validate Discovery Logs: Examine the discovery logs to ensure that there are no errors or exceptions reported. If there are any errors, investigate and address them accordingly.
Debug Application Patterns: If the issue persists, it might be necessary to debug the application patterns to identify any potential issues or misconfigurations. Analyze the pattern scripts and ensure they are designed correctly to identify the desired application components.
Test Discovery: Perform a test discovery using the application patterns and monitor the logs to verify if the patterns are being launched successfully and capturing the desired application information.
Was this answer helpful?
Please consider marking it correct or helpful.
Your feedback helps us improve!
Thank you!
Regards,
Amit Gujrathi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-28-2023 06:16 AM
Hi Amit,
I verified all the points you mentioned. It used to work perfectly fine in the past. suddenly custom patterns stopped working.