x
/
stacktach-quincy
Code Issues Proposed changes

start framing out the plan of attack

This commit is contained in:
Sandy Walsh 2014-06-03 19:00:43 +00:00
parent f2134a8d11
commit b114342c48
1 changed files with 19 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
README.md
View File

@ -1,6 +1,23 @@
quincy
======
REST interface to StackTach.v3
> "If you want to get the answers, talk to Quincy ..."
![Quincy](images/quincy.jpg)
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. All of the client cmdline and
library tools will work with 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.