Splunk Search

My eval statement works in the Search App, but why does it not work when it is created via Settings, Fields, Calculated Field or via props.conf?

lyanta
Explorer

I'm able to create the following calculated field in the Search app.

.... | eval KCQueueDuration = (strptime(KCQStartDate." ".KCQStartTime, "%Y-%m-%d %H:%M:%S")) - (strptime(KCQEndDate." ".KCQEndTime, "%Y-%m-%d %H:%M:%S"))

However, I'm not able to get it to work when I create this field using the Splunk Web App (Settings->Fields->Calculated Fields) or editing the props.conf file. The field doesn't show up in the list of interesting fields, when I just search for all events for the source type. If I use this process to create a calculated field that just contains 1 of the strptime functions, it appears in the list of interesting fields.

Below is an example of the event data.
KCUID=905252z911311o,KCQStartDate=2016-01-06,KCQStartTime=15:19:46,KCQEndDate=2016-01-06,KCQEndTime=15:19:48

I couldn't find anything indicating that this expression is invalid in props.conf. Is this a known limitation of calculated fields in props.conf?

Tags (1)
0 Karma
1 Solution

sundareshr
Legend

I just tried this and it worked for me

EVAL-KCQueueDuration = (strptime(KCQStartDate." ".KCQStartTime, "%Y-%m-%d %H:%M:%S") - strptime(KCQEndDate." ".KCQEndTime, "%Y-%m-%d %H:%M:%S"))

View solution in original post

0 Karma

sundareshr
Legend

I just tried this and it worked for me

EVAL-KCQueueDuration = (strptime(KCQStartDate." ".KCQStartTime, "%Y-%m-%d %H:%M:%S") - strptime(KCQEndDate." ".KCQEndTime, "%Y-%m-%d %H:%M:%S"))
0 Karma

lyanta
Explorer

I tried your expression, and it also worked for me. It was one of the expression permutations I didn't think of trying.

Thanks for your help resolving this issue.

0 Karma

lguinn2
Legend

Perhaps it is a permissions problem? In which app did you create the calculated field and what are its permissions?

0 Karma

aljohnson_splun
Splunk Employee
Splunk Employee

Most likely its an ordering-of-the-knowledge-objects issue. Are any of the fields in your calculated field coming from an alias or lookup?

lyanta
Explorer

The fields in the calculated field expression are not alias or lookup fields. If I create a calculated field that just contains: strptime(KCQStartDate." ".KCQStartTime, "%Y-%m-%d %H:%M:%S"), it works. Likewise, it works if I create a calculated field with just strptime(KCQEndDate." ".KCQEndTime, "%Y-%m-%d %H:%M:%S"), it works.

The calculated field doesn't work when I tried to combine the 2 expressions to calculate a duration value.

0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...

What’s New in Splunk Security Essentials 3.8.0?

Splunk Security Essentials (SSE) is an app that can amplify the power of your existing Splunk Cloud Platform, ...