Skip to content

scrape-config-generator job from metrics-discovery/3.2.25

Github source: 64c833bb or master branch

Properties

config_ttl

This determines how long a scrape config lives before being expired

Default
45s

expiration_interval

This interval determines how often scrape endpoints are expired

Default
15s

metrics

ca_cert

TLS CA cert to verify requests to metrics endpoint.

cert

TLS certificate for metrics server signed by the metrics CA

debug

Enables go_ and process_ metrics along with a pprof endpoint

Default
false

key

TLS private key for metrics server signed by the metrics CA

port

Port to host metrics endpoint

Default
15822

pprof_port

If debug metrics is enabled, pprof will start at this port, ideally set to something other then 0

Default
0

server_name

The server name used in the scrape configuration for the metrics endpoint

nats_client

cert

TLS certificate to communicate with the NATs server signed by the NATs CA

key

TLS private key to communicate with the NATs server signed by the NATs CA

nats_instance_group

When deployed to this instance group, connect to the same instance via its IP address rather than via DNS lookup

Default
""

scrape_config_file_path

The path to the generated scrape config file

Default
/var/vcap/data/scrape-config-generator/scrape_targets.json

Templates

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

  • config/bpm.yml (from bpm.yml.erb)
  • config/certs/metrics.crt (from metrics.crt.erb)
  • config/certs/metrics.key (from metrics.key.erb)
  • config/certs/metrics_ca.crt (from metrics_ca.crt.erb)
  • config/certs/nats.crt (from nats_client.crt.erb)
  • config/certs/nats.key (from nats_client.key.erb)
  • config/certs/nats_ca.crt (from nats_ca.crt.erb)
  • config/prom_scraper_config.yml (from prom_scraper_config.yml.erb)

Packages

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