The statuses of most services in the service
hierarchy are calculated from the messages associated with the
service and from the subservices on which the service is dependent.
Status propagation refers to how a service represents its
status to its superordinate services.
Rule Type
You can choose to create a Simple Rule, where the
propagation is always the same, regardless of the status of the
service, or a Severity Based Rule, where the propagation
changes, depending on the status of the service.
Simple/Default Rule
You can create a Simple/Default Rule regardless of which
rule type you choose. If the propagation rule type is Simple, then
this rule will be used in all cases with two exceptions (noted
below). Use a severity-based rule if you want to propagate normal
as some other status. If the propagation rule type is Severity
Based, then this rule will be used as the default for any severity
levels for which you have not specified another rule. You can
choose one of four Simple/Default Rules:
Unchanged: Propagate the status with no change. For
example, a status of Warning equals Warning. (This is a reasonable
default value to use. If you are new to status calculation,
consider starting with this value and editing it later, if
necessary.)
Ignore: The status of the subservice is not considered
when calculating the status of the dependent service. This status
propagation allows you to include a service in the service
hierarchy without allowing it to influence the status
calculation.
Propagate Fixed As: The status of the subservice is
always considered to have a certain status, regardless of the
actual status. For example, with status propagation set to
fixed:warning, a subservice with a status of minor is
interpreted as warning. If the status of the subservice changes to
critical, the status will still be interpreted as warning.
Exception: the status normal is always propagated as
normal and will not be change by this setting.
Propagate Relative: To propagate the status at a fixed
level higher or lower than what the status really is. For example,
if you select INCREASE BY 2, then when the subservice has a status
of warning, a status of major is propagated. Exception: the
status normal is always propagated as normal and will not be
change by this setting.
Severity Based Rule Propagation
Severity Based Rule Propagation allows you to override the
Simple/Default rule for specific severities. For example, if your
Simple rule is INCREASE BY 2, and the Severity Based Rule
Propagation for all severities is set to use default, all
severities (except normal) will be increased by two. If, however,
you change the Severity Based Rule Propagation for Warning to
Critical, then a severity of warning will be propagated as
critical, normal will be propagated as normal and all others will
be increased by two. Use default overrides the Simple/Default rule
and allows the unchanged severity to be propagated.
To configure propagation rules:
Open the Service Editor
Select
your top-level services folder in the console tree.
Click the Configuration toolbar to open the Service
Editor.
Select the service that you want to configure.
Select Properties.
Select Superordinates or Subordinates.
Double-click the service where you want to change the
propagation rule.
the Configuration toolbar to open the Service
Editor.
