Skip to content

ingestor_cloudfoundry-firehose job from logsearch-for-cloudfoundry/202.0.0

Github source: 1245e745 or master branch

Properties

cloudfoundry

api_endpoint

URI of the CF cloud controller

doppler_endpoint

URI of the loggregator endpoint

firehose_client_id

CF UAA client ID with ‘doppler.firehose’ permissions

Default
""

firehose_client_secret

CF UAA client secret with ‘doppler.firehose’ permissions

Default
""

firehose_events

Comma seperated list of events you would like to get. Valid options are CounterEvent,Error,HttpStartStop,LogMessage,ValueMetric,ContainerMetric

Default
LogMessage

firehose_password

CF UAA password of user with ‘doppler.firehose’ permissions

Default
""

firehose_port

The CF API doppler port, defaults to 443

Default
443

firehose_subscription_id

ID for the firehose-to-syslog subscription

Default
firehose

firehose_user

CF UAA username of user with ‘doppler.firehose’ permissions

Default
""

skip_ssl_validation

Set to true to skip SSL validation when connecting to CF (defaults to false)

Default
false

ingestor_cloudfoundry-firehose

debug

Debug level logging. This disables forwarding to syslog

Default
false

logstash

metadata_level

Whether to include additional metadata throughout the event lifecycle. NONE = disabled, DEBUG = fully enabled

Default
NONE

syslog

host

IP or hostname of the syslog drain

port

port of the syslog drain

Default
5514

protocol

Syslog protocol (tcp/udp).

Default
tcp

Templates

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

  • bin/ingestor_cloudfoundry-firehose_ctl (from bin/ingestor_cloudfoundry-firehose_ctl)
  • bin/monit_debugger (from bin/monit_debugger)
  • data/properties.sh (from data/properties.sh.erb)
  • helpers/ctl_setup.sh (from helpers/ctl_setup.sh)
  • helpers/ctl_utils.sh (from helpers/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.