loggregator_trafficcontroller job from cf/209

Github source: 35f75e02 or master branch

Properties¶

cc¶

srv_api_uri¶

API URI of cloud controller

doppler¶

uaa_client_id¶

Doppler’s client id to connect to UAA

Default

doppler

etcd¶

machines¶

IPs pointing to the ETCD cluster

maxconcurrentrequests¶

Number of concurrent requests to ETCD

Default

10

loggregator¶

doppler_port¶

Port for outgoing doppler messages

Default

8081

outgoing_dropsonde_port¶

Port for outgoing dropsonde messages

Default

8081

loggregator_endpoint¶

shared_secret¶

Shared secret used to verify cryptographically signed loggregator messages

metron_endpoint¶

dropsonde_port¶

The port used to emit dropsonde messages to the Metron agent

Default

3457

nats¶

machines¶

IP addresses of Cloud Foundry NATS servers

password¶

Password for cc client to connect to NATS

port¶

IP port of Cloud Foundry NATS server

user¶

Username for cc client to connect to NATS

ssl¶

skip_cert_verify¶

when connecting over https, ignore bad ssl certificates

Default

false

system_domain¶

Domain reserved for CF operator, base URL where the login, uaa, and other non-user apps listen

traffic_controller¶

collector_registrar_interval_milliseconds¶

Interval for registering with collector

Default

60000

debug¶

boolean value to turn on verbose logging for loggregator system (dea agent & loggregator server)

Default

false

host¶

The host the loggregator_trafficcontroller should listen on

Default

0.0.0.0

incoming_port¶

Default

3456

outgoing_port¶

Default

8080

status¶

password¶

password used to log into varz endpoint

Default

""

port¶

port used to run the varz endpoint

Default

0

user¶

username used to log into varz endpoint

Default

""

zone¶

Zone of the loggregator_trafficcontroller

uaa¶

clients¶

doppler¶

secret¶

Doppler’s client secret to connect to UAA

no_ssl¶

Do not use SSL to connect to UAA (used in case uaa.url is not set)

Default

false

url¶

URL of UAA

Templates¶

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

• bin/loggregator_trafficcontroller_ctl (from loggregator_trafficcontroller_ctl.erb)
• config/loggregator_trafficcontroller.json (from loggregator_trafficcontroller.json.erb)

Packages¶

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

• common
• loggregator_trafficcontroller