Getting Data In

Props.conf extractions

JoshuaJohn
Contributor

Any reason why my statement for props.conf isn't showing up as an extracted field?

EXTRACT-kls_error = (?(kls_error_*)\w+)

When I use just the rex in a search it gets the exact info that I need but when I am trying to create an extracted field it cannot

0 Karma
1 Solution

diogofgm
SplunkTrust
SplunkTrust

I believe you are missing group name like MuS suggested. Try this

EXTRACT-kls_error = (?<kls_error>kls\_error\_[\w]+)
------------
Hope I was able to help you. If so, some karma would be appreciated.

View solution in original post

diogofgm
SplunkTrust
SplunkTrust

I believe you are missing group name like MuS suggested. Try this

EXTRACT-kls_error = (?<kls_error>kls\_error\_[\w]+)
------------
Hope I was able to help you. If so, some karma would be appreciated.

skoelpin
SplunkTrust
SplunkTrust

@diogofgm is correct, you need to put <NAME> in your expression

For troubleshooting, you could try the extraction via rex in the search bar to test it and see if it works

... | rex (?<kls_error>kls\_error\_[\w]+)

0 Karma

MuS
SplunkTrust
SplunkTrust

Does it work if you run it in an ad-hoc search and is it just the format or are you missing a capturing group name?

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...