Is it possible to start the LogstreamerInput without catching up old logs?

In my use case oldest_duration is not enough because the log is constantly
being updated. The issue this causes is that parsing large log file
attempts to inject too many messages when heka first starts up. I realize
that we will end up loosing messages this way, but as it stands its very
hard to deploy (ie: we have to rotate the logs manually, then start heka).

Ideally what I do want is to parse all our logs, but I can't do this on a
production machine anyway. What I would rather do is have heka start fresh
each time when in production.

Thanks!
_______________________________________________
Heka mailing list
[email protected]
https://mail.mozilla.org/listinfo/heka

Reply via email to