Sparks

CI relationship editor

Searching for 981309

The CMDB, in contrast to a static asset list, helps you track not only the configuration items CIs within your system but also the relationships between those items. For example, a web application might read data from a particular instance of Oracle, which in turn might depend on a piece of the underlying hardware. The relationships between CIs can be automatically discovered. If you use Discovery, many relationships can be automatically loaded into the system through the discovery process. If you import your data from another system, you may need to build relationships. You can add to automatically discovered relationships, create new relationships, or edit relationships for a CI by launching the CI relationship editor from the CI form. If this job is not active, please activate and run the job periodically. Description The CMDB, in contrast to a static asset list, helps you track not only the configuration items CIs within your system but also the relationships between those items.

This article aims to explain how en route for delete or correct these records, accordingly that you can then discount them as a potential cause of your issue. I will also try en route for identify some of the reasons they may come about in the at the outset place. There is always a attempt when running this kind of character that more gets deleted than plans. This is fine and to be expected.

This article will explain how the existing CMDB relationships that are not accommodating with suggested relationships are flagged. The report will only flag a affiliation if a suggested relationship of the same type does not exist devoid of taking into consideration the direction. This means that a relationship will be valid if there is a affiliation rule defined for the classes along with the given relation type regardless of which class is the parent after that which is the child. This affiliation is valid because there is a suggested relationship rule created between Attendant and Business Service for the Relationship: Depends on::Used By. Even though the rule is defined in the conflicting way, the direction of the affiliation is not taken into consideration, barely the rel type. This relationship is not valid as there is denial suggested relationship rules for Uses::Used as a result of between server and service, regardless of the direction. Therefore, the dashboard activity will flag it and it bidding be included in the report.

Designed for each dependent CI, there should be a relation that contains the blood relation, child, and type. An example be able to be seen as follows:. Review the payload passed to the identification apparatus and confirm if the relation is present or not. In the next example we look at a consignment passed to the identification engine as a result of a pattern probe. If the consignment does not have a relationship amid the dependent CI and the central CI, the relationship will need en route for be added to the payload. But the payload was built by a pattern, the pattern will need en route for be updated to add such affiliation. Click on Dependent Relationships to analysis the possible containment rules for the CI.

Your email address will not be published. Required fields are marked *