Exclude/stop the Insert/Creation or update of CI's based on Name during Disocvery

[mike2agk]

All,

Do we have a way of excluding a CI by name once discovered by Discovery and before its created or updated in the CMDB . This is as a result of dealing with alias. For example if I don’t want a particular CI[based on the name] created or updated in the CMDB how do I do that? 

Always appreciate your feedback

Thanks

Mike

[TJ6]

Hi Mike,

That sounds different from what I thought this question was originally asking.

If you want a set of CMDB CIs to not be updated AT ALL then there are various ways to do that.

Depending on what set of CIs and what classes they are.

The easiest way, in my opinion, is to create a custom checkbox on the cmdb_ci table. Maybe call it "No Discovery Updates" and have it checked for any CI that you do not want discovery to ever update or touch. Then create a business rule on cmdb_ci that says not to update that record if the updating user is the user you have configured to run your MID server. 

Nevertheless, this is a solution I can only offer without knowing more of exactly what you are trying to do, with no specifics.

thanks,

-TJ

[mike2agk]

Always appreciate your input TJ, let me be more detailed.

Lets say I have an IP "z" that gets discovered as "P" or "Q"[hence alias: round robin].l I want a situation where by i can let discovery know that if Q is identified it shld not update of create the CI in the CMDB. So maybe i should  have a table that contains all these CI that i dont want to be created or updated in the CMDB so that when disocvery runs its verifies against this table and if the CI is present it does not create or update the CMDB

Thanks

Mike

[TJ6]

Hi Mike,

If a device can have the name as 'P' or 'Q', if you discover the IP associated with it the first time and it comes back P, the next time it comes back Q then you do not want it to update the CI to name as Q that second time? You just want it to do nothing. 

In this case then yeah, a business rule that says if the name changes and the updating user is the MID server user (the one you configured to work with your MID server), to no update the CI. Note that this rule will prevent the whole CI from being updated, not just the name field. 

thanks,

-TJ

[mike2agk]

Yes this shld solve that Issue and also prevent any CI in general present in the table that you dont want to be created or updated based on its name. Do you have like an article or "how to" that will guide me in configuring this?

Thanks

Mike