Service Level Objective Object (SLO)

SLO objects depict the following four parties involved in a Service Level Agreement: The subject of the agreement, that is, the services (executable objects) provided; The beneficiaries of those services, that is the entities (departments, business units, etc.) that consume the services; The criteria they should fulfill and, finally, the actions that will be taken in case they do or do not.

Object Definition

Object class: Passive object

Object type/Short form: SLO

SLO objects can be defined either in the Process Assembly or in the Administration Perspective.

This page is not available in system client 0000.

Background/Purpose

In an SLO object you determine the following:

• (optionally) the beneficiaries of the service, that is, the departments, business units, etc. that require the service as stipulated in the agreement. They are defined via custom attributes and can be assigned to the objects (services) as Custom Attributes.
• the service itself, that is, the objects or groups of objects whose execution results are the subjects of the agreement
• the criteria that must be fulfilled
• (optionally) which actions will be taken in case the requirements are fulfilled/not fulfilled.

As soon as you activate the SLO object, the services defined in it are monitored and, if the requirements are not met, a violation is generated. See Monitoring Services.

Defining SLO Objects

The steps for defining SLO objects are the same as for any other Automic object. This section describes the settings that are specific to only SLO objects.

An SLO object definition is made up of the following pages:

• Standard pages that are always available, no matter what type of object you are defining:
• General Page
• Version Management Page
• Documentation Page

• SLO-specific pages:

  • Service Level Objective Page
    • Service Level Objective - Service Selection Page
    • Service Level Objective - Fulfillment Criteria

See also:

• Monitoring Services
• Possible Outcomes