Define default CI relationships found by Discovery

[mitzaka]

Hi, community,

I have a question about CI relationships, I know a lot has been written in SNC, I read a lot, but I still can't find exactly what I am looking for, so excuse me if repeating the topic.

Here goes: I have a CMDB which is populated of mixed mode - I use SN Discovery, which finds s number of CI types, then I import some other CIs manually via update sets. For the stuff which Discovery finds automatically, there are certain types of pre-configured relationship types (like for example: SQL Server : Runs On : Windows Server OS). What I want to achieve is to change the default relationship type between automatically discovered CI types. In my example say SQL Server : Depends On: Windows Server (just an example). In few words   - chnage the default relationship between two CIs which are found automatically.

So how do I tell Discovery to use my relationship map instead of the default?
I found this: Diving Into CI Relationships..., but is this the right place to go?

Thanks in advance for the answers.

[doug_schulze]

If you look at the process classifiers (discovery definition > process) you will see each oob application that we map and the default relationship we assign.   While it is not common to change a runs on :: runs relationship I dont see why you couldn't choose one of your own.  

One key point though.   Do not change the OOB relationships if you want to use something of your own naming convention say works on :: works then add that parent child descriptor to the list (configuration > CI relationship types) do not change any of the default values.. somewhere down the line you might cause some serious confusion..

[mitzaka]

Doug, thanks for the reply, what I intend is not to create relationships of my own, but more likely to change one OOB relationship type with another OOB relationship type. Here by OOB, I mean standard for ServiceNow, not custom.

My   final goal is to have the CIs discovered as of now, but just populate a different default relationship type between some of them. To explain why - this is mainly because I am using a large number of VMware CI types in my CMDB. For some of them(like vCenter related) the Discovery automatically sets certain relationships, but I think some of them are not the best use at least in the BSM I am trying to create.

Thank you for the advise, all such feedback is much appreciated!

[doug_schulze · Accepted solution]

If thats the case then also know that there are relationships built into the sensors as well, especially in the vCenter world.   ALWAYS REMEMBER, Be careful changing OOB probes and sensors, once you do..you own them and they will not be updated on subsequent releases!   Best practice is to create your own!

And of course test all your changes in /dev to ensure you do not impact other parts of the business!

[mitzaka]

Hi, Doug, yes I think the sensors are the link I was missing in understanding that.

You are absolutely right, I don't want to mess with the OOTB stuff in general, perhaps I will just think of defining some custom probes and sensors for my case.

Thanks for the info!