Custom Fields in Raw Results of Scheduled Search

[mpetteys]

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.

[BobM · Accepted solution]

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 + *