This adds support for setting the statsd metrics aggregation interval
as part of Monasca setup. Setting this interval is useful for users
calculating rates from statsd metrics.
Story: 2005063
Task: 29607
Change-Id: I22f5f1700c438245fd7e98deb40d706358349b6c
Add configurable maximum size of batches of measumrement to write
to Monasca API. Prevents killing Monasca API in memory limited
configurations. The default is no limit.
Change-Id: I2bf84501cc51c24843d7c3befd8f9dd42f010f0c
Story: 2001434
This will allow deployments of the monasca-agent to monitor systems
belonging to users without needing the credentials of the user, such
as monitoring Trove instances.
Change-Id: I7233e44fd5abe25744c19f24984bddb2e8018dae
Monasca URL is pulled from Keystone Service Catalog when not given
explicitly in agent.yaml, but only the URL with service_type=monitoring
and endpoint_type=publicURL will be retrieved.
These two options together with the region_name have been included in
the agent.yaml template and may be configured by monasca-setup, so that
the KSClient object is initialized with such keywords. This client will
retrieve the URL from Catalog accordingly.
Change-Id: Icfbfa7c46db648e3d3c27f8e5c72d02957c778f1
Closes-Bug: #1625573
Add config option monasca_statsd_port to configure statsd port
via monasca-setup.
Fixes-Bug: #1628401
Change-Id: Ie7b517f06f7b93e5929776ab4a77a388458e3b4b
Size of messages may vary based on the number of metrics the
agent is generating, limiting by measurements will be more stable.
Store messages as json strings when queuing to save space
Change-Id: If6dc0a272a26ac951a5d8823dafd32cab69a3981
Allow the value of sub_collection_warn to be configurable using
monasca_setup. However, use the name plugin_collect_time_warn
as the configuration option since that is easier to understand
Change-Id: I769ec9dd1dcfb1fba5a6da9b59cf03376707c4a6
This is to handle the case of long running plugins that
added together can exceed the collection frequency. Running
the plugins on multiple threads should bring the collection
time down close to the longest running plugin
A Thread pool is created and used if the new parameter
collector_threads is greater than 1
Due to the Global Interpreter Lock, this will only work well
if the checks are I/O bound which seems to be the case so far
Changed the logging messages to reference plugins instead of
checks to match the usage in docs/Agent.md
Plugins are run in reverse order of last collection time.
Plugins that are still running at the end of a collection cycle
are skipped in the next cycle. If all of the pool threads are
blocked too long by plugins, the collector will exit
Plugins are always run in the thread pool even if pool_size is
1 so that the other changes above still work
Change-Id: Ib50f7fe50a26c949a0066baa3d73ff4a25a8de84
Remove name, pattern and recursive in directory check to make
directory check only checks for the size of the target directory
(not file size)
Add directory detection plugin to automatically generate
directory.yaml file
Change-Id: I10fde0a4ed43f62c310045bccccb3a66e07542e1
Add collector_restart_interval in agent.yaml
Fix a table format in agent documentation
Add boundary check for the value of collector_restart_interval
Delete --collector_restart_interval and --sub_collection_warn
from monasca-setup
Change-Id: I909e392ed04bc5b2aebc5875860dd6725a00711f
Add collection time in millisecond for each check in log file (DEBUG).
If the collection time for a single check is larger than the threshold value
for warning (5second as default), a warning message will be created in log file.
Change-Id: Ieb4949fbdd6b3db79de13b52abe2a367afceaa9e
Adding double quotes around the password field handles the problem when
password is something like !h2hboJC8p
Change-Id: Ic62f3c0ed46ca9142b7f6e869fd54dcb206626e4
For the agent I just modified to the config to use the new standard location for custom checks.
For monasca-setup I added automatic plugin detection.
Fixed config compare so order changes don't register as a config change.
Change-Id: I7ab17c894bb0496e30d7f5aa5a1b1cf9684bdf87
Converted the config file to yaml and updated the config processing logic to match.
Cleaned up some deprecated config item processing.
Change-Id: I8c5d9ad841b22d20825608ac9f2c82d8011b04f0
Doug Szumski