- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2020 04:19 AM
SInce our Upgrade to NY I have started seeing Discovery Status with Description="Discover CIs API" with no Schedule. The Discovery Status is being created by people who don't have discovery roles and at best have cmdb_read and cmdb_query_builder roles (as well as others).
This thing runs a ServiceDiscoveryProbe against the target Endpoints. Now I discovered this because I had a couple of "@servername" Oracle Instances discovered by DiscoverySource=CredentiallessDiscovery which I was surprised by because we have mid.discovery.credentialless.enable=false
I thought it might be the "Discover Now" UI Action but that has a constraint of gs.hasRole('discovery_admin') and these people don't have that or admin.
Solved! Go to Solution.
- Labels:
-
Discovery
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2020 07:22 AM
Duane I don't think this is 100% new in New York but maybe it got turned on but check Change Management. There was an option in there where when a change finished it would auto trigger a discovery of that CI. I have a feeling it's going to be something like that that is causing it. Hope this helps.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2020 12:18 PM
HI Duane,
I am having the same issue as you did and have a quick question:
Did you find which business rule is doing this and what did you change on that rule?
Thank you
bk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2021 05:26 AM
Hello BK
BR which controls this behavior are :
Trigger Auto Discovery
Trigger top down Discovery
When state has been changed to Review on change_request These BR are triggered.
System property for it is :com.snc.change_request.disco.auto.state
Regards
Marcin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2024 04:20 PM
Thank you @DuaneNMore, @robertgeen, and @Marcin Witosla1! This just helped me find the root cause of a cancelled Discovery job based on a decommission change request going to Review. I had no idea why I was seeing "Refresh processes and connections" discovery jobs being kicked off.
Erik