> OctoPerf load testing - SLA Profile Action documentation page. SLA Profile Actions apply an SLA profile on their parent Action / Container.

Source: https://api.octoperf.com/doc/design/edit-virtual-user/action-types/post-processors/sla-action/

# SLA Profile Action

![Service Level Agreement](https://api.octoperf.com/doc/design/edit-virtual-user/action-types/post-processors/img/sla-profile-action.png "Service Level Agreement")

The SLA Profile Action applies an SLA profile on its parent Action / Container.
SLAs are applied to every parent sample result.
Use the [SLA monitor](https://api.octoperf.com/doc/monitoring/create-connection/sla/) to check aggregated values for the whole test.

| Parameter name | Description                                                                         | Required |
|----------------|-------------------------------------------------------------------------------------|----------|
| SLA Profile    | Selection of the [SLA Profile](https://api.octoperf.com/doc/design/edit-virtual-user/configuration/sla-profiles/) to apply. | Yes      |

!!! info
    The [SLA Profiles](https://api.octoperf.com/doc/design/edit-virtual-user/configuration/sla-profiles/) panel is automatically opened if you drop an SLA Action when there is no profile created for the current project.

The SLA Action is available in every Virtual User, K6 and Playwright included. A threshold on a [custom metric](https://api.octoperf.com/doc/design/edit-virtual-user/configuration/sla-profiles/#custom-metrics), the Core Web Vitals of a Playwright test for instance, is only evaluated when the SLA Action sits at the root of the Virtual User: it judges the whole Virtual User.