The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
Service Desk Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Building relations between CI`s.

SOLVED
Go to solution
Highlighted
Vladislavs
Super Collector

Building relations between CI`s.

Hi!

All the Configuration Items has been imported to Service Desk 4.5.(SP21) mainly without relations. One of next our goals is to automate registration of incidents (If child CI is down, parent CI is automatically down).
Now we are thinking how is better to build relations between CIs. Parent-Child Relationship or Related CIs?

Thanx!
8 REPLIES
Vasily Kamenev
Honored Contributor
Solution

Re: Building relations between CI`s.

Hi
If you like have informations - what is be if this host, service and etc. is down, use the parent-child relation, because internal SD searching using only this type relation, direction from child to up.

Vasily
Vladislavs
Super Collector

Re: Building relations between CI`s.

Thank u Vasily!
Vladislavs
Super Collector

Re: Building relations between CI`s.

Vasily,

You showed Service Parent-Child relation. But what about Configuration Items relations?
Vasily Kamenev
Honored Contributor

Re: Building relations between CI`s.

Vadim,
if CI2 include in CI1 as child, and CI2 is down, then in list shows Services by CI1, but if you did by another way (CI2 is parent on CI1) and services related to CI1, system doesn't show you any Services when CI2 is down. The propogation not end one step, this working for Child->Parent->Parent ... .

Vasily
Vladislavs
Super Collector

Re: Building relations between CI`s.

Thank you! I've checked, it works.

If Server1 is down and it is related as child for CI2, CI3, CI4.......accordingly Service2, Service3, Service4 is down.
As I understand, several incidents should be registered so we could receive correct Availability Report?
Vasily Kamenev
Honored Contributor

Re: Building relations between CI`s.

Must be, that depend from your SLA and Services structure. But this picture need so define most impotent Services from list of all involved in incident.

Vasily
Vladislavs
Super Collector

Re: Building relations between CI`s.

What is the best way to create DB rule which could register many Incidents with Parent Configuration Items? As I understand the status (or other parameter) of Parent CI must be changed after first/main incident registration?
Vasily Kamenev
Honored Contributor

Re: Building relations between CI`s.

Optionlly, this is not need, because this is a task of monitoring system. The monitoring system must prevent event storm. Example if your host go down, but on host you are monitored not only network card, but a some more other services IIS, ftp , etc. so event come from all monitoring services too?, but this is one problem, not need registered more others. So in this case monitoring system must prevent event storm and sent only one notification. Any way , if you system can't to do that use additional field in CI where you store the "monitoring name" and monitoring system must operating only this name if down IIS use this name , down ftp use the same name , CI every time will be a one but text you can add other, by rule( using function CONCATENATE). this is easy way prevent event storm, by my vision.

Vasily
//Add this to "OnDomLoad" event