REST interface to StackTach.v3

Go to file

Eddie Sheffield f392a3f97a Add functionality for counting events Similar to the existing streams functionality, this patch exposes in quincy the ability added to winchester and quince to count filtered events. There are corresponding changes in winchester, quince, and klugman. Change-Id: If2cdb66c4752fd19eac642a6fbec3c5d45745d29		2015-03-20 12:44:44 -04:00
images	added quincy image	2014-06-03 15:33:13 -03:00
quincy	Add functionality for counting events	2015-03-20 12:44:44 -04:00
.gitignore	Initial commit	2014-06-03 15:18:41 -03:00
.gitreview	Add fixes for basic stream api support	2014-12-02 16:28:53 +00:00
LICENSE	Initial commit	2014-06-03 15:18:41 -03:00
README.md	feeling it out	2014-06-06 11:35:26 +00:00
requirements.txt	Add fixes for basic stream api support	2014-12-02 16:28:53 +00:00
setup.cfg	Add functionality for counting events	2015-03-20 12:44:44 -04:00
setup.py	feeling it out	2014-06-06 11:35:26 +00:00
tox.ini	well, it loads anyway	2014-06-09 22:55:44 -03:00

README.md

quincy

"If you want to get the answers, talk to Quincy ..."

Just like the famous forensic pathologist, you can talk to Quincy to ask questions of StackTach.v3. "How happened to this instance?" "How did it die?" "Who touched it last?" "Was it in pain?"

Quincy is a REST interface for StackTach.v3 ... but it's only the API, there is no implementation. The default implementation is a dummy one for testing purposes. You can specify different implementations as you like. So, if you have another monitoring service that you would like to expose with a StackTach.v3 interface, you can adopt Quincy. However, if you want to work with StackTach.v3, there is a quince driver that handles that for you.

Later in this document we will show you how to configure Quincy to use the Quince drivers.

The klugman library is both a cmdline tool for accessing quincy and a python library for programmatically accessing it.

api

.../v1/
.../v1/events/