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
05-15-2025 05:51 AM
Did you get to the bottom of this; I'm seeing a similar behaviour myself!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-21-2025 06:43 AM
-
Validate Running Processes: Ensure that the running processes of the custom application/applications are detected once the ADM probe completes. The infrastructure host pattern should pick up the running processes at this stage.
-
Verify Application Pattern Association: After the running processes are detected, ensure that the corresponding application pattern is automatically applied (Out-of-the-Box), provided the patterns are associated with the process classifiers record of the custom application.
-
Check OS Configuration: If unsure about the application host, verify that the Operating System field in the application pattern is set to [All]. Also, ensure the pattern is enabled for both operating systems if applicable.
-
Ensure Process Classification is Enabled: Confirm that the Enforce Process Classification checkbox is checked in the pattern configuration. This ensures that the process classification rule is applied.
-
Synchronize Patterns with MID Servers: If you've recently made changes to the application pattern, make sure to synchronize the pattern with the MID Servers to ensure the latest updates are applied.
-
Retry Discovery: After completing the steps above, re-run the Discovery process to verify that the issue is resolved and the custom application is discovered properly
------------------------------------------------------------
If my response is helpful, I would appreciate it if you could mark it as 'Accept as Solution' and click 'Helpful.' This helps both the community and me. Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2025 03:02 AM
Thanks for this; it was the missing link to my problem 😉
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2025 07:11 AM
Thanks @dhowell happy that it helped !!