How to Define Service Level Agreements

This task describes how to define service level agreements (SLAs).

You can define service level agreements (SLAs) which measure scenario goals over time intervals, or over a whole scenario run. For details, see Service Level Agreements Overview.

See also Defining Service Level Agreementsin Analysis.

Tip: For a use-case scenario related to this task, see How to Define Service Level Agreements - Use-Case Scenario.

  1. Prerequisites

    If you are defining an SLA for Average Transaction Response Time, your scenario must include a script that contains at least one transaction.

  2. Run through the SLA wizard

    In the Service Level Agreement pane, click New to open the Service Level Agreement wizard. For user interface details, see Service Level Agreement Wizard.

    1. Select a measurement for the SLA.

    2. If you are defining an SLA for Average Transaction Response Time, select the transactions to include in your goal.

    3. (Optional) When evaluating SLA statuses over a timeline, select load criteria to take into account and define appropriate load value ranges for the load criteria. For an example, see How to Define Service Level Agreements - Use-Case Scenario.

    4. Set thresholds for the measurements.

      • If the Average Transaction Response Time or Errors per Second exceed the defined thresholds, Analysis will produce a Failed SLA status.

      • If Total Hits per run, Average Hits (hits/second) per run, Total Throughput (bytes) per run, or Average Throughput (bytes/second) per run are lower than the defined threshold, Analysis will produce a Failed SLA status.

    Back to top
  3. Define a tracking period - optional

    For measurements whose SLA statuses are determined over time intervals, you need to define the frequency of the time intervals, that is, the tracking period. For details, see Tracking Period.

    For user interface details, see Advanced Options Dialog Box.

  4. Results

    When analyzing your scenario run, HPE LoadRunner Analysis compares the data collected from the scenario run against the SLA settings, and determines SLA statuses which are included in the default Summary Report.

Back to top