christianhellsten / gulag
- Source
- Commits
- Network (1)
- Issues (0)
- Downloads (0)
- Wiki (1)
- Graphs
-
Branch:
master
commit ce2ef5ed03cb6a953070b8af9859c9b216926a50
tree ea18a439098d9e54dc9bf52ad240f312756c410e
parent 935480022cb85e834a5f2fcebce57dead0f41520
tree ea18a439098d9e54dc9bf52ad240f312756c410e
parent 935480022cb85e834a5f2fcebce57dead0f41520
gulag /
| name | age | message | |
|---|---|---|---|
| |
.gitignore | ||
| |
README.textile | ||
| |
app/ | ||
| |
config.ru | ||
| |
gulag.rb | ||
| |
public/ | ||
| |
scripts/ | ||
| |
sinatra - 1a0bdae | ||
| |
spec/ | ||
| |
views/ |
README.textile
Gulag – A prison camp for application errors
Gulag is a log server for application errors. Gulag has a REST API.
How does it work?
GulagLogger, a Rails plugin, captures errors such as exceptions and slow database queries/requests and sends the details to Gulag.
Let me demonstrate:
Application error -> Gulag REST API (HTTP/HTTPs) -> Gulag data store (Tokyo Tyrant)
You, the administrator, can login to the dashboard and view and delete the errors:
Administrator -> Gulag dashboard -> Gulag data store (Tokyo Tyrant)
Why write something like this?
To capture application errors and experiment with Tokyo Cabinet and Sinatra.
What about Hoptoad and GetExceptional
Yeah, I know.
Status
Beta software. Works fine until you break it.
TODO
- More tests
- Review design
- ABCDEF…

