Splunk Search

Why does inputlookup NOT fail to exclude rows?

cmille19
Engager

I'm trying to exclude known issues from a search by using a lookup of exclusions. Our Splunk admins lock down alert creation so I can't hard code these exclusions in the search itself which generates alerts however I can make use of lookups which I'm able to edit as needed. The search fails to exclude my list of exclusions and I still see rows for data for the excluded values. The field name DELGROUP is the same name as returned in output from source.
Is there something wrong with this search or is there a better to accomplish exclusions/overrides?

index=perfmon (sourcetype=perfmon:oracle OR sourcetype=perfmon:mssql) source="*ggs_hb_vw_perf_mon" NOT ([| inputlookup dba_lookup_Exclusions.csv  where (id=2) | fields exclude_name | rename exclude_name as DELGROUP]) DIFF>600 
0 Karma
1 Solution

cmille19
Engager

This my error, lookup name had a case error and was listed as

| inputlookup dba_lookup_exclusions.csv

and not

| inputlookup dba_lookup_Exclusions.csv

View solution in original post

0 Karma

cmille19
Engager

This my error, lookup name had a case error and was listed as

| inputlookup dba_lookup_exclusions.csv

and not

| inputlookup dba_lookup_Exclusions.csv

0 Karma

richgalloway
SplunkTrust
SplunkTrust

@cmille19 If your problem is resolved, please accept an answer to help future readers.

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

woodcock
Esteemed Legend

Try this:

index=perfmon AND (sourcetype=perfmon:oracle OR sourcetype=perfmon:mssql) AND source="*ggs_hb_vw_perf_mon" AND DIFF>600
NOT [|inputlookup dba_lookup_Exclusions.csv  | where id==2 | fields exclude_name | rename exclude_name AS DELGROUP]
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...