2 ms·

Very 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 c

by themgt 14y ago

Very 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/index.html 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. https://github.com/mozilla-services/circus https://github.com/mozilla-services/circus

nonsequitarian 14y ago
Heka and Circus have very different goals. Heka is about generic data gathering, processing, and routing. Circus is about task and process monitoring and management. There's some overlap in that Circus needs to gather and process a bit of data to do its job, and it would certainly be possible to use Heka as a part of that, but we're not doing so. We'll probably use Circus to manage at least a few of our `hekad` processes, though.