Exclude Discovery Pattern per device or schedule
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2024 02:50 AM
Hello,
i have a bunch of Oracle Databases on Linux which should not be discovered because they are third party and we dont have any DB User access to those. At the moment the Linux Discovery connects via SSH, recognizes the Oracle Processes and tries to discovery the Oracle Databases which ends in failed logon attempts on those DB Systems.
Is there a way to disable specific patterns for specific servers/ips and/or schedules?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2024 12:51 AM
You can try disabling oracle db on unix pattern.
Regards,
Pratiksha

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2024 09:15 AM
Hi @Tone1,
You can achieve this at CI Process Classification (discovery_classy_proc) table on Oracle Instance table by modifying the filter. Add all the vendor managed servers at computer field that should not be discovered. please refer screenshot 1. If you think that's a manual process to add to computer names to filter, then update all these servers with computer.vendor field populated in the server table. Then add filter in the ci process classification table vendor is not equals "hp" (for example) that should fix your issue. please find the screenshot 2 in the attachment.
Please mark my solution as helpful or accept the solution.
Regards,
Srinija
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2024 11:55 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2024 02:40 PM - edited 07-30-2024 02:50 PM
Hi @Tone1 ,
I tried on oracle on unix pattern by adding computer not contains filter "server name" to the oracle instance ci classifier. It worked for me; Discovery did not trigger the oracle on unix pattern after applying the condition at ci classifier level. I am pretty sure, ci process classification is where we need to add the filter to exclude but then not sure, why it is not working at your end.
Regards,
Srinija