Fabian Stäber

Hi, sorry for the late reply. Currently `grok_exporter` with special characters works only with UTF-8 encoding (because of [this](https://github.com/fstab/grok_exporter/blob/118f9f6a6c60116eda808b7ebb105fdb6a73f7a8/oniguruma/oniguruma.go#L33)). If you use UTF-8 it should work. If you use another...

I think it sounds like a good idea. `grok_exporter` was originally made for plain text log lines, but more and more people are using it for Json, so it would...

Please tell me you the `input` section in your `grok_config.yaml` is configured.

This is weird. If you configure `readall: false`, `grok_exporter` starts reading from the end of the log file. It should not matter if the file has 10,000 lines or 100...

:+1: yes, I think it's just example values. As it's defined in the OpenMetrics spec, and in the OpenTelemetry spec, we should support this. It's maybe ok to ignore the...

Thanks a lot @dhoard for analyzing this!!! I guess adding a label like `mbean_name` in case there is a name conflict is the best way to solve this. Something like...

Please let me know when your branch is ready to review!

Can we add the extra label only to the metrics that have a name collision, rather than to all metrics? I think name collisions are rare, so most metrics won't...

I am confused. Is the problem conflicting metric names, or conflicting labels?

Thanks a lot for the example, that was helpful. I implemented a proposal how to solve this in #960. What do you think?