Monsyne Dragon f5a03f1afe Fixes for stacktach verifier processes
Fix memory usage for verifiers. Events to verify were being loaded
from the db into an in-memory fifo queue to spool to worker processes.
This was not being limited, resulting in a large amount of memory
being used if events were read from the DB faster than they were
being processed. This change pauses the loading of events if the
in-memory queue grows larger than specified batchsize.

Also, verifier child processes were not handling signals (like SIGTERM)
properly, resulting in them not shutting down properly.
Added proper signal handling.

Change-Id: Ife25ca07398acf111f4388071b5f2e4eafeecb05
2016-07-21 22:54:48 +00:00
2014-03-19 15:19:09 +04:00
2014-03-28 11:47:16 -03:00
2014-01-06 11:14:03 -05:00
2012-10-26 15:00:50 -03:00
2014-03-28 11:47:16 -03:00
2014-03-28 11:47:16 -03:00
2015-07-12 17:48:58 -07:00
2013-12-12 13:00:46 +05:30
2013-09-13 13:21:33 -04:00
2014-03-28 11:47:16 -03:00
2014-01-17 18:40:19 +00:00
2014-01-17 17:50:13 +00:00
2014-03-28 11:47:16 -03:00
2014-03-28 11:47:16 -03:00

Build Status

StackTach

StackTach is a debugging / monitoring utility for OpenStack ([Open]StackTach[ometer]). StackTach can work with multiple datacenters including multi-cell deployments.

Watch the video here: http://www.youtube.com/watch?v=pZgwDHZ3wm0

Overview

OpenStack has the ability to publish notifications to a RabbitMQ exchange as they occur. So, rather than pouring through reams of logs across multiple servers, you can now watch requests travel through the system from a single location.

A detailed description of the notifications published by OpenStack is available here

Documentation

http://stacktach.readthedocs.org/

Description
Event-based Debugging, Monitoring and Billing solution for OpenStack.
Readme 1.2 MiB
Languages
Python 94.3%
PLpgSQL 3.9%
HTML 0.8%
Shell 0.5%
JavaScript 0.3%
Other 0.2%