Getting Data In

Why is my EVAL configuration in props.conf on the Search Head not processing?

Communicator

I'm working with data that is being sent from a universal forwarder (UF) on the server. I do an INDEXED_EXTRACTION in the props.conf on the universal forwarder. When I search for the data on the search head (SH) it is put into the correct fields. I also have EVALs in the props.conf on the SH. What I don't see is the EVALs processed. This EVALS were processed in my standalone dev laptop, but not in the distributed environment. Do I need to move the EVALs to the UF?

0 Karma
1 Solution

Communicator

There are days. I had a meeting with the rest of the team and my issue was due to our distributed environment. The TA got pushed to the UF, but not to the SH. Once it was pushed to the SH, the problem resolved itself.

View solution in original post

0 Karma

Communicator

There are days. I had a meeting with the rest of the team and my issue was due to our distributed environment. The TA got pushed to the UF, but not to the SH. Once it was pushed to the SH, the problem resolved itself.

View solution in original post

0 Karma

SplunkTrust
SplunkTrust

Do post your relevant configuration, e.g. the props.conf defining the eval, some sample events, the searches you are running, etc.

0 Karma

Revered Legend

No, the EVAL (calculated fields) are search time field extraction and should be on SH. Can you check if those EVAL have sharing permissions Global and allows read to your user role (or everyone)?

0 Karma

Communicator

The sharing permission is global. The permissions are everyone:read, admin:write, and power:write.

0 Karma

SplunkTrust
SplunkTrust

what is the full path to file for this particular props.conf?
how your distributed environment looks like?
try and place the props.conf on the indexer as well.
hope it helps

0 Karma
State of Splunk Careers

Access the Splunk Careers Report to see real data that shows how Splunk mastery increases your value and job satisfaction.

Find out what your skills are worth!