datadog-firehose-nozzle job from datadog-firehose-nozzle/73
Github source:
1b44bf5
or
master branch
Properties¶
cc
¶
endpoint
¶Cloud Controller Endpoint for getting appmetrics
- Default
""
datadog
¶
additional_api_key_1
¶The datadog API key to use while submitting requests for additional endpoint url 1
additional_api_key_2
¶The datadog API key to use while submitting requests for additional endpoint url 2
additional_api_key_3
¶The datadog API key to use while submitting requests for additional endpoint url 3
additional_api_key_4
¶The datadog API key to use while submitting requests for additional endpoint url 4
additional_api_key_5
¶The datadog API key to use while submitting requests for additional endpoint url 5
additional_api_url_1
¶Additional Endpoint URL 1 for datadog
- Default
https://app.datadoghq.com/api/v1/series
additional_api_url_2
¶Additional Endpoint URL 2 for datadog
- Default
https://app.datadoghq.com/api/v1/series
additional_api_url_3
¶Additional Endpoint URL 3 for datadog
- Default
https://app.datadoghq.com/api/v1/series
additional_api_url_4
¶Additional Endpoint URL 4 for datadog
- Default
https://app.datadoghq.com/api/v1/series
additional_api_url_5
¶Additional Endpoint URL 5 for datadog
- Default
https://app.datadoghq.com/api/v1/series
api_key
¶The datadog API key to use while submitting requests
api_url
¶The REST API Endpoint for datadog
- Default
https://app.datadoghq.com/api/v1/series
custom_tags
¶Send up custom tags with every request (e.g. to label your foundries)
- Default
[]
flush_duration_seconds
¶The duration in seconds between flushes to datadog
- Default
15
flush_max_bytes
¶The maximum number of bytes to send per POST request
- Default
2.097152e+06
logrotate
¶
freq_min
¶The frequency in minutes which logrotate will rotate VM logs
- Default
5
rotate
¶The number of files that logrotate will keep around on the VM
- Default
3
size
¶The size at which logrotate will decide to rotate the log file
- Default
50M
metric_prefix
¶Text which will be prepended to each metric name submitted to datadog
- Default
cloudfoundry.nozzle.
tags
¶Send up custom tags with every request (e.g. to label your foundries)
- Default
[]
timeout_seconds
¶The number of seconds to set the timeout for writes to Datadog
- Default
5
loggregator
¶
traffic_controller_url
¶Traffic controller URL (not necessary if you have cc.endpoint)
- Default
""
nozzle
¶
app_metrics
¶Turn on grabbing of app metrics (may substantially increase load)
- Default
true
deployment
¶Name of deployment (added as tag on all outgoing metrics)
deployment_filter
¶If set, this will filter out envelopes that do not match the deployment name
- Default
""
disable_access_control
¶Datadog Nozzle bypasses authentication with the UAA
- Default
false
environment
¶The name of the environment where the nozzle is running
- Default
""
grab_interval
¶The Interval (in minutes) to update the app metadata
- Default
10
http_proxy_url
¶Use an http proxy
- Default
""
https_proxy_url
¶Use an https proxy
- Default
""
idle_timeout_seconds
¶Number of seconds to wait before timing out the read to the firehose, if there are no messages
- Default
60
insecure_ssl_skip_verify
¶Skip verifying SSL certificate
no_proxy
¶Hosts that should skip the proxy
- Default
""
subscription_id
¶The subscription id to be used for the firehose
workers
¶The number of worker threads to use
- Default
4
uaa
¶
client
¶The client that has access to the loggregator firehose
client_secret
¶The secret for the user
url
¶URL for the UAA server
Templates¶
Templates are rendered and placed onto corresponding
instances during the deployment process. This job's templates
will be placed into /var/vcap/jobs/datadog-firehose-nozzle/
directory
(learn more).
bin/clean_config.py
(fromclean_config.py
)bin/datadog-firehose-nozzle-ctl
(fromdatadog-firehose-nozzle-ctl.erb
)bin/flare
(fromflare.erb
)config/datadog-firehose-nozzle.json
(fromdatadog-firehose-nozzle.json.erb
)config/datadog_logrotate.cron
(fromdatadog_logrotate.cron.erb
)config/logrotate.conf
(fromlogrotate.conf.erb
)
Packages¶
Packages are compiled and placed onto corresponding
instances during the deployment process. Packages will be
placed into /var/vcap/packages/
directory.