syslog_drain_binder job from cf/247
Github source:
af4efe9f
or
master branch
Properties¶
cc
¶
bulk_api_password
¶Password for the bulk api
srv_api_uri
¶API URI of cloud controller
loggregator
¶
etcd
¶
ca_cert
¶PEM-encoded CA certificate
- Default
""
machines
¶IPs pointing to the ETCD cluster
maxconcurrentrequests
¶Number of concurrent requests to ETCD
- Default
10
require_ssl
¶Enable ssl for all communication with etcd
- Default
false
metron_endpoint
¶
dropsonde_port
¶The port used to emit dropsonde messages to the Metron agent
- Default
3457
host
¶The host used to emit messages to the Metron agent
- Default
127.0.0.1
ssl
¶
skip_cert_verify
¶When connecting over https, ignore bad ssl certificates
- Default
false
syslog_drain_binder
¶
debug
¶Boolean value to turn on verbose logging for syslog_drain_binder
- Default
false
drain_url_ttl_seconds
¶Time to live for drain urls in seconds
- Default
60
etcd
¶
client_cert
¶PEM-encoded client certificate
- Default
""
client_key
¶PEM-encoded client key
- Default
""
locked_memory_limit
¶Size (KB) of shell’s locked memory limit. Set to ‘kernel’ to use the kernel’s default. Non-numeric values other than ‘kernel’, ‘soft’, ‘hard’, and ‘unlimited’ will result in an error.
- Default
unlimited
polling_batch_size
¶Batch size for the poll from cloud controller
- Default
1000
update_interval_seconds
¶Interval on which to poll cloud controller in seconds
- Default
15
system_domain
¶
Domain reserved for CF operator, base URL where the login, uaa, and other non-user apps listen
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/syslog_drain_binder/
directory
(learn more).
bin/syslog_drain_binder_ctl
(fromsyslog_drain_binder_ctl.erb
)config/certs/etcd-ca.crt
(frometcd-ca.crt.erb
)config/certs/etcd-client.crt
(frometcd-client.crt.erb
)config/certs/etcd-client.key
(frometcd-client.key.erb
)config/syslog_drain_binder.json
(fromsyslog_drain_binder.json.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.