Skip to content

loggr-expvar-forwarder job from loggregator-agent/3.3

Github source: 3afa057 or master branch

Properties

counters

An array of Objects that have the following fields: - addr: address of the expvar endpoint - name: The output name of the Counter - source_id: The output sourceID of the Counter - template: The golang text/template to find the metric in the expvar output. - tags: An object that can only have string values. They will be passed as tags on the envelope.

Default
[]

default_source_id

Source ID to use for reported metrics when none is provided.

gauges

An array of Objects that have the following fields: - addr: address of the expvar endpoint - name: The output name of the Counter - unit: The output unit of the Counter - source_id: The output sourceID of the Counter - template: The golang text/template to find the metric in the expvar output. - tags: An object that can only have string values. They will be passed as tags on the envelope.

Default
[]

interval

How often the expvar-forwarder should scrape registered endpoints and report values.

Default
1m

log_agent

addr

The Loggregator ingress address. This is the gRPC host that metrics will be written to.

Default
127.0.0.1:3458

ca_cert

The Loggregator CA certificate in PEM format.

client_cert

The client certificate used to connect to the Loggregator Agent.

client_key

The client private key used to connect to the Loggregator Agent.

Templates

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

  • config/bpm.yml (from bpm.yml.erb)
  • config/certs/ca.crt (from ca.crt.erb)
  • config/certs/forwarder.crt (from forwarder.crt.erb)
  • config/certs/forwarder.key (from forwarder.key.erb)

Packages

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