loggr-system-metric-scraper job from system-metrics-scraper/4.0.9
              Github source:
              f7af1da or
              master branch
            
Properties¶
enabled¶
  
    
      Enables the system metrics agent scraper
- Default
- true 
leadership_election¶
  
  
    
ca_cert¶TLS CA cert to verify requests to leadership election endpoint.
cert¶TLS certificate for leadership election client signed by the leadership election CA
key¶TLS private key for leadership election client signed by the leadership election CA
metrics¶
  
  
    
ca_cert¶TLS CA cert to verify requests to metrics endpoint.
cert¶TLS certificate for metrics server signed by the metrics CA
key¶TLS private key for metrics server signed by the metrics CA
port¶Port the agent uses to serve metrics and debug information
- Default
14920
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
scrape_interval¶
  
    
      The interval to scrape the metrics URL (golang duration)
- Default
- 1m 
scrape_port¶
  
    
      The port where the scraping endpoints are hosted
- Default
- 53035 
system_metrics¶
  
  
    
tls¶
ca_cert¶TLS loggregator root CA certificate. It is required for key/cert verification.
cert¶TLS certificate for system metrics agent signed by the loggregator CA
common_name¶Common name for system metrics agent CA
- Default
system-metrics
key¶TLS private key for system metrics agent signed by the loggregator CA
Templates¶
            Templates are rendered and placed onto corresponding
            instances during the deployment process. This job's templates
            will be placed into /var/vcap/jobs/loggr-system-metric-scraper/ directory
            (learn more).
          
- config/bpm.yml(from- bpm.yml.erb)
- config/certs/leadership_election.crt(from- leadership_election.crt.erb)
- config/certs/leadership_election.key(from- leadership_election.key.erb)
- config/certs/leadership_election_ca.crt(from- leadership_election_ca.crt.erb)
- config/certs/loggregator_agent.crt(from- loggregator_agent.crt.erb)
- config/certs/loggregator_agent.key(from- loggregator_agent.key.erb)
- config/certs/loggregator_ca.crt(from- loggregator_ca.crt.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/certs/system_metrics.crt(from- system_metrics.crt.erb)
- config/certs/system_metrics.key(from- system_metrics.key.erb)
- config/certs/system_metrics_ca.crt(from- system_metrics_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.