metron_agent job from cf/212
Github source:
ae2ec7a5
or
master branch
Properties¶
etcd
¶
machines
¶IPs pointing to the ETCD cluster
maxconcurrentrequests
¶Number of concurrent requests to ETCD
- Default
10
loggregator
¶
dropsonde_incoming_port
¶Port where loggregator listens for dropsonde log messages
- Default
3457
incoming_port
¶Port where loggregator listens for legacy log messages
- Default
3456
loggregator_endpoint
¶
shared_secret
¶Shared secret used to verify cryptographically signed loggregator messages
metron_agent
¶
collector_registrar_interval_milliseconds
¶Interval for registering with collector
- Default
60000
debug
¶boolean value to turn on verbose mode
- Default
false
deployment
¶Name of deployment (added as tag on all outgoing metrics)
dropsonde_incoming_port
¶Incoming port for dropsonde log messages
- Default
3457
etcd_query_interval_milliseconds
¶Interval for querying ETCD for trafficcontroller heartbeats
- Default
5000
incoming_port
¶Incoming port for legacy log messages
- Default
3456
status
¶
password
¶password used to log into varz endpoint
- Default
""
port
¶port used to run the varz endpoint
- Default
0
user
¶username used to log into varz endpoint
- Default
""
zone
¶Availability zone where this agent is running
nats
¶
machines
¶IP addresses of Cloud Foundry NATS servers
password
¶Password for cc client to connect to NATS
port
¶IP port of Cloud Foundry NATS server
user
¶Username for cc client to connect to NATS
syslog_daemon_config
¶
address
¶IP address for syslog aggregator
port
¶TCP port of syslog aggregator
transport
¶Transport to be used when forwarding logs (tcp|udp|relp).
- 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/metron_agent/
directory
(learn more).
bin/metron_agent_ctl
(frommetron_agent_ctl.erb
)config/metron_agent.json
(frommetron_agent.json.erb
)config/syslog_forwarder.conf
(fromsyslog_forwarder.conf.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.