VendorGate

Expected response

The expected response configuration tells VendorGate what a healthy endpoint looks like. You can combine multiple checks.

Status code

Require one or more acceptable status codes, for example [200] or [200, 201]. The field is status_codes and accepts a list.

Response time

Set max_response_time_ms to the maximum allowed response time in milliseconds. If the response takes longer, the monitor is marked degraded or down depending on your thresholds.

Body content

  • Contains: check that the body contains a specific string (body_contains).
  • Regex: check that the body matches a regular expression (body_regex).
  • JSON path exists: check that a JSON path is present (json_path_exists).
  • JSON path equals: check that a JSON path equals an expected value (json_path_equals: { path: "...", expected: ... }).

Headers

  • Header exists: check that a specific header is present (header_exists).
  • Header equals: check that a header has an expected value (header_equals: { name: "...", value: "..." }).

TLS certificate

Set tls_cert_expiry_warning_days to check that the TLS certificate will not expire within the given number of days.

Consecutive failures

Choose how many consecutive failed checks are needed before the monitor is considered down. The default is two, which helps avoid false alarms from brief blips.

Example

A healthy endpoint might require:

  • Status code 200.
  • Response time under 2000 ms.
  • Body JSON path status equals ok.
  • TLS certificate valid for at least 14 days.