Fabian Stäber

Hi @cawamata, thanks for offering your help. I agree, it's time to get 1.0.0 done. There is no missing feature in my opinion, the only thing holding me back is...

grok_exporter should not need that much memory. Could you send me a few example log lines so I can reproduce this? Moreover, as you set `readall: true` grok_exporter will read...

`grok_exporter` is basically a tool for executing regular expressions (grok patterns are converted to regular expressions internally). Almost all of the CPU usage should come from evaluating the regular expressions....

Good point. Yes, with `readall: true` all initial lines will be in the buffer until they are processed. I could implement a limit to the buffer size. I didn't do...

> does this mean that once all the log lines are read, my memory consumption should come down to normal? yes > is implementing the feature of limiting buffer size...

Sure, that should not be a problem. I'll keep it in mind for the next release.

Unfortunately this is currently not possible. However, there is work in progress: `grok_exporter`'s templates support a `timestamp` function for converting a timestamp to a Unix timestamp (number of seconds since...

Here's an example of what I mean. Imagine you have the following log lines: ``` 2019-12-02 09:38:27 start serving request nr 12345. 2019-12-02 09:39:28 start serving request nr 12346. 2019-12-02...

Thanks a lot! This sounds like a valuable contribution. I'll look into the code in detail in the next couple of days.

Thanks for bringing this up. I'm in favor of option 1. Option 2 would mean that we introduce a feature that will not be available for Windows users, and I'd...