Some content in OMi is part of a hierarchy that may relate to and depend upon other content. When you select content for inclusion in a content pack, its dependent content must also be included, either as part of the same content pack, or referred to from another content pack that will also be uploaded. For example, if you include a KPI assignment, any indicators, KPIs, menus, or rules necessary for this KPI assignment must also be included.
Automatically Including Dependent Content
If you select content that has dependent content, and the dependent content is not part of another content pack, the dependent content is automatically included in the content pack definition along with the content that requires it.
For example, the correlation rule BB DB Connection Status requires two indicators: the BB Component indicator BB DB Connection Status and the Database indicator Database Server Status. If you include the correlation rule BB DB Connection Status in a content pack definition and the indicators BB DB Connection Status and Database Server Status are not included in other content packs, they are automatically included in this content pack definition.
Setting Dependency
If dependent content is included in more than one other content pack, you can select which content pack to reference. This is called setting dependency.
For example, if Content Packs A and B both include the indicator CPU Load and you select the correlation rule Database Affects WebApp (which depends on CPU Load) for inclusion in Content Pack C, you can set the dependency in Content Pack C to reference CPU Load in either Content Pack A or B.
Referencing Dependent Content Included in Another Content Pack
If dependent content is already included in another content pack, by default the new content pack references its inclusion in the other content pack rather than including it in both. You can, however, use the Dependencies page to also add it to the included content in the new content pack.
For example, if content pack definition A includes the indicator Ping Availability and now you select the correlation rule Database Affects WebApp (which depends on Ping Availability) for inclusion in Content Pack B, Content Pack B references the inclusion of Ping Availability in Content Pack A.
On the Content Pack B Dependencies page, Ping Availability is listed in bold, under Content Pack A. The dependency is set automatically. To include Ping Availability in Content Pack B (and thus, in both content packs), select it and click Add to Included Content.
Note It is not recommended to have content in multiple content packs. It is preferable to set dependencies between content packs.
Deleting Referenced Content Pack
If you delete a referenced content pack containing dependent content, the dependent content is automatically added to the content pack definition that depends on it.
For example, if Content Pack B includes the correlation rule Database Affects WebApp and references the dependent indicator Extend TS in Content Pack A, and you delete Content Pack A, Extend TS is automatically included in Content Pack B.
Note You are warned via a pop-up message if you delete a referenced content pack containing dependent content.
Deleting Referenced Content Pack on Which Dependency Was Set
If you delete a referenced content pack on which dependency was set, the dependent content is automatically added to the content pack definition that depends on it. You can set dependency to another content pack manually, but it is not set automatically.
For example, if Content Packs A and B both include the indicator Extend TS, and Content Pack C includes the correlation rule Database Affects WebApp (which depends on Extend TS) and has dependency set to reference Extend TS in Content Pack A, and then you delete Content Pack A, Extend TS is automatically included in Content Pack C. You can then set dependency to Extend TS in Content Pack B, but it is not set automatically.