Splunk Search
Highlighted

What are the regex equivalents of the wildcards ... and *?

Splunk Employee
Splunk Employee

In inputs.conf and props.conf, the wildcards ... and * are supported for use in the spec headers. What do they translate to in PCRE? This is useful to know because sometimes the resulting matches are confusing.

Tags (1)
Highlighted

Re: What are the regex equivalents of the wildcards ... and *?

Splunk Employee
Splunk Employee
  • ... (three periods) in source stanza headings is treated as .* in PCRE regex
  • * (asterisk) in source stanza headings is treated as [^/\\]* in PCRE regex
  • . (one period) in stanza headings is treated as \.
  • Note that all other PCRE syntax is also valid
  • Note that the expression must match the entire path. In regex terms, the expression has an implicit ^ at the beginning and an implicit $ at the end, and that must match the source value.

View solution in original post

Highlighted

Re: What are the regex equivalents of the wildcards ... and *?

Splunk Employee
Splunk Employee

BTW, a particular piece of PCRE regex that may be particularly useful is the prefix (?i), which indicates that the regex from that point on is case-insensitive. This should usually be used when trying to match Windows file paths, e.g., [source::(?i)...\\program files\\applogs\\*.log]

0 Karma
Highlighted

Re: What are the regex equivalents of the wildcards ... and *?

Super Champion

You may also find some of this helpful: