Splunk Search

splunk search, token issue

yohhpark
Path Finder

trying to set a token where system_id shows ABC1, ABC1-a, ABC10, ABC10-a and so on.

 

when I set the token for that system_id as ABC1* to return all the ABC1 and ABC1-a and so on, it also returns the ABC10, and ABC10-a and so on. BUt obvisouly if I just do ABC10* it will return the right result.

the first portion is the problem. hope my question makes sense.

 

Labels (1)
Tags (2)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

That's the nature of wildcards - they're *wild* and sometimes match more than is desired.

The workaround is to tell Splunk what not to match, using the NOT operator and some other pattern, or use the regex command to filter using a more precise regular expression.

index=test control_id=AC-2*
| regex control_id="AC-2[a-z]?"

This query first reads all events where the control_id field starts with "AC-2".  This is similar to the existing behavior.  The regex command keeps only the events where the control_id field contains "AC-2" followed by an optional single letter.

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

View solution in original post

0 Karma

yohhpark
Path Finder

for example

index=test
|search control_id=AC-2*

this would give me AC-2, AC-2a, AC-20a, AC-22b, and so on.

I just want AC-2, AC-2a and not the tenth digit of 2s.

0 Karma

richgalloway
SplunkTrust
SplunkTrust

That's the nature of wildcards - they're *wild* and sometimes match more than is desired.

The workaround is to tell Splunk what not to match, using the NOT operator and some other pattern, or use the regex command to filter using a more precise regular expression.

index=test control_id=AC-2*
| regex control_id="AC-2[a-z]?"

This query first reads all events where the control_id field starts with "AC-2".  This is similar to the existing behavior.  The regex command keeps only the events where the control_id field contains "AC-2" followed by an optional single letter.

---
If this reply helps you, Karma would be appreciated.
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!

Splunk Auto Ingestion Parallel Pipeline Scaling

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

Best Practices: Splunk auto adjust pipeline queue

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

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...