Splunk Search

How can I remove a events from a search table

vino06
New Member

Hi Guys,

Good Day!

Just want to ask on how can I remove YYYYMMDD HH24:MI:SS") event on my search table. Here is my search and the result.

index=nf_index source=/appl/in_house/batch/AS*
| multikv
| stats count by "ACCESS CODE"

alt text

Tags (1)
0 Karma
1 Solution

s2_splunk
Splunk Employee
Splunk Employee
index=nf_index source=/appl/in_house/batch/AS* 
 NOT "ACCESS CODE"="YYYYMMDD*"
| multikv 
| stats count by "ACCESS CODE"

Or you could fix your data onboarding and don't index those events, because it seems these values are the result of something that is parsed incorrectly.

View solution in original post

s2_splunk
Splunk Employee
Splunk Employee
index=nf_index source=/appl/in_house/batch/AS* 
 NOT "ACCESS CODE"="YYYYMMDD*"
| multikv 
| stats count by "ACCESS CODE"

Or you could fix your data onboarding and don't index those events, because it seems these values are the result of something that is parsed incorrectly.

rjthibod
Champion

You could try the simple boolean check of isint()

index=nf_index source=/appl/in_house/batch/AS*
| multikv 
| stats count by "ACCESS CODE"
| where isint("ACCESS CODE")
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...