collector job from cf/209
The collector will discover the various components on the message bus and query their `/healthz` and `/varz` interfaces. The metric data collected is published to collector plugins such as OpenTSDB, AWS CloudWatch and DataDog.
Github source:
35f75e02
or
master branch
Properties¶
collector
¶
aws
¶
access_key_id
¶AWS access key for CloudWatch access
secret_access_key
¶AWS secret for CloudWatch access
datadog
¶
api_key
¶Datadog API key
application_key
¶Datadog application key
deployment_name
¶name for this bosh deployment. All metrics will be tagged with deployment:XXX when sending them to CloudWatch, Datadog and Graphite
graphite
¶
address
¶IP address of Graphite
port
¶TCP port of Graphite
intervals
¶
discover
¶the interval in seconds that the collector attempts to discover components
- Default
60
healthz
¶the interval in seconds that healthz is checked
- Default
30
local_metrics
¶the interval in seconds that local_metrics are checked
- Default
30
nats_ping
¶the interval in seconds that the collector pings nats to record latency
- Default
30
prune
¶the interval in seconds that the collector attempts to prune unresponsive components
- Default
300
varz
¶the interval in seconds that varz is checked
- Default
30
logging_level
¶the logging level for the collector
- Default
info
opentsdb
¶
address
¶IP address of OpenTsdb
port
¶TCP port of OpenTsdb
use_aws_cloudwatch
¶enable CloudWatch plugin
- Default
false
use_datadog
¶enable Datadog plugin
- Default
false
use_graphite
¶enable Graphite plugin
- Default
false
use_tsdb
¶enable OpenTsdb plugin
- Default
false
nats
¶
machines
¶IP of each NATS cluster member.
password
¶NATS password
port
¶NATS TCP port
user
¶NATS user
networks
¶
apps
¶Collector network information.
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/collector/
directory
(learn more).
bin/collector_ctl
(fromcollector_ctl.erb
)config/config.yml
(fromconfig.yml.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.