Skip to content

telemetry-centralizer job from telemetry/0.13.3-xenial

Github source: 8624a3e or master branch

Properties

audit_mode

If enabled, telemetry data will be kept on disk but not sent

Default
false

flush_interval

Time in seconds for the Centralizer to forward a telemetry batch

Default
3600

port

Port to listen on for fluent forward protocol

Default
24224

telemetry

api_key

Bearer token for authenticating against telemetry endpoint

data_collection_multi_select_options

The data collection programs the user has opted into

Default
[]

endpoint

HTTP endpoint to send telemetry batches to

env_type

The environment type of the foundation

foundation_id

The unique ID of the foundation

foundation_nickname

The nickname of the foundation used in reporting by VMware

iaas_type

The IaaS type of the foundation

operational_data_only

Whether only operational data is being collected

proxy_settings

http_proxy

the http proxy to send telemetry data through

Default
""
https_proxy

the https proxy to send telemetry data through

Default
""
no_proxy

list of hostnames to not interact with through the current proxy settings (http(s)_proxy settings)

Default
""

tls

agent_cert

TLS Certificate for telemetry agents to consume

agent_private_key

TLS Private Key for telemetry agents to consume

ca_cert

TLS CA for telemetry certificates

cert

TLS Certificate for the Centralizer

private_key

TLS Private Key for the Centralizer

Templates

Templates are rendered and placed onto corresponding instances during the deployment process. This job's templates will be placed into /var/vcap/jobs/telemetry-centralizer/ directory (learn more).

  • bin/telemetry_centralizer (from telemetry_centralizer.erb)
  • config/bpm.yml (from bpm.yml.erb)
  • config/ca_cert.pem (from ca_cert.pem.erb)
  • config/cert.pem (from cert.pem.erb)
  • config/curl_config (from curl_config.erb)
  • config/fluent.cnf (from config.erb)
  • config/private_key.pem (from private_key.pem.erb)

Packages

Packages are compiled and placed onto corresponding instances during the deployment process. Packages will be placed into /var/vcap/packages/ directory.