Skip to content

log-cache-nozzle job from log-cache/2.11.7

Github source: 20face2 or master branch

Properties

enabled

Enable Log Cache RLP Ingress

Default
true

logging

format

timestamp

Format for timestamp in component logs. Valid values are ‘deprecated’ and ‘rfc3339’.

Default
deprecated

logs_provider

tls

ca_cert

CA root required for key/cert verification to connect to the logs-provider

cert

TLS certificate for the logs-provider connection

key

TLS key for the logs-provider connection

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

The port for the nozzle to bind a health endpoint

Default
6061

server_name

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

Default
log_cache_nozzle_metrics

rlp

override_address

Override of bosh links for reverse-log-proxy url

selectors

A list of envelope types to read from RLP

Default
  - log
  - gauge
  - counter
  - timer
  - event

shard_id

The sharding group name to use for egress from RLP

Default
log-cache

Templates

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

  • config/bpm.yml (from bpm.yml.erb)
  • config/certs/log_cache.crt (from log_cache.crt.erb)
  • config/certs/log_cache.key (from log_cache.key.erb)
  • config/certs/log_cache_ca.crt (from log_cache_ca.crt.erb)
  • config/certs/logs_provider.crt (from logs_provider.crt.erb)
  • config/certs/logs_provider.key (from logs_provider.key.erb)
  • config/certs/logs_provider_ca.crt (from logs_provider_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/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.