monasca-agent/agent.conf.template
gary-hessler 95b38bcd39 Fixing issue with API reconnection
The agent had issues with the token when the API would go down and come back up again
Added a message queue to buffer metrics when the API was down or unreachable
Removed some excess logging of messages in debug

Change-Id: Ib1300bc0c66e00b06302b2b2f875f991520c9f1f
2014-10-10 12:31:37 -06:00

141 lines
5.6 KiB
Plaintext

[Api]
# Monitoring API URL: URL for the monitoring API
# Example: https://region-a.geo-1.monitoring.hpcloudsvc.com/v1.1/metrics
url: {args.monasca_url}
# Keystone Username
username: {args.username}
# Keystone Password
password: {args.password}
# Keystone API URL: URL for the Keystone server to use
# Example: https://region-a.geo-1.identity.hpcloudsvc.com:35357/v3/
keystone_url: {args.keystone_url}
# Project name to be used by this agent
project_name: {args.project_name}
# The following 2 options are for handling buffering and reconnection to the monasca-api
# If you want the messages to be sent as fast as possible, set these two options to
# the same number. If you have a larger system with many agents, you may want to throttle
# the number of messages sent to the API by setting the backlog_send_rate to a lower number.
# Maximum number of messages to buffer when unable to communicate with the monasca-api
max_buffer_size: 1000
# Maximum number of messages to send at one time when communication with the monasca-api is restored
backlog_send_rate: 1000
[Main]
# Force the hostname to whatever you want.
hostname: {hostname}
# Optional dimensions to be sent with every metric from this node
# They should be in the format name:value and seperated by a comma
# Example (dimensions: service:nova, group:group_a, ...)
dimensions: service:{args.service}
# Set the threshold for accepting points to allow anything
# with recent_point_threshold seconds
# Defaults to 30 seconds if no value is provided
#recent_point_threshold: 30
# Use mount points instead of volumes to track disk and fs metrics
use_mount: no
# Change port the Agent is listening to
# listen_port: 17123
# Additional directory to look for checks
# additional_checksd: /etc/monasca/agent/checks.d/
# Allow non-local traffic to this Agent
# This is required when using this Agent as a proxy for other Agents
# that might not have an internet connection
# For more information, please see
# https://github.com/DataDog/dd-agent/wiki/Network-Traffic-and-Proxy-Configuration
# non_local_traffic: no
# ========================================================================== #
# MonStatsd configuration #
# ========================================================================== #
# MonStatsd is a small server that aggregates your custom app metrics.
# Make sure your client is sending to the same port.
monstatsd_port : 8125
## The monstatsd flush period.
# monstatsd_interval : 10
## If 'yes', counters and rates will be normalized to 1 second (that is divided
## by the monstatsd_interval) before being sent to the server. Defaults to 'yes'
# monstatsd_normalize : yes
# If you want to forward every packet received by the monstatsd server
# to another statsd server, uncomment these lines.
# WARNING: Make sure that forwarded packets are regular statsd packets and not "monstatsd" packets,
# as your other statsd server might not be able to handle them.
# statsd_forward_host: address_of_own_statsd_server
# statsd_forward_port: 8125
# ========================================================================== #
# Service-specific configuration #
# ========================================================================== #
# -------------------------------------------------------------------------- #
# Disk #
# -------------------------------------------------------------------------- #
# Some infrastrucures have many constantly changing virtual devices (e.g. folks
# running constantly churning linux containers) whose metrics aren't
# interesting. To filter out a particular pattern of devices
# from collection, configure a regex here:
# device_blacklist_re: .*\/dev\/mapper\/lxc-box.*
# -------------------------------------------------------------------------- #
# Dogstream (log file parser)
# -------------------------------------------------------------------------- #
# Comma-separated list of logs to parse and optionally custom parsers to use.
# The form should look like this:
#
# dogstreams: /path/to/log1:parsers_module:custom_parser, /path/to/log2, /path/to/log3, ...
#
# Or this:
#
# dogstreams: /path/to/log1:/path/to/my/parsers_module.py:custom_parser, /path/to/log2, /path/to/log3, ...
#
# Each entry is a path to a log file and optionally a Python module/function pair
# separated by colons.
#
# Custom parsers should take a 2 parameters, a logger object and
# a string parameter of the current line to parse. It should return a tuple of
# the form:
# (metric (str), timestamp (unix timestamp), value (float), attributes (dict))
# where attributes should at least contain the key 'metric_type', specifying
# whether the given metric is a 'counter' or 'gauge'.
#
# Unless parsers are specified with an absolute path, the modules must exist in
# the Agent's PYTHONPATH. You can set this as an environment variable when
# starting the Agent. If the name of the custom parser function is not passed,
# 'parser' is assumed.
#
# If this value isn't specified, the default parser assumes this log format:
# metric timestamp value key0=val0 key1=val1 ...
#
# ========================================================================== #
# Logging
# ========================================================================== #
log_level: INFO
collector_log_file: /var/log/monasca/agent/collector.log
forwarder_log_file: /var/log/monasca/agent/forwarder.log
monstatsd_log_file: /var/log/monasca/agent/monstatsd.log
# if syslog is enabled but a host and port are not set, a local domain socket
# connection will be attempted
#
# log_to_syslog: yes
# syslog_host:
# syslog_port: