Fabian Stäber

One thing you can try is to create a single pattern that matches all cases. For example, if you have ```yaml - type: counter name: my_metric match: pattern1 ... ```...

This is weird, CPU usage should be constant. Did you see any increase in memory usage?

I tried to reproduce the behavior with your data, but something's wrong with the pattern you posted above: ``` [%{HTTPDATE:timestamp}] ``` Square brackets are special characters in regular expressions. If...

Just as a side note: I'm working on improving the built-in metrics to make it easier to see where `grok_exporter` spends processing time. This will be part of the next...

It looks like you are using a `gauge` metric with `323232` as a value. You could use a counter metric and `323232` as a label. For example, if you call...

`cumulative` is for `gauge` metrics, not for `counter` metrics. I'm not sure if I understand correctly what you want to do, but usually if you have two counters from to...

Yes, `pprof` is the right tool, but you need to add it to the source code and recompile `grok_exporter` in order to use it. If you do that, could you...

I'm building the Windows release on a Linux machine using `./hack/release.sh windows-amd64`. This will run the `fstab/grok_exporter-compiler-amd64` Docker image which contains a cross-compiler for creating the Windows executable. Alternatively, you...

Oh, sorry, copy-and-paste error. The latest image is `fstab/grok_exporter-compiler-amd64:v1.0.0.RC5`. The `v1.0.0-SNAPSHOT` version is wrong.

When I saw an error related to `v1.0.0-SNAPSHOT` I assumed it's the wrong tag causing the problem, but now I see that it's about Docker's new pull rate limit and...