Getting Data In

Convert timestamps in transforms.conf?

holtb
Explorer

I'm new to this wonderful app, so pardon my inexperience if this is easy...I have a very long search string, but I'd like to have these values created automatically on index. How could I convert this set of converts and calculations into a transform?

source="/sge/default/default/common/accounting" 
| eval "Wait Time"=start_time-submit_time 
| eval "Run Time"=end_time-start_time 
| eval "Submit Time"=strftime(submit_time,"%Y %b %d %H:%M:%S") 
| eval "Start Time"=strftime(start_time,"%Y %b %d %H:%M:%S") 
| eval "End Time"=strftime(end_time,"%Y %b %d %H:%M:%S") 
| table uid job_name project qname "Submit Time" wait_time "Start Time" "End Time" run_time failed

I tried doing it this way to no avail:

[accttimeconvert]
eval "Wait Time"=start_time-submit_time
eval "Run Time"=end_time-start_time
eval "Submit Time"=strftime(submit_time, "%Y/%m/%d %H:%M:%S")
eval "Start Time"=strftime(start_time, "%Y/%m/%d %H:%M:%S")
eval "End Time"=strftime(end_time, "%Y/%m/%d %H:%M:%S")
1 Solution

dwaddle
SplunkTrust
SplunkTrust

This feature does not exist as of Splunk 4.3. Today, your best option is a macro that implements your series of eval operations.

There are rumours that the next major release of Splunk will support a feature quite similar to this. But, of course, the exact feature content of the next release is always subject to change. I would recommend keeping an eye out.

I think one thing to point out is that you don't necessarily want this done at index time, but rather at search time. The search-time late binding of field names to values is one of Splunk's strengths.

View solution in original post

dwaddle
SplunkTrust
SplunkTrust

This feature does not exist as of Splunk 4.3. Today, your best option is a macro that implements your series of eval operations.

There are rumours that the next major release of Splunk will support a feature quite similar to this. But, of course, the exact feature content of the next release is always subject to change. I would recommend keeping an eye out.

I think one thing to point out is that you don't necessarily want this done at index time, but rather at search time. The search-time late binding of field names to values is one of Splunk's strengths.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...