Splunk Dev

StreamingCommand Inappropriately Removes Leading Spaces

malvidin
Communicator

I can find a way to get results from a StreamingCommand to retain leading spaces. It doesn't matter if the field was fine before the app, it is gone afterward. Or even if the field wasn't processed by the command.

 

| makeresults
| eval test1 = "  "
| eval test2 = urldecode("%20%20")
| eval ok_here = if(test1==test2 AND len(test1) == 2, "true", "false")
| eval value_for_command = "nothing_special"
| customstreamingcommand field=value_for_command
| eval still_ok_here = if(test1==test2 AND len(test1) == 2, "true", "false")

In this simple case, "still_ok_here"  is false, but the same test was true before the command.

 

 

Labels (1)
0 Karma

malvidin
Communicator

I found a solution, but the problem may not be with the SDK. The SDK reads the data passed from the search command, but Splunk strips the data when passed back to Splunk.

The workaround is to modify the SDK 'splunklib.searchcommands' CSV dialect to pass the data back with csv.QUOTE_ALL in internals.py. Although this is not recommended by Splunk, it is likely preferable to modifying other Splunk internals.

malvidin
Communicator

csv.QUOTE_NONNUMERIC also works, with potentially less overhead that csv.QUOTE_ALL

Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...