Splunk Enterprise Security
Highlighted

How to reference a token name with spaces in it for notable event action? (ES Correlation Searches)

Influencer

I'm working on creating new notable events in Enterprise Security. In the notable event alert action, I'm trying to add field values to the title so that it's easier for analysts to differentiate alerts on the Incident Review dashboard. I've noticed that when the field name does not contain spaces, I can just reference the field name using its token, e.g. Excessive failed logins from $src_ip$, and it works fine. The notable event will pop into the Incident Review dashboard with the expected title of, "Excessive failed logins from 123.456.789.0"

However, some of my searches have renames at the end, like rename src_ip as "Source IP". I can't seem to get the Incident Review dashboard to display the field value when the field name contains spaces. What's the correct syntax to reference a token where the field name contains spaces in it?

An obvious workaround would be to remove the renames so that none of the field names contain spaces, but if referencing them with spaces is possible, I would like to know how. I was unable to find an answer in the documentation or online.

0 Karma
Highlighted

Re: How to reference a token name with spaces in it for notable event action? (ES Correlation Searches)

Splunk Employee
Splunk Employee

I'd suggest removing the renames and then use the incident review settings page to provide user-facing names for the custom fields. http://docs.splunk.com/Documentation/ES/5.0.0/Admin/Customizenotables#Add_a_field_to_the_notable_eve...

View solution in original post

0 Karma
Highlighted

Re: How to reference a token name with spaces in it for notable event action? (ES Correlation Searches)

Influencer

Accepted as this is what I ended up doing.

0 Karma
Highlighted

Re: How to reference a token name with spaces in it for notable event action? (ES Correlation Searches)

Splunk Employee
Splunk Employee

Sorry I didn't have an SPL workaround for you, mason 😉

0 Karma