haproxy job from logsearch/201.0.11
The HAProxy.
Github source:
84c42949 or
master branch
Properties¶
haproxy¶
client_timeout¶Timeout waiting for data from a client (in seconds)
- Default
30
cluster_monitor¶
backend_port¶The port number the cluster monitor backends are listening on
- Default
5601
backend_servers¶Array of the cluster monitor backend IPs
- Default
[]
inbound_port¶The public port of the cluster monitor UI
- Default
8080
connect_timeout¶Timeout waiting for connections to establish to a server (in seconds)
- Default
5
ingestor¶
backend_port¶The port number the ingestor backends are listening on
- Default
5514
backend_servers¶Array of the ingestor backend IPs
- Default
[]
inbound_port¶The public port of the ingestor service
- Default
5514
kibana¶
auth¶
password¶Basic auth password for kibana. Optional
- Default
""
username¶Basic auth username for kibana. Optional
- Default
""
backend_port¶The port of the kibana backend server(s)
- Default
5601
backend_servers¶The list of kibana servers
inbound_port¶The public port of the kibana service
- Default
80
log_level¶Log level
- Default
info
queue_timeout¶Timeout for requests queued waiting for free connection slots (in seconds)
- Default
30
server_timeout¶Timeout waiting for data from a server (in seconds)
- Default
30
ssl_pem¶SSL certificate (PEM file). Omit if you don’t want to use SSL
syslog_server¶An IPv4 address optionally followed by a colon and a UDP port. It can also be an IPv6 address or filesystem path to a UNIX domain socket.
- Default
127.0.0.1
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/haproxy/ directory
(learn more).
bin/haproxy_ctl(fromhaproxy_ctl)bin/monit_debugger(frommonit_debugger)config/cert.pem(fromcert.pem.erb)config/haproxy.config(fromhaproxy.config.erb)data/properties.sh(fromproperties.sh.erb)helpers/ctl_setup.sh(fromhelpers/ctl_setup.sh)helpers/ctl_utils.sh(fromhelpers/ctl_utils.sh)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/ directory.