Open Stack

Meniscus is my project at Rackspace.

Our goal is to build a scalable, guaranteed collection and delivery platform for arbitrary messages. It is mainly aimed at gathering log messages from a large number of geographically distributed resources, applying custom routing rules and shipping that information to various data processing platforms like Hadoop, Swift, etc. While we are hoping it will be used by OpenStack services (and it runs on an OpenStack installation), it is capable of handle tenant logging as well as logging for an OpenStack installation.

Our goal is not to provide processing of the log data (although we will offer an ElasticSearch cluster for basic search), but rather to collect and deliver those messages and a secure and compliant way. Other projects could use our platform as a way to collect and distribute messages if they wish, they would still be responsible for creating the event (e.g. talking to libvirt) and processing the messages, but we could take over the collection and transit of those messages at some point.

Hopefully that helps. Feel free to reach out with more questions.


Jarret Raim




From: Endre Karlson [mailto:endre.karlson at gmail.com]
Sent: Monday, May 06, 2013 2:07 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] Monitoring / Logging services in OpenStack

Hi, I am just looking at different things like:
* Ceilometer
* Meniscus - projectmeniscus.org<http://projectmeniscus.org>
* Healthnmon
* Synaps

Where does the project boundaries go? What's the differences?

Endre
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130506/71102da3/attachment.html>