metricsgateway job from app-autoscaler/12.2.1
Github source:
39557d4a
or
master branch
Properties¶
autoscaler
¶
metricsgateway
¶
app_manager
¶
app_refresh_interval
¶The time interval to refresh cached application from policy database
- Default
60s
emitter
¶
buffer_size
¶The size of channel in each emitter to store envelopes before sending to metricsserver
- Default
500
handshake_timeout
¶The timeout of webscoket handshake between emitter and metricsserver
- Default
1s
keep_alive_interval
¶The time interval of keep alive for the websocket connection between emitter and metricsserver
- Default
5s
max_close_retry_count
¶The maximum retry times to close a websocket connection between emitter and metricsserver
- Default
5
max_setup_retry_count
¶The maximum retry times to set up a websocket connection between emitter and metricsserver
- Default
5
metricsserver_client
¶ca_cert
¶PEM-encoded ca certificate of metricsserver
cert
¶PEM-encoded tls client certificate to connect to metricsserver
key
¶PEM-encoded tls client key to connect to metricsserver
retry_delay
¶The duration between two websocket retrying
- Default
10s
envelop_chan_size
¶The channel size to transport envelope from nozzles to emitters
- Default
500
health
¶
ca_cert
¶PEM-encoded CA certificate for the health endpoint
password
¶the password of health endpoint
- Default
""
port
¶The listening port of health endpoint
- Default
6503
server_cert
¶PEM-encoded server certificate for the health endpoint
server_key
¶PEM-encoded server key for the health endpoint
username
¶the username of health endpoint
- Default
""
logging
¶
level
¶The level of logging
- Default
info
nozzle
¶
loggregator_rlp_tls
¶ca_cert
¶PEM-encoded ca certificate of ReverseLogProxy
cert
¶PEM-encoded tls client certificate to connect to ReverseLogProxy
key
¶PEM-encoded tls client key to connect to ReverseLogProxy
rlp_addr
¶The address of ReverseLogProxy
shard_id
¶The shard id for nozzle to fetch envelopes from ReverseLogProxy
- Default
CF_AUTOSCALER
nozzle_count
¶The go-loggregator client count in a metricsgateway
- Default
3
policy_db
¶
address
¶IP address on which the policydb server will listen
- Default
autoscalerpostgres.service.cf.internal
databases
¶The list of databases used in policydb database including name
db_scheme
¶Database scheme to be used to access policydb
port
¶Port on which the policydb server will listen
roles
¶The list of database roles used in policydb database including name/password
sslmode
¶The sslmode to connect to postgres server
- Default
disable
tls
¶
ca
¶PEM-encoded ca certificate of tls database server
- Default
""
certificate
¶PEM-encoded certificate of tls database client
- Default
""
private_key
¶PEM-encoded key of tls database client
- Default
""
policy_db_connection_config
¶
connection_max_lifetime
¶
- Default
60s
max_idle_connections
¶
- Default
10
max_open_connections
¶
- Default
20
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/metricsgateway/
directory
(learn more).
bin/bpm-pre-start
(frombpm-pre-start.erb
)config/bpm.yml
(frombpm.yml.erb
)config/certs/healthendpoint/ca.crt
(fromhealthendpoint_ca.crt.erb
)config/certs/healthendpoint/server.crt
(fromhealthendpoint.crt.erb
)config/certs/healthendpoint/server.key
(fromhealthendpoint.key.erb
)config/certs/metricsserver_client/ca.crt
(frommetricsserver_client_ca.crt.erb
)config/certs/metricsserver_client/server.crt
(frommetricsserver_client.crt.erb
)config/certs/metricsserver_client/server.key
(frommetricsserver_client.key.erb
)config/certs/policy_db/ca.crt
(frompolicy_db_ca.crt.erb
)config/certs/policy_db/crt
(frompolicy_db.crt.erb
)config/certs/policy_db/key
(frompolicy_db.key.erb
)config/certs/reverselogproxy_client/ca.crt
(fromreverselogproxy_client_ca.crt.erb
)config/certs/reverselogproxy_client/client.crt
(fromreverselogproxy_client.crt.erb
)config/certs/reverselogproxy_client/client.key
(fromreverselogproxy_client.key.erb
)config/metricsgateway.yml
(frommetricsgateway.yml.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.