loggregator_trafficcontroller job from cf/235
Github source:
edc3e3c9 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
loggregator¶
doppler_port¶Port for outgoing doppler messages
- Default
etcd¶
machines¶IPs pointing to the ETCD cluster
maxconcurrentrequests¶Number of concurrent requests to ETCD
- Default
outgoing_dropsonde_port¶Port for outgoing dropsonde messages
- Default
login¶
protocol¶Protocol to use to connect to UAA (used in case uaa.url is not set)
- Default
metron_endpoint¶
dropsonde_port¶The port used to emit dropsonde messages to the Metron agent
- Default
ssl¶
skip_cert_verify¶when connecting over https, ignore bad ssl certificates
- Default
system_domain¶
Domain reserved for CF operator, base URL where the login, uaa, and other non-user apps listen
traffic_controller¶
debug¶boolean value to turn on verbose logging for loggregator system (dea agent & loggregator server)
- Default
disable_access_control¶Traffic controller bypasses authentication with the UAA and CC
- Default
outgoing_port¶Port on which the traffic controller listens to for requests
- Default
security_event_logging¶
enabled¶Enable logging of all requests made to the Traffic Controller in CEF format
- Default
zone¶Zone of the loggregator_trafficcontroller
uaa¶
clients¶
doppler¶
secret¶Doppler’s client secret to connect to UAA
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(fromloggregator_trafficcontroller_ctl.erb)config/loggregator_trafficcontroller.json(fromloggregator_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.