Possible Outcomes
Depending on how you define the fulfillment criteria in an SLO object, the results of monitoring the services are as described in this topic.
This is what happens depending on the object definition and on the results of it:
| Case | Behavior |
|---|---|
| No fulfillment criteria are defined in the Service Level Objective - Fulfillment Criteria page |
No criteria can be violated as no criteria have been selected to be checked. Therefore, the SLM monitoring will always generate a fulfillment. |
| The SLO considers one or more services (executable objects) |
At least one record per service is generated and displayed on the Services - Fulfillment table. When all criteria are met, either exactly one Fulfilled record or 1-n violated recored (one per violated criterion) are generated. For every criterion that is not met, a Violated record is generated. This way, detailed information on all the violations is provided to allow operators to analyze and fix the problems. |
| Latest start time is checked but not the latest end time or any other criteria |
In this case only the "latest start time" criterion rules. A fulfillment is generated immediately right at service start, the monitoring does not wait for the service to end. |
| Latest start/end time criteria | For time-based checks, the logical start time of a service is used. |
| Cascaded/nested objects |
In case of monitoring a service that contains sub services (such as Workflows and Schedules, for example), the sub services are not monitored as part of the parent/top service in general. If you want to monitor sub-services too you have to either include them in the SLO's Service Selection filter or cover them in other SLO objects. Example: A service called JOBP.SLM.PARENT contains the two subs-services JOBP.SLM.CHILD.1 and JOBP.SLM.CHILD.2. If you set the SLO object Service Selection filter to Object Name contains/starts with "JOBP.SLM" this SLO object covers all three services. |
See also: