Monasca Database Persister
Go to file
Craig Bryant 88d7d8ceea Get initial build to work.
Add .gitreview

Change-Id: If8d87bb211fd66dae218322c143905d2ea542ec8
2014-07-15 15:29:35 -06:00
src Ensure that metrics and alarms are flushed on shutdown and that the Kafka 2014-07-13 16:13:32 -06:00
.gitreview Get initial build to work. 2014-07-15 15:29:35 -06:00
LICENSE Added copyright header and LICENSE file. 2014-05-01 12:45:08 -06:00
pom.xml Change the build to use the mon-common from the local repository. Updated README.md with build instructions. 2014-07-08 13:01:36 -06:00
README.md Change the build to use the mon-common from the local repository. Updated README.md with build instructions. 2014-07-08 13:01:36 -06:00

mon-persister

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 primarly a Web service it uses DropWizard, https://dropwizard.github.io/dropwizard/, which provides a nice Web appliction 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 the Message Queue.

Build

Requires mon-common from https://github.com/hpcloud-mon/mon-common. Download and build following instructions in its README.md. Then build mon-persister by:

mvn clean package

TODO

  • 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.

License

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

http://www.apache.org/licenses/LICENSE-2.0

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.