REST interface to StackTach.v3
Go to file
OpenDev Sysadmins 6bee8d3a26 OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
2019-04-19 19:51:13 +00:00
images added quincy image 2014-06-03 15:33:13 -03:00
quincy Add PEP8 check and fix related issues 2015-05-04 15:53:56 -05:00
.gitignore Add PEP8 check and fix related issues 2015-05-04 15:53:56 -05:00
.gitreview OpenDev Migration Patch 2019-04-19 19:51:13 +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 PEP8 check and fix related issues 2015-05-04 15:53:56 -05: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 Add PEP8 check and fix related issues 2015-05-04 15:53:56 -05:00

README.md

quincy

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

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/