Splunk Search

Why is MV_ADD=true extracting everything twice and producing duplicates in my search results?

ejharts2015
Communicator

My Event:

Directory: /var/tmp/.X11-unix
  Mtime    : 2015-01-06 06:26:36 +0000        | 2016-01-04 15:31:39 +0000
  Ctime    : 2015-01-06 06:26:36 +0000        | 2016-01-04 15:31:39 +0000
  Inode    : 12                               | 393217

Props.conf (the relevant stuff):

source::.../aide.log]
sourcetype = aide

#Configuration for the new sourcetype
[aide]
pulldown_type = TRUE
SHOULD_LINEMERGE = TRUE
MAX_EVENTS  = 1000
KV_MODE = none
DATETIME_CONFIG =  NONE
MAX_TIMESTAMP_LOOKAHEAD = 0 
REPORT-extract_changes = extract_changes

Transforms:

#Extract each field pair from detailed message:
[extract_changes]
REGEX = ^\s\s(\w+)\s*:\s([^|]+)\|\s([^\n]+)\n*
FORMAT = value::$1 old_value::$2 new_value::$3
MV_ADD=true

These give me twice the results I would expect, can't figure out why:
alt text

1 Solution

ejharts2015
Communicator

I feel kind of stupid now, but the issue was with my original search, I had been using:

Wrong Search:

index="aide_index" | extract reload=t | search "Socket" | table _time _raw, value, old_value, new_value

Correct Search:

index="aide_index" | search "Socket" | table _time _raw, value, old_value, new_value

I forgot to remove extract reload=t after refreshing the new transforms.conf file... so it was parsing all those fields twice.

View solution in original post

0 Karma

richgalloway
SplunkTrust
SplunkTrust

What is the search you are using to produce the results?

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

ejharts2015
Communicator

I feel kind of stupid now, but the issue was with my original search, I had been using:

Wrong Search:

index="aide_index" | extract reload=t | search "Socket" | table _time _raw, value, old_value, new_value

Correct Search:

index="aide_index" | search "Socket" | table _time _raw, value, old_value, new_value

I forgot to remove extract reload=t after refreshing the new transforms.conf file... so it was parsing all those fields twice.

0 Karma
Get Updates on the Splunk Community!

Updated Team Landing Page in Splunk Observability

We’re making some changes to the team landing page in Splunk Observability, based on your feedback. The ...

New! Splunk Observability Search Enhancements for Splunk APM Services/Traces and ...

Regardless of where you are in Splunk Observability, you can search for relevant APM targets including service ...

Webinar Recap | Revolutionizing IT Operations: The Transformative Power of AI and ML ...

The Transformative Power of AI and ML in Enhancing Observability   In the realm of IT operations, the ...