Splunk Search

Fields with '=' as value stored in summary index are not extracted

darshan
Observer

I am storing a certain dataset in summary index which has some events with fields where the values are '=' or '=='. When searched, these events does not such fields. 

I managed to replicate this by doing this,

| makeresults 
| eval testval1 = "="
| eval testval2 = "=="
| eval testval3 = "-"
| eval testval4 = "--"
| eval testval5 = "*"
| eval testval6 = "/"
| table testval*
| summaryindex index="a_summary_index" name="testval"
which returns,
testval1testval2testval3testval4testval5testval6testval7testval8
===-

--

*/+++
 
index="a_summary_index" source="testval" 
| table testval*

 returns,

testval1testval2testval3testval4testval5testval6testval7testval8
  ---*/+++

 

(where the testval1 and testval2 are null). The raw event looks like this,

 

 

testval1="=", testval2="==", testval3="-", testval4="--", testval5="*", testval6="/", testval7="+", testval8="++"

 

 

The sourcetype is by default (as all other configurations) is stash.

Field extractions configuration is,

 

[stash_extract]
DELIMS = ",", "="
CAN_OPTIMIZE = false
MV_ADD = true
CLEAN_KEYS = false

 

I was wondering if there will be any implications on other search features if the above stanza is modified (since this is default configuration). Any feedbacks or suggestions are much appreciated.

Labels (2)
0 Karma
Get Updates on the Splunk Community!

Demo Day: Strengthen Your SOC with Splunk Enterprise Security 8.1

Today’s threat landscape is more complex than ever. Security operation centers (SOCs) are overwhelmed with ...

Dashboards: Hiding charts while search is being executed and other uses for tokens

There are a couple of features of SimpleXML / Classic dashboards that can be used to enhance the user ...

Splunk Observability Cloud's AI Assistant in Action Series: Explaining Metrics and ...

This is the fourth post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how ...