Fabian Stäber

I think it's best to approach this step by step. Let's first try to see the metric in Prometheus without any labels, and then see where we can go from...

If you really want to use the error message as a label value you can do it like this: ```yaml global: config_version: 2 input: type: file path: ./test.log readall: true...

Yes, it's compatible. There are no breaking changes between these Prometheus versions. Alerting rules have nothing to do with `grok_exporter` anyway, `grok_exporter` is only focused on providing metrics, but not...

Did you set the `:method` and `:scheme` headers in the push promise?

The push promise should contain the same headers that would normally be present in a request.

It depends on what exactly you want to achieve. One simple way is to use the `kubectl logs` command to print the logs to the stdout, and to pipe it...

In grok_exporter, you need to distinguish two names: * The names used in the grok pattern (like the name `cs_user_agent` in `%{NOTSPACE:cs_user_agent}`) are just used inside the `grok_exporter` config file,...

It seems that the content of your XML example got lost in the comment. Could you comment it again? The best way to comment an XML snippet on Github is...

This is because with the current version v0.2.5 the match must match the entire line, not just part of the line. If you change it to `'.*%{TIMESTAMP_ISO8601}.*'` it should work....

This sounds like a bug. It does not seem related to missing settings. The only thing that starts a thread is the built-in server https://github.com/fstab/promagent/blob/master/promagent-framework/promagent-internal/src/main/java/io/promagent/internal/BuiltInServer.java. If you start promagent without...