Riemann is a service for receiving streams of events, and causing one or
more side-effects (sending email, routing to Graphite, etc). It can do
arbitrary transformations on event streams (the effects from an input may
be arbitrarily time shifted), and assumes that the inputs are fixed
structure (n
I've read about Lamina and Narrator, watched the linked videos and I think
I understand how it all fits together:
1) Instrument the applications using Lamina's `instrument` or `trace`
2) Probe the instrumented code somehow by channeling the traces to some
endpoint (how do you do this? do you aut
I was aware of Babbage, but haven't used it. There is a certain similarity
to the syntax, but I think most (if not all) of the things I listed
differentiate Narrator from Babbage, as well. Please correct me if I'm
wrong.
On Sat, Nov 2, 2013 at 3:36 PM, Ben Wolfson wrote:
> seems kind of simil
seems kind of similar to babbage:
https://github.com/ReadyForZero/babbage/tree/1.1
On Sat, Nov 2, 2013 at 3:28 PM, Zach Tellman wrote:
> https://github.com/ztellman/narrator
>
> This is a reimplementation of an approach I've discussed in several talks
> [1] [2], with an eye towards performance,
https://github.com/ztellman/narrator
This is a reimplementation of an approach I've discussed in several talks
[1] [2], with an eye towards performance, memory efficiency, and
flexibility w.r.t. how the event stream is represented. The readme does a
good job of explaining how it works, but the