How do problems affect the state of services? Which services are affected by a particular problem? Are there related problems?
Use SCM to create a tree that shows all services with corresponding trouble tickets. Figure 13-3 shows services with problem tickets:
Figure 13-3 Alarms View
The following scenario shows how a SCM definition is created to overlay services with trouble tickets from a Remedy ARS system.
Feed trouble ticket information directly to the
hierarchy. Tickets are matched to the services by using a simple hostname match. The resulting hierarchy shows services with trouble ticket information. Trouble tickets can then be managed by associated service.This scenario uses:
A Data Integrator adapter that taps into an internal IT‑maintained database
It organizes technology (server information) by the service that it supports.
A Remedy ARS adapter that provides trouble ticket information
To use SCM to create a configuration to manage problem tickets:
In the Explorer pane, add an element that is the parent of the new tree.
In this example, create a
element under the element:Right-click the element, then select
> to open the Service Configuration Editor.To define the Structures for the element by identifying an existing hierarchy that drives the shape of the new tree, create a Structure definition that adds the
element as a , as shown in the illustration below.In this case, the
hierarchy is a branch from a Data Integrator adapter that taps into an internal IT‑maintained database. It organizes technology (server information) by the service that it supports.To view all elements contained in the
hierarchy, leave and at 0.Use the default Matching Rule to apply a simple name match to select elements.
To define the Sources for the configuration by identifying an existing hierarchy that provides state and information to the new elements in the configuration, create a Source definition that uses the
element as the .is a hierarchy resulting from a Remedy ARS adapter integration. It provides trouble ticket information to the new configuration elements based on a simple name join.
Use the default join rule to link state information to structure elements using a simple name match.
This definition allows state and property information to be available for any new elements found when the configuration searches for dependencies.
To define
and policy rules to further define how the configuration is generated and elements are correlated:To specify that Structures define the elements in the new configuration and Source data provide state, retain all the generation defaults, but do not select any
policy options.To match all elements and sources, retain the default
selection in policies.Those objects that are matched are included in the new configuration tree.
Click Save to save configuration settings.
Click Generate to generate the new tree.
The new hierarchy is built under the
element in the hierarchy:Use the
tab to review problem tickets for the appropriate elements.After the configuration is run and results are verified, create a schedule for the generation of the service configuration on a routine basis.
Schedule this configuration to generate every five minutes as problem management is always an immediate requirement.