Monasca Database Persister
Go to file
Hervé Beraud 37411e792a Add doc/requirements
We need to specify doc requirements in doc/requirements.txt
to avoid problems with the pip resolver [1] for the release team [2][3].

Removing specific doc requirements from test-requirements.txt.

The problem here is that this repos haven't doc/requirements.txt file
and by default in this case zuul will use the test-requirements.txt file
to pull requirements [4].

This requirements file contains extra requirements like flake8 that
collided with those allowed in our job environment and so the new pip
resolver fails to install these requirements and the job exits in error.

This project meet the conditions leading to the bug.

Notice that I voluntarily added the doc directory even if no docs
are generated here because zuul will try to pull this requirements from
there first and the contained requirements are needed for reno but AFAIK
the releasenotes dir is ignored by zuul. c.f [4] for further details.

Bump a series of lower-constraints and requirements to work with new pip
resolver, testing with steps outlined at [5]

Fix Flake8 E741 [6]


Change-Id: Ic1504a18a780b0f517c5aa3dd3bfb04998d42e74
2021-01-18 10:55:41 +01:00
common Replace URLs with URLs 2019-06-03 15:33:15 +02:00
config-generator Update documentation to use new default config 2019-02-18 18:21:25 +01:00
doc Add doc/requirements 2021-01-18 10:55:41 +01:00
docker Set legacy_kafka_client_enabled = False on default for Docker 2020-10-23 13:25:41 +02:00
etc/monasca Turn logging down from DEBUG in persister-logging.conf 2018-09-28 16:26:36 -07:00
java Deprecate Java implementation 2019-09-17 10:29:34 +02:00
monasca_persister Add doc/requirements 2021-01-18 10:55:41 +01:00
perf Fix the misspelling of "available" 2019-01-22 13:32:21 +08:00
playbooks Push Docker image to Docker Hub 2019-04-15 15:04:28 +02:00
releasenotes Update master for stable/victoria 2020-09-28 15:49:09 +00:00
.coveragerc Add coverage report display 2019-04-05 13:33:43 +02:00
.gitignore Add job for releasenotes 2019-02-19 10:46:25 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:26:25 +00:00
.stestr.conf Add .stestr.conf . 2017-09-22 14:13:18 +02:00
.zuul.yaml Add Python3 wallaby unit tests 2020-10-15 11:30:50 +00:00
CONTRIBUTING.rst Add CONTRIBUTING.rst 2020-05-19 16:25:13 +02:00
LICENSE Added copyright header and LICENSE file. 2014-05-01 12:45:08 -06:00
README.rst Change README.rst with a better title 2019-12-26 10:06:05 +08:00
bindep.txt Add bindep.txt 2017-04-12 18:10:55 +02:00
lower-constraints.txt Add doc/requirements 2021-01-18 10:55:41 +01:00
pom.xml Update links in pom.xml 2018-01-15 16:39:54 +08:00
requirements.txt Remove six 2020-11-24 15:10:57 +01:00 Ensure the same branch is used for common build 2016-02-10 15:30:38 -07:00
setup.cfg [goal] Migrate testing to ubuntu focal 2020-10-13 16:07:06 +02:00 Cleanup py27 support 2020-04-05 09:58:52 +02:00
test-requirements.txt Add doc/requirements 2021-01-18 10:55:41 +01:00
tox.ini Add doc/requirements 2021-01-18 10:55:41 +01:00


Monasca Persister


The Monasca Persister consumes metrics and alarm state transitions from the Apache Kafka message queue and stores them in the time series database.


To install the Python monasca-persister modules, git clone the source and run the following command:

$ pip install -c -e ./monasca-persister

To run the unit tests use:

$ tox -e py36

To start the persister run:

$ monasca-persister --config-file=monasca-persister.conf


A sample configuration file can be generated using the Oslo standards used in other OpenStack projects.

tox -e genconfig

The result will be in ./etc/monasca/monasca-persister.conf.sample

If the deployment is using the Docker files, the configuration template can be found in docker/monasca-persister.conf.j2.


For information on Java implementation see java/Readme.rst.

Contributing and Reporting Bugs

Ongoing work for the Monasca project is tracked in Storyboard.


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.