Skip to content

metric-store-blackbox job from metric-store/1.5.5

Github source: a95558b4 or master branch

Properties

cf_blackbox

client_id

UAA client ID for egress testing - requires logs.admin scope

client_secret

UAA client secret

enabled

Test HTTP egress which uses CF-based UAA authentication

Default
false

metric_store_address

Base URL for Metric Store (should not usually be configured)

skip_tls_verify

Skip certificate validation when testing HTTP egress

Default
false

deployment

The deployment name for the Blackbox, used to tag metrics

emission_interval

The interval between emitted test metrics

Default
1s

metric_store_metrics

tls

ca_cert

The Certificate Authority for metric-store metrics mutual TLS.

cert

The cert for metric-store metrics mutual TLS.

key

The private key for metric-store metrics mutual TLS.

metrics_port

The port for the Blackbox to bind a prometheus metrics endpoint

Default
6066

sample_interval

The interval between samples

Default
1m

source_id

Source ID for metadata of both test and result metrics

Default
metric-store

window_interval

The trailing interval over which to measure metric retrieval

Default
10m

window_lag

How far in the past the measurement should be taken

Default
20m

Templates

Templates are rendered and placed onto corresponding instances during the deployment process. This job's templates will be placed into /var/vcap/jobs/metric-store-blackbox/ directory (learn more).

  • config/bpm.yml (from bpm.yml.erb)
  • config/certs/metric_store.crt (from metric_store.crt.erb)
  • config/certs/metric_store.key (from metric_store.key.erb)
  • config/certs/metric_store_ca.crt (from metric_store_ca.crt.erb)
  • config/certs/metric_store_metrics.crt (from metric_store_metrics.crt.erb)
  • config/certs/metric_store_metrics.key (from metric_store_metrics.key.erb)
  • config/certs/metric_store_metrics_ca.crt (from metric_store_metrics_ca.crt.erb)
  • config/metric_port.yml (from metric_port.yml.erb)

Packages

Packages are compiled and placed onto corresponding instances during the deployment process. Packages will be placed into /var/vcap/packages/ directory.