Splunk Search

Issue adding a symbol after a field value

UMDTERPS
Communicator

The following previous splunk thread works fine:

https://community.splunk.com/t5/Archive/Insert-sign-for-each-result-in-a-specific-column/m-p/149167


| eval sensor = sensor + " %"
51%


However,  if the field name has a space, it does not work:

| eval "System Outlook" = "System Outlook" + " %"
System Outlook %

 

I'm assuming it needs some sort of backslash escaping? (I've tried a bunch of ways). I know I can just rename it without the space, but I want to keep the space.

Any ideas?

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

bowesmana
SplunkTrust
SplunkTrust

When using field names with non standard characters, you need to use single quotes on the right hand side of the eval statement, i.e.

| eval "System Outlook" = 'System Outlook' + " %"

 

View solution in original post

bowesmana
SplunkTrust
SplunkTrust

When using field names with non standard characters, you need to use single quotes on the right hand side of the eval statement, i.e.

| eval "System Outlook" = 'System Outlook' + " %"

 

UMDTERPS
Communicator

Perfect, that worked!

 

Thanks!😀

Tags (1)
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 ...