for log pipelines, why do grok capture groups need...
# support
c
for log pipelines, why do grok capture groups need to have a
p
before them? e.g.
Copy code
%{YEAR}-%{MONTHNUM}-%{MONTHDAY} %{TIME} %{LOGLEVEL:level} %{NUMBER} --- \[.*\] (?P<method>.*) :
works, but
Copy code
%{YEAR}-%{MONTHNUM}-%{MONTHDAY} %{TIME} %{LOGLEVEL:level} %{NUMBER} --- \[.*\] (?<method>.*) :
doesn't. Grok debugger only accepts the second syntax, so I'm curious why the first syntax is used in Signoz.
same for Regex. I couldn't find anything else online that uses the "P" as part of their capturing groups
n
Yeah it uses the re2 syntax https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/stanza/docs/operators/regex_parser.md grok supports regex as well, so
(?P<method>.*)
is the regex in your grok pattern you can change it to grok