Validators Config (v0.14.5)

# Response's AA (Authoritative Answer) flag should match this value: # authoritative: true => AA flag should be set, i.e. the responding # server is authoritative for the queried domain. # This is useful while probing authoritative DNS # servers, typically along with dns_probe's # recursion_desired set to false. # authoritative: false => AA flag should not be set, e.g. while verifying # that a response came from a resolver's cache or # that a server returns a referral. # If unset, AA flag is not checked at all.

# Comma-separated list of success status codes and code ranges. # Example: success_stauts_codes: 200-299,301,302

# Comma-separated list of failure status codes and code ranges. If HTTP # status code matches failure_status_codes, validator fails.

# Header based validations. # TODO(manugarg): Add support for specifying multiple success and failure # headers. # # Success Header: # If specified, HTTP response headers should match the success_header for # validation to succeed. Example: # success_header: { # name: "Strict-Transport-Security" # value_regex: "max-age=31536000" # }

# Failure Header: # If HTTP response headers match failure_header, validation fails.

# Last Modified Difference: # If specified, HTTP response's Last-Modified header is checked to be # within the specified time difference from the current time. Example: # max_last_modified_diff_sec: 3600 # This will check that the Last-Modified header is within the last hour.

# Header name to look for

# Header value to match. If omited - check for header existence

# Validate the data integrity of the response using a pattern that is # repeated throughout the length of the response, with last len(response) % # len(pattern) bytes being zero bytes. # # For example if response length is 100 bytes and pattern length is 8 bytes, # first 96 bytes of the response should be pattern repeated 12 times, and # last 4 bytes should be set to zero byte ('\0')

# If jq filter is specified, validator passes only if applying jq_filter to # the probe output, e.g. HTTP API response, results in 'true' boolean. # See the following test file for some examples: # https://github.com/cloudprober/cloudprober/blob/master/validators/json/json_test.go

# Response's AA (Authoritative Answer) flag should match this value: # authoritative: true => AA flag should be set, i.e. the responding # server is authoritative for the queried domain. # This is useful while probing authoritative DNS # servers, typically along with dns_probe's # recursion_desired set to false. # authoritative: false => AA flag should not be set, e.g. while verifying # that a response came from a resolver's cache or # that a server returns a referral. # If unset, AA flag is not checked at all.

# Comma-separated list of success status codes and code ranges. # Example: success_stauts_codes: 200-299,301,302

# Comma-separated list of failure status codes and code ranges. If HTTP # status code matches failure_status_codes, validator fails.

# Header based validations. # TODO(manugarg): Add support for specifying multiple success and failure # headers. # # Success Header: # If specified, HTTP response headers should match the success_header for # validation to succeed. Example: # success_header: { # name: "Strict-Transport-Security" # value_regex: "max-age=31536000" # }

# Failure Header: # If HTTP response headers match failure_header, validation fails.

# Last Modified Difference: # If specified, HTTP response's Last-Modified header is checked to be # within the specified time difference from the current time. Example: # max_last_modified_diff_sec: 3600 # This will check that the Last-Modified header is within the last hour.

# Header name to look for

# Header value to match. If omited - check for header existence

# Validate the data integrity of the response using a pattern that is # repeated throughout the length of the response, with last len(response) % # len(pattern) bytes being zero bytes. # # For example if response length is 100 bytes and pattern length is 8 bytes, # first 96 bytes of the response should be pattern repeated 12 times, and # last 4 bytes should be set to zero byte ('\0')

# If jq filter is specified, validator passes only if applying jq_filter to # the probe output, e.g. HTTP API response, results in 'true' boolean. # See the following test file for some examples: # https://github.com/cloudprober/cloudprober/blob/master/validators/json/json_test.go