Getting Data In

EXTRACT source field in props.conf has 'period'

Dworsnop
Path Finder

Hi all,

I've been trying to get an EXTRACT to work in a TA that someone has made for me and after much searching I have narrowed the problem down to the fact that the source field is "model.name". According to the props.conf docs, the source must be alphanumerical or an underscore, the docs also say that the source cannot be derived from a filed alias etc.

 

[mysourcetype]

...

EXTRACT-CIM_category = ^(?<category>.*):: in model.name

 

What is the best way therefore, to perform the regex extraction at search time on that field if I can't alias it? The docs say it can come from an preceding EXTRACT but what would the syntax be to rename the field to something like "model_name"? And how would this work because surely my source is always going to have the period in, which is incompatible with EXTRACT?

Many thanks in advance.

Labels (1)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

Have you tried not using the IN keyword and matching against _raw?  You may need to modify the regex for it work against _raw.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

Have you tried not using the IN keyword and matching against _raw?  You may need to modify the regex for it work against _raw.

---
If this reply helps you, Karma would be appreciated.

Dworsnop
Path Finder

Thanks @richgalloway that's worked!

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Introducing Splunk 10.0: Smarter, Faster, and More Powerful Than Ever

Now On Demand Whether you're managing complex deployments or looking to future-proof your data ...

Community Content Calendar, September edition

Welcome to another insightful post from our Community Content Calendar! We're thrilled to continue bringing ...