Otis Gospodnetić

@rabbitstack Do you have a sample of Go stack traces that are not getting parsed that you could include here?

Any luck with this @madsbredholt ?

@madsbredholt can we assume this is no longer an issue for you?

> But as more logagent slows down the consumption of disk space will grow and might hit the storage limit. Right. But I think that should/could be addressed separately by...

Looks useful at first glance. One may want to know the exact time window from which these aggregations were derived (so 'from' and 'to' timestamps may need to be tracked...

Seems juicy, will digest (btw should we move this to #43?). Performance: Have you compared before/after performance with ~equivalent configs to see if these modifications change CPU or memory footprint,...

@erik-stephens @megastef: - how would these stages be connected together? with queues? (sorry if this is an ignorant Node.js question) - what happens when one stage is much slower than...

Running multiple Logagent instances for multiple pipelines doesn't sound great to me from the operational perspective: - each JS VM has some overhead - starting Logagent may require sudo, etc....

gentle nudge @erik-stephens. We are hoping to nail down the direction ASAP and get a proper release before Santa comes to town.

This is a good place to discuss. Maybe you can submit a PR?