Splunk Search

normalising duplicate multivalue field

ytl
Path Finder

so i have numerous field extractions in place. unfortunately due to the number of regex's there are some events that match two field extractions. the issue is that i have the same field name defined in both extractions.

this isn't a problem as splunk is nice enough to create a multivalue field for me automatically. it just so happens that the value of that field is the same for both entries!

is there a way i can reduce/normalise this so it doesn't show twice? (without reconstructing my regex's)

0 Karma
1 Solution

gkanapathy
Splunk Employee
Splunk Employee

There really isn't an easy way globally.

In general, you might look at:

  • Using app namespaces to control when particular extractions are performed. If some are only needed in certain contexts, then perhaps these contexts could be separated out into their own app to avoid this kind of conflict
  • Making the regexes more precise and/or combining multiple regexes into a single one that retrieves multiple fields

View solution in original post

0 Karma

gkanapathy
Splunk Employee
Splunk Employee

There really isn't an easy way globally.

In general, you might look at:

  • Using app namespaces to control when particular extractions are performed. If some are only needed in certain contexts, then perhaps these contexts could be separated out into their own app to avoid this kind of conflict
  • Making the regexes more precise and/or combining multiple regexes into a single one that retrieves multiple fields
0 Karma

ytl
Path Finder

oh well... back to restructuring my regex's i guess... just a thought, when i do a top on such a field - would it double count? cheers,

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...