Monasca Database Persister
Go to file
Adrian Czarnecki 5f168778c6 Use oslo-config-generator
To generate the sample config file, do what other OpenStack projects do
and use the oslo.config provided mechanism.

Story: 2001009
Task:  4201

Change-Id: I490de4110843f7dfd618a6a8cc8d6a4e35db65ce
2017-07-28 13:48:01 +02:00
common Ensure the same branch is used for common build 2016-02-10 15:30:38 -07:00
config-generator Use oslo-config-generator 2017-07-28 13:48:01 +02:00
etc/monasca Use oslo-config-generator 2017-07-28 13:48:01 +02:00
java Release version 1.2.1 for Java 2017-02-15 13:49:25 +00:00
monasca_persister Use oslo-config-generator 2017-07-28 13:48:01 +02:00
tools Sync tools/ 2016-08-30 20:17:06 +02:00
.gitignore Use oslo-config-generator 2017-07-28 13:48:01 +02:00
.gitreview Update .gitreview for new namespace 2015-10-17 22:30:59 +00:00
.testr.conf Add unit tests 2017-01-12 09:18:29 +00:00
LICENSE Added copyright header and LICENSE file. 2014-05-01 12:45:08 -06:00 Optimize the link address 2017-04-11 11:59:32 +05:30
bindep.txt Add bindep.txt 2017-04-12 18:10:55 +02:00
pom.xml Release version 1.2.1 for Java 2017-02-15 13:49:25 +00:00
requirements.txt Updated from global requirements 2017-06-15 16:26:08 +00:00 Ensure the same branch is used for common build 2016-02-10 15:30:38 -07:00
setup.cfg Use oslo-config-generator 2017-07-28 13:48:01 +02:00 Updated from global requirements 2017-03-13 19:34:04 +00:00
test-requirements.txt Updated from global requirements 2017-05-15 09:38:29 +02:00
tox.ini Use oslo-config-generator 2017-07-28 13:48:01 +02:00

Team and repository tags

Team and repository tags


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,, 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,, 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 Download and build following instructions in its 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.


  • Purge metrics on shutdown
  • Add more robust offset management in Kafka. Currently, the offset is advanced as each message is read. If the Persister stops after the metric has been read and prior to it being committed to the Metrics and Alarms database, the metric will be lost.
  • Add better handling of SQL exceptions.
  • Complete health check.
  • Specify and document the names of the metrics that are available for monitoring of the Persister.
  • Document the yaml configuration parameters.


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.