CI Settings/Property to disable update from Discovery

[manddar]

Hi,

I have some CIs created manually in CMDB, however when Discovery started one of the CI (created manually) discovered and updated by discovery process.

I want to disable discovery update for some CIs, is it possible?

if yes, Please tell me the solution.

Thanks in advance

Mandar

[lawrence_tse]

Nothing out of the box, but you can create something like a custom field and use it like a flag for manual entries vs discovery entries.

Then probably create a before query business rule to pull non-flag CI if the updated by is discovery.

[doug_schulze]

To add onto Lawrences' very good idea, you might even consider adding that logic in your discovery identifier instead of a BR...Will accomplish the same but this way you can ensure that the Exploration phase does not take place other then asking the questions and getting rejected when trying to update

[Bhavesh Jain1]

As a best practice, all the CIs that gets created via Job should be done in a common name like

Create By - Discovery

So Discovery is the user.You can do see by setting the Run As field in the discovery Job.

Once you ensure that all the Cis gets inserted/updated in the name of Discovery, you can easily differentiate between manual entries and discovered entries.

in the onBefore transform script of your transform map, you can write this condition :

if(target.sys_created_by != 'discovery' && action == 'update')

{

ignore = true;

}

Regards,

Bhavesh

http://www.igate.com

[DanLevin · Accepted solution]

Hi Mandar,

If the IPs of the CIs you'd like Discovery to not update are encompassed in an IP range within one of your Discovery Schedules, it can be a pain to spit up that range into smaller slices to avoid Discovering them.

An easy way to ensure that those IPs won't be Discovered is to add them to the "Discovery Range Item Excludes" related list on the on the corresponding IP range within your Discovery Schedule.

I realize that the tool will not Discover IPs that you do not provide it with, but I'm hoping for a future enhancement to make exclusions easier - perhaps a list you could populate containing "IPs to never be Discovered" that would be excluded from all Discovery Schedules. Here's to hoping!

Dan