search

openruko / logplex

Logplex - primitive, debugging aid, somewhat compatible logplex server
6 stars 4 forks source link

compatible with Heroku/Logplex API #2

Open Filirom1 opened 11 years ago

Filirom1 commented 11 years ago

OpenRuko could not use Heroku/Logplex because it is not usable outside Heroku.

But things are changing, and if OpenRuko/Logplex API are compatible with Heroku/Logplex API, it could make the transition easier.

The Heroku/Logplex API: https://github.com/heroku/logplex/blob/master/doc/README.logplex_api.md

sitepodmatt commented 11 years ago

I think initially if you have a 2 week crunch, we should get logplex working from client tools fully, i.e. make sure tail etc.. are passed and interrupted properly, ignoring the rest of the API. Logplex is a beast, I tried to make headed with the Heroku version but at least a few months ago all the rebar config pointed to internal herokai repos, it had a direct dependency on a very specific version of redis etc.. things might of changed now

Filirom1 commented 11 years ago

There is a public-logplex branch now, that one day might work for us, but, we don't know when.

We also have a project called logdunum that persist logs in MongoDB. We are thinking of making this project the first OpenRuko addons, that will receive logs via Logplex drains, and persist them on MongoDB.

Filirom1 commented 11 years ago

The public-logplex branch seems to work: https://github.com/heroku/logplex/issues/24. Yet I don't know if I am able to debug erlang on production :-/

Being heroku logplex API compatible is not difficult. So one day, if we want to switch from our dead simple logplex to the scalable and error resilient heroku logplex that will make things easier.

An other option is to also make openruko/logplex using redis, and redis data structure compatible to become a true clone of heroku logplex in node.js. The nodejs nsync equivalent is https://github.com/pconstr/redis-sync, but it doesn't look to be very active.