I think it would be a good if you could add a message or something at the
front page of the github repo to state that this project will soon be
discontinued. Because if I were someone looking for a new tool to use, I
would most definitely be impressed and go ahead and start using it - only
to find
Hi all,
Ali, I share your opinion concerning Heka's strengths. I also think that
Heka stands out because of the flexibility of its filters. There are few to
none lightweight data collectors/shippers that allow to process events with
that many decoders/filters/encoders, with the possibility of
Thanks, Rob!
I have to say, I'm EXTREMELY DISAPPOINTED to hear this.
I have been away from Heka for a while (working on other projects at work)
and am now able to refocus on designing our new data
collection/analysis/reporting system. Once I read this e-mail, I started
looking around to see
On 05/10/2016 12:37 PM, Tony Cesaro wrote:
One of the big selling features for me was the fact that we can deploy
heka as an agent or a server, with the same executable and configure it
to assume the role of one or the other (or both). Splitting these into
separate executables would be a
One of the big selling features for me was the fact that we can deploy heka
as an agent or a server, with the same executable and configure it to
assume the role of one or the other (or both). Splitting these into
separate executables would be a negative in my opinion.
Another point I wanted to
Right, Heka currently has many more data ingestion plugins, so it's very useful
running on the endpoints snarfing up logs and system data and etc. One
possibility that interests me is extracting the Logstreamer code out of Heka
into a standalone utility, which could be used to feed data into
Well, I know I for one am not especially surprised as I think there have
been some hints that this was coming for a while now, but thank you for the
really detailed and clear notice about the future status of Heka. It's
interesting to hear what the pain points have been.
"Yuge" thanks to everyone
Please don't mistake the small size of the documentation as it being
incomplete. What is there is a full reference to the current functionality.
Its small size (when compared to the Heka documentation) is due to the
reduction of complexity in it's design (Hindsight is just a skeleton around
the
Hi Rob,
Thanks for those info about the future of Heka.
You're seeking help to keep heka alive, but what about Hindsight?
It has currently no mailing list, the docs are minimal, and there are
no configuration examples (except the benchmarks dir). Any plan to
improve this? Heka's doc is one of
Hi everyone,
I'm lng overdue in sending out an update about the current state of
and plans for Heka. Unfortunately, what I have to share here will
probably be disappointing for many of you, and it might impact whether
or not you want to continue using it, as all signs point to Heka
10 matches
Mail list logo
