Documentation Grafana Cloud Testing and synthetics Synthetic Monitoring Create checks Check types MultiHTTP check

MultiHTTP check

MultiHTTP checks can test multiple URLs in a single check while measuring uptime and response latency like other check types. You can also use the results of one request in a later one and make several assertions for each request.

Options

The list of common options to all check types:

Additionally, MultiHTTP checks have the following options:

These last options don’t produce any additional labels in the resulting check metrics.

Assertions

There are four types of assertions.

Text assertions

Text assertions match a string against different parts of a response:

• Body: Match a string against the entire response body.
• Headers: Each individual header is matched against the specified value. The header name is lower-cased, followed by a colon and a space (: ), followed by the header’s value (as is). The match succeeds if at least one of the headers matches.
• Status code: Match a string against the HTTP status code.

The match can be performed against the specified subject in one of several ways:

• Contains: The specified value must be present somewhere in the subject.
• Does not contain: The specified value must not be present anywhere in the subject.
• Equals: The subject must be exactly equal to the specified value.
• Starts with: The subject must start with the specified value.
• Ends with: The subject must end with the specified value.

JSON path value assertions

This type of assertion expects the response body to be a JSON document, and it accepts a JSONPath expression to be matched against the specified value. The possible matches are:

• Contains: The specified value must be present somewhere in the result of evaluating the JSONPath expression.
• Does not contain: The specified value must not be present anywhere in the result of evaluating the JSONPath expression.
• Equals: The result of evaluating the JSONPath expression must be exactly equal to the specified value.
• Starts with: The result of evaluating the JSONPath expression must start with the specified value.
• Ends with: The result of evaluating the JSONPath expression must end with the specified value.

JSON path assertions

This type of assertion expects the response body to be a JSON document, and it accepts a JSONPath expression that must evaluate to a non-empty result for the assertion to succeed.

Regex assertions

Regular expression assertions evaluate the provided regular expresion against one of various subjects:

• Body: The entire response body is used.
• Headers: Each individual header is evaluated against the specified regular expression. The header name is lower-cased, followed by a colon and a space (: ), followed by the header’s value (as is). The match succeeds if at least one of the headers matches.
• Status code: The status code is used.

Variables

Variables can capture values from the responses to individual HTTP requests. Each variable must be named, and the name must be unique across all requests. The name can be used in subsequent requests by using the ${name} variable. It’s possible to use this anywhere where a string is expected, for example, as the value of a header or the value of an assertion.

Variable values can be obtained from the following.

• A JSONPath: The value of the variable is the result of evaluating the JSONPath expression.
• A regular expression: The value of the variable is the string matching the regular expression.
• A CSS selector: The value of the variable is the value of evaluating the CSS selector against the response body. Optionally, an attribute name can be specified, in which case the value of the variable is the value of the specified attribute.

Metrics

Checks store their results as Prometheus metrics, including the list of common metrics:

Additionally, MultiHTTP checks produce the following metrics: