Splunk Search

Search based on transformation field

benjiminhugh
Explorer

I came across a very strange problem:
I have a transformation field:
[record]
FORMAT = event_type::Record_DVR dvr_start_time::$1 dvr_end_time::$2 dvr_sid::$3 dvr_freq::$4
REGEX = RecordingManager.record(LocatorRecSpec<(\w{3} \w{3} \d{2} \d{2}:\d{2}:\d{2} EST\d+EDT \d{4}) to (\w{3} \w{3} \d{2} \d{2}:\d{2}:\d{2} EST\d+EDT \d{4}) OcapLocator[SId=([-|\d]) freq=([-|\d]) prog#=([-|\d]) ([\d|\w])]>)

And a search:
sourcetype=Message event_type=Record_DVR

This is doesn't work.
However If i change
event_type::Record

and
event_type=Record
It can work.
if I change both to Record_Dvr
still doesn't work
if change to record,
it works again!
I try a lot of ways, but the result is also very strange.

Tags (2)
0 Karma
1 Solution

Ayn
Legend

The behaviour you are seeing is very likely related to what is described in this blog post: http://blogs.splunk.com/2011/10/07/cannot-search-based-on-an-extracted-field/

The blog post really says it all so I won't say more than that 🙂

View solution in original post

Ayn
Legend

The behaviour you are seeing is very likely related to what is described in this blog post: http://blogs.splunk.com/2011/10/07/cannot-search-based-on-an-extracted-field/

The blog post really says it all so I won't say more than that 🙂

Get Updates on the Splunk Community!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...