The etcd Metrics Server is meant to be collocated with the etcd server to collect and expose runtime statistics for the Collector.
???s with appropriate values.
Following example does not account for release job
collocation or for optional/conflicting properties.
PEM-encoded CA certificate
PEM-encoded client certificate
PEM-encoded client key
DNS suffix of the etcd server to instrument. Target etcd server must be colocated with this etcd_metrics_server. This property is only used if ‘etcd_metrics_server.etcd.require_ssl’ is ‘true’.”
Address of any etcd server to instrument. Target etcd server does not need to be colocated with this etcd_metrics_server. This address must be an IP or a domain name that resolves to a single etcd server. This property is only used if ‘etcd_metrics_server.etcd.require_ssl’ is ‘false’.
port of etcd server to instrument
enable ssl for all communication with etcd
basic auth password for metrics server (leave empty for generated)
listening port for metrics server
basic auth username for metrics server (leave empty for generated)
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into
- bin/etcd_metrics_server_ctl (etcd_metrics_server_ctl.erb)
- bin/pre-start (pre-start.erb)
- certs/ca.crt (ca.crt.erb)
- certs/client.crt (client.crt.erb)
- certs/client.key (client.key.erb)