Skip to content

metric-store-nozzle job from metric-store/1.4.2

Github source: a2b4d4b or master branch

Properties

health_port

The port for the Nozzle to bind a health endpoint

Default
6061

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

metric_store_client

tls

ca_cert

The Certificate Authority for metric-store mutual TLS.

cert

The cert for metric-store TCP client mutual TLS

key

The private key for metric-store TCP client mutual TLS

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.

shard_id

The sharding group name to use for egress from RLP

Default
metric-store

timer_rollup_buffer_size

The number of envelopes that will be allowed to be buffered while timer metric aggregations are running

Default
16384

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-nozzle/ directory (learn more).

  • config/bpm.yml (from bpm.yml.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/metric_store_client.crt (from metric_store_client.crt.erb)
  • config/certs/metric_store_client.key (from metric_store_client.key.erb)
  • config/certs/metric_store_client_ca.crt (from metric_store_client_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/indicators.yml (from indicators.yml.erb)

Packages

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