Alerting

When adding alert suppression fields with spaces in them should we use quotes around the field name?

abroglesc
Explorer

Let's say we have an alert which has a few field like:

 

| search <INSERT_RANDOM_BASE_QUERY>
| table src_ip, _time, dest_ip
| rename _time as "Time", src_ip as "Source IP", dest_ip as "Destination IP"

 

And we want to suppress on "Source IP" and "Destination IP" being the same. Should our suppress fields look like:

 

alert.suppress.fields = "Source IP","Destination IP"

 

Or:

 

alert.suppress.fields = Source IP,Destination IP

 

 ?

Labels (1)

gcusello
SplunkTrust
SplunkTrust

Hi @abroglesc,

at first, as @richgalloway said, if you have spaces in a field name, you have to use quotes, and in my experience it isn't a good idea to use spaces in field names, eventually you could rename them at the end of your search in column displaying.

Anyway, Taking always "Source IP" when present or "Destination IP" if the first isn't present, you could use eval coalesce:

| eval IP=coalesce("Source IP","Destination IP")

Ciao.

Giuseppe

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Use quotation marks.  Without them you have 3 fields, one of which is repeated.

---
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!

At .conf26, Don’t Just See What’s Next. Help Shape It at Innovation Labs.

Long before a new capability reaches the keynote stage, it begins as an idea waiting to be tested. At ...

Forwarder Topology Guidance: Intermediate HF vs Intermediate UF

Why Universal Forwarders Should Not Be Used as Intermediate Forwarders A practical Splunk forwarding topology ...

Data Management Digest – August 2026

Data Management Digest   Welcome to the August 2026 edition of Data Management Digest! August was a big month ...