Service Level Objectives (SLO)

Although Service Level Objective (SLO) objects can be created in the Administration perspective, this is mainly a task for object designers. For this reason you can find the user-related documentation in the Using the Automation Engine guide.

The following topics describe what are SLO objects and how to set them up:

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

The following topics describe how to monitor and react to them in case of violations:

• Monitoring Services
• Filtering the List of Fulfillments

The following examples illustrate how you can define and use them:

• Example: SLM Unattempted Start
• Example: Skipping a Job Due to an SLM Violation

Service Level Objectives List

In the Administration perspective, the following columns are displayed by default:

• Service Level Objective

  Name of the Service Level Objective

• Title

  (Optional) Short description to recognize the SLO at a glance

• Enabled

  Weather SLO is enabled or not

• Last Modification

  Time and date of the last modification

• Version

  Objective version

  Displays how many times the objective has been modified.

Tip: You can share filtered lists with other users. You can also bookmark the filtered list to be able to access it quickly next time. For more information, see Bookmarking and Sharing Links.

See also:

• Showing and Hiding Columns
• Exporting Tables to CSV