Also note I’ve changed your regex from .*W=(?P<writes>.*), to .*W=(?P<writes>\S*),.
If you use .*W=(?P<writes>.*),, you will overrun that field: regex101: build, test, and debug regex ... (I=9730, O=0, R=0, W=9730, U=0, E=0) will match anything after W= until the next comma: W=9730, U=
I assume you want to capture just the value after W, so searching for any non-space character (\S) is probably what you want in that case.
@dannykopping Thank you very much for your support. It is not easy to get any example for such calculations.
The mistake in the regex come from forum parser. I had troubles with escaping special characters here.
It had to be non greedy
`.W=(?P<writes>.?),`
Any way the unexpected unwrap went away but I got something new. No matter I use your or mine syntax.
pipeline error: 'SampleExtractionErr' for series: '{__error__="SampleExtractionErr", app="pentaho", filename="********/pdi.log", host="*******", job="integrator", level="WARN ", path="/************.kjb"}'. Use a label filter to intentionally skip this error. (e.g | __error__!="SampleExtractionErr"). To skip all potential errors you can match empty errors.(e.g __error__="") The label filter can also be specified after unwrap. (e.g | unwrap latency | __error__="" )
I know that not all lines include this match, co adding filter | __error__=""
should avoid that however grafana 7.3.7 claims that there is syntax error:unexpected |, expecting )
That would mean it is unsupported for my current version?
If i’ll make this : {container="etl-receipt-fobo-create"} |="Analytical log" | regexp "^(?s)(?P<event_time>\\S+\\s\\S+).\\s(?P<log_lvl>\\S+).*?in\\s(?P<created_time>\\d+\\.\\d+).*$"