Clarify dependency on cachetools in recreate-metric-id tool
It was found in some installations that python-cachetools needed to be present on the system. This can happen if the installation was configured for the Java mon-persister but the recreate-metric-id tool is written in Python. Added a bullet item to describe this dependency and the quick workaround of installing the python-cachetools package. Change-Id: I25635c069a5ed21342780a28b516c74b61dae30b Story:
|1 week ago|
|common||2 weeks ago|
|config-generator||4 months ago|
|docker||2 weeks ago|
|etc/monasca||8 months ago|
|java||7 months ago|
|monasca_persister||1 week ago|
|perf||4 months ago|
|playbooks||2 months ago|
|releasenotes||2 months ago|
|.coveragerc||2 months ago|
|.gitignore||3 months ago|
|.gitreview||2 months ago|
|.stestr.conf||1 year ago|
|.testr.conf||2 years ago|
|.zuul.yaml||2 months ago|
|LICENSE||5 years ago|
|README.rst||3 months ago|
|bindep.txt||2 years ago|
|lower-constraints.txt||3 months ago|
|pom.xml||1 year ago|
|requirements.txt||1 year ago|
|run_maven.sh||3 years ago|
|setup.cfg||3 months ago|
|setup.py||2 years ago|
|test-requirements.txt||3 months ago|
|tox.ini||2 weeks ago|
The Monitoring Persister consumes metrics and alarm state transitions from the Message Queue and stores them in the Metrics and Alarms database.
Although the Persister isn't primarily a Web service it uses DropWizard, https://dropwizard.github.io/dropwizard/, which provides a nice Web application framework to expose an http endpoint that provides an interface through which metrics about the Persister can be queried as well as health status.
The basic design of the Persister is to have one Kafka consumer publish to a Disruptor, https://github.com/LMAX-Exchange/disruptor, that has output processors. The output processors use prepared batch statements to write to the Metrics and Alarms database.
The number of output processors/threads in the Persister can be specified to scale to more messages. To horizontally scale and provide fault-tolerance any number of Persisters can be started as consumers from the Message Queue.
Requires monasca-common from https://github.com/openstack/monasca-common. Download and build following instructions in its README.md. Then build monasca-persister by:
mvn clean package
A sample configuration file is available in java/src/deb/etc/persister-config.yml-sample.
A second configuration file is provided in java/src/main/resources/persister-config.yml for use with the vagrant "mini-mon" development environment.
Copyright (c) 2014 Hewlett-Packard Development Company, L.P.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
To install the Python monasca-persister modules, git clone the source and run the following command:
$ sudo python setup.py install
To run the unit tests use:
$ tox -e py27,py35