Mozilla Services announces Heka - a tool for high performance data gathering, analysis, monitoring, and reporting.
Introducing Heka
blog.mozilla.org
Introducing Heka
1–10 of 58 posts
Re: Introducing Heka
#2Seems similar to Riemann: http://riemann.io/
Re: Introducing Heka
#3Very interesting. Does this fit in conceptually with circus at all? It seems like there's a fair amount of overlap between the process/HTTP management done by circus and this stats/data collection/analysis (specifically hekad agent in the architecture diagram):
http://heka-docs.readthedocs.org/en/latest/architecture/inde...
I'm curious if Mozilla is using these two tools in combination internally, and what that architecture looks like.
Re: Introducing Heka
#4Is this similar to piwik?
Re: Introducing Heka
#5Off the top of my head this is a reimplementation of the following
* SNMP
* CollectD
* Carbon
* JMX
* WMI
* CMIP
And a whole host of other proprietary transports. So its cool and looks awesome, but what does it give me that the entirety of other monitoring protocols doesn't
Re: Introducing Heka
#6with reference to the name: "and I do live in South Berkeley / North Oakland…"
I had a feeling. We may hope your code is hella tight...
Re: Introducing Heka
#7Off the top of my head this is a reimplementation of the following * SNMP * CollectD * Carbon * JMX * WMI * CMIP And a whole host of other proprietary transports. So its cool and looks awesome, but what does it give me that the entirety of other monitoring protocols doesn't
One of the driving motivations was simplicity for developers and get a reasonable out-of-the-box experience.
This comes from a couple things.
Go compiles to a single static library so you don't have to worry about having dozens of "the right" library installed on your machine. Grab the heka binary and run with it.
This greatly eases our operations work as we have fewer dependency conflicts to deal with when we push things to production.
Re: Introducing Heka
#8Off the top of my head this is a reimplementation of the following * SNMP * CollectD * Carbon * JMX * WMI * CMIP And a whole host of other proprietary transports. So its cool and looks awesome, but what does it give me that the entirety of other monitoring protocols doesn't
One of the driving motivations was simplicity for developers and get a reasonable out-of-the-box experience. This comes from a couple things. Go compiles to a single static library so you don't have to worry about having dozens of "the right" library installed on your machine. Grab the heka binary and run with it. This greatly eases our operations work as we have fewer dependency conflicts to deal with when we push t…
Interesting so its more of a ease of use then a performance issue ? The numbers you quotes for performance seemed impressive.
Re: Introducing Heka
#9Off the top of my head this is a reimplementation of the following * SNMP * CollectD * Carbon * JMX * WMI * CMIP And a whole host of other proprietary transports. So its cool and looks awesome, but what does it give me that the entirety of other monitoring protocols doesn't
One of the driving motivations was simplicity for developers and get a reasonable out-of-the-box experience. This comes from a couple things. Go compiles to a single static library so you don't have to worry about having dozens of "the right" library installed on your machine. Grab the heka binary and run with it. This greatly eases our operations work as we have fewer dependency conflicts to deal with when we push t…
That doesn't make a lot of sense. You don't have to write a monitoring software from scratch just because you want statically compiled bundled libraries. You can do that with any programming language.
Re: Introducing Heka
#10Earlier quoted context omitted.
One of the driving motivations was simplicity for developers and get a reasonable out-of-the-box experience. This comes from a couple things. Go compiles to a single static library so you don't have to worry about having dozens of "the right" library installed on your machine. Grab the heka binary and run with it. This greatly eases our operations work as we have fewer dependency conflicts to deal with when we push t…
Interesting so its more of a ease of use then a performance issue ? The numbers you quotes for performance seemed impressive.
We needed performance as well as simplicity.
We started by extending logstash, but our needs were more "we need a router" and logstash isn't meant to be a router.
Statically linking the world isn't trivial. For our existing Python code bases - how are you going to deal with third party libraries from PyPI?
Come by on #heka on irc.mozilla.org, we're kicking around in there.