Set thresholds for specific requests

Set request thresholds in the UI

In Step 3/3: Load Configuration, open the Thresholds tab. Each threshold is one row where you choose a metric, a condition, and a value, then set its scope.

Use the for dropdown to choose which requests the threshold applies to:

• All Requests: the aggregated metric across the entire test run. This is the default.
• Single Request: a specific request only.
• Request Pattern: the aggregated metric across requests that match a wildcard pattern.
• Request Group: the aggregated metric across a list of requests.

For any scope other than All Requests, enter the request URL, k6 tag, or JMeter sampler label that applies to your test type. The UI guides you with framework-specific helper text and validates your entry.

For multiple scenarios tests, use the on dropdown to choose the scenario scope:

• Across all scenarios: the aggregate of every scenario. This is the default.
• Scenario name: that scenario only.

Select Add Threshold to add more thresholds, then save the test.

Named request groups, set with the group: prefix, are available only in the CLI. In the UI, use a request group to apply one threshold across several requests.

Set request thresholds in browserstack-load.yml

Add an optional request field to any entry in the thresholds block. Without a request field, the threshold applies to overall metrics, exactly as it does by default. With a request field, the threshold applies only to the requests you target.

Target a single request

Set request to an exact request URL, k6 tag, or JMeter sampler label.

Target a pattern

Use * to match a single path segment and ** to match multiple segments. The threshold applies to every request that matches the pattern.

Target an inline group

Pass a list of requests to apply one threshold across all of them.

Reuse a named group

Define reusable groups under the top-level request-groups field, then reference a group from any threshold with the group: prefix. This keeps a single list that many thresholds can share.

Scope a threshold to a scenario

For multiple scenarios tests, add a scenario field to evaluate the threshold within a single scenario. The value must match a scenario name in your config. Omit scenario to evaluate the threshold across all scenarios.

request and scenario are independent scopes. Combine them to evaluate a metric on a specific request within a specific scenario.

The following rules apply to request thresholds:

• For JMeter, replace URLs with sampler labels, such as request: "Process Payment".
• For k6, you can target a request URL or a k6 tag.
• Keep group: references on their own. You can’t mix a group: reference with URLs, tags, or labels in the same list.
• Every group under request-groups needs a unique name and at least one entry.
• The scenario field works only for browser tests. Adding it to an API test threshold returns an error.