Alerting

Custom Fields in Raw Results of Scheduled Search

mpetteys
New Member

We recently upgraded our Splunk app from 3.4.14 to 4.2.1. I have a custom script called from a scheduled search which reads the raw results in the CSV format. I am still testing but it appears that in the older version, custom fields (as parsed by props.conf and transforms.conf) were included as columns in the CSV. In the new version, they are not being populated in the raw results. Any suggestions on howto get the custom fields to be included in the raw results.

Tags (1)
0 Karma
1 Solution

BobM
Builder

Newer versions of splunk have been optimised to not extract or create fields that are not needed. This makes it more efficient but has the drawback you mention.

You can tell splunk to add them back in using the fields command. Either mention only the fields you need or load them all with :

yoursearch | fields + *

View solution in original post

BobM
Builder

Newer versions of splunk have been optimised to not extract or create fields that are not needed. This makes it more efficient but has the drawback you mention.

You can tell splunk to add them back in using the fields command. Either mention only the fields you need or load them all with :

yoursearch | fields + *
Get Updates on the Splunk Community!

Detecting Remote Code Executions With the Splunk Threat Research Team

WATCH NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If exploited, ...

Enter the Splunk Community Dashboard Challenge for Your Chance to Win!

The Splunk Community Dashboard Challenge is underway! This is your chance to showcase your skills in creating ...

.conf24 | Session Scheduler is Live!!

.conf24 is happening June 11 - 14 in Las Vegas, and we are thrilled to announce that the conference catalog ...