Hi,
I recently discovered the work pushed into the Hindsight repository (
https://github.com/trink/hindsight) which seems to be a lightweight
alternative to Heka, based on the lua sandbox.
The Hindsight vs Heka benchmarks are quite impressive.
I'm currently running Heka on the raspberry pi (not s
- It is usable and being actively developed with the intent to move it into
production later this year.
- We are currently running production data through it for testing but it is
not deployed in an official capacity. It has been very stable but until a
more robust set of tests have been build out
Thanks a lot for your answers.
And yes, I'm very interested in bootstrapping a first prototype of my own
data pipeline based on Hindsight so that I can compare the performance on a
raspberry pi.
(here is the current state of our Heka-based data pipeline:
https://bitbucket.org/helioslite/heka-hl-sa
I now have some time to do a few tests with Hindsight, so I tried to
compile it on our targeted arm platform (raspberry pi), but I get the
following error:
root@hl-mc--dev:~/hindsight/release# cmake -DCMAKE_BUILD_TYPE=release ..
-- The C compiler identification is GNU 4.7.2
-- The CXX compiler
Yeah, I have only been building on Ubuntu and haven't done any cross
platform clean-up. Thanks for the build output I will fix those errors
(unless you already have a patch).
Trink
On Tue, Jul 7, 2015 at 5:57 AM, bruno binet wrote:
> I now have some time to do a few tests with Hindsight, so I
Ok, thanks.
And sorry, but I don't have a patch (don't know how to fix this kind of
compilation issue).
On 7 July 2015 at 16:17, Michael Trinkala wrote:
> Yeah, I have only been building on Ubuntu and haven't done any cross
> platform clean-up. Thanks for the build output I will fix those error
I changed the checkpoint id to an unsigned long long. Can you test out the
branch and add any other compilation errors to the issue (closing out this
email thread). I am also taking suggestions/recommendations for a CI build
system that supports multiple platforms. TravisCI adds almost no value
s
Sure, I will try your branch and report possible new compilation issues in
github.
Cheers,
Bruno
On 7 July 2015 at 18:26, Michael Trinkala wrote:
> I changed the checkpoint id to an unsigned long long. Can you test out the
> branch and add any other compilation errors to the issue (closing out
Back from vacations, I'm now playing again with Hindsight on a raspberry pi.
As reported on github
https://github.com/trink/hindsight/issues/1#issuecomment-119593775 the
compilation now succeeds.
So getting inspiration from the examples in the benchmarks directory, I
tried to create a Hindsight co
There is no message looping in Hindsight (one analysis plugin cannot
consume the output of another analysis plugin). In your example the
decoding should happen in the input. Heka has Inputs, splitters, and
decoder (in Hindsight it is just an Input and common functionality can be
split into module
I see, so I need to investigate how I can merge my multiple lua sandbox
filters into a single one.
This make me wondering if there is some other differences between Hindsight
and Heka?
The fact that only one analysis plugin cannot consume the output of another
analysis plugin is the only differenc
There are a few intentional changes between Heka and Hindsight. Looping
messages in Heka has always been a bad idea so it was removed. There are a
few API enhancements such as a protobuf stream reader and writer.
Checkpoint are all managed by the Hindsight infrastructure (so much of the
burden is
Thanks for all this valuable information.
On 11 August 2015 at 17:17, Michael Trinkala wrote:
> There are a few intentional changes between Heka and Hindsight. Looping
> messages in Heka has always been a bad idea so it was removed.
>
Personally I like the looping messages feature in Heka as i
On 12 August 2015 at 10:19, bruno binet wrote:
> Thanks for all this valuable information.
>
> On 11 August 2015 at 17:17, Michael Trinkala
> wrote:
>
>> There are a few intentional changes between Heka and Hindsight. Looping
>> messages in Heka has always been a bad idea so it was removed.
>>
Most looping requirements can be flatten out: i.e., alerting can be handled
in the output plugins in your example and aggregation/sessionization etc
can be handled in the inputs. As for sharing: things fall into place when
you start thinking about it from a module level instead of an individual
plu
On 12 August 2015 at 18:16, Michael Trinkala wrote:
> Most looping requirements can be flatten out: i.e., alerting can be
> handled in the output plugins in your example and
> aggregation/sessionization etc can be handled in the inputs. As for
> sharing: things fall into place when you start thin
Yes, I will get the plugins checked in shortly I just need to add a config
option or two.
run once - set the ticker_interval to 0 and return from process_message
when you are done
polling - set the ticker_interval > 0 and return from process_message, it
will be called again when the ticker interva
Hi Michael,
Thanks again for your answer.
I've also seen that you have checked in your "prune_input.lua plugin" on
github:
https://github.com/trink/hindsight/blob/master/sandboxes/input/prune_input.lua
This is very useful, and I'm wondering if you also have a similar pruning
plugin that could prun
Generally I only use the prune for reporting in which case I don't want it
to clean up the results but it would be pretty easy to include the analysis
directory as a config option.
Yes, there is up to a second of latency on detecting/reading the rolled
logs. It is there to prevent rapid polling w
On 16 September 2015 at 00:19, Michael Trinkala
wrote:
> Generally I only use the prune for reporting in which case I don't want it
> to clean up the results but it would be pretty easy to include the analysis
> directory as a config option.
>
Here is a pull request to support analysis plugins t
Hello,
We've started to play with Hindsight internally and our sandboxes work just
fine. That's really neat!
I remember that Trink mentioned at some point that Hindsight (and the Lua
sandbox I guess) will be packaged as deb/rpm. Is there any news on this
side?
Thanks,
Simon
21 matches
Mail list logo
