Splunk Enterprise

Use eval field inside append search

mad_splunker
New Member

Hello Splunkers,

I am trying below query -

 

index=someindex cluster=gw uuid=gw98037234c6e51a48816016172b8a3c56
| eval api_uuid="gw"+reqid
| head 1
| append [search index=someindex cluster=api uuid=api_uuid]

 

Basically what I am trying is to get result from first search, evaluate new field from first search and add it as condition to second search. It is not working if I supply api_uuid field but If I replace uuid in append with actual computed value it is returning proper result. I have seen few people using join but dont want to use join as its expensive and comes with limit. Any solution to above query ?

Labels (1)
Tags (2)
0 Karma

mad_splunker
New Member

Nope not working

0 Karma

kamlesh_vaghela
SplunkTrust
SplunkTrust

@mad_splunker 

index=someindex cluster=api uuid=api_uuid [ search index=someindex cluster=gw uuid=gw98037234c6e51a48816016172b8a3c56 | eval uuid="gw"+reqid  | table uuid ]

 

Can you please try this? I have used different approach. 

 

thanks

KV

0 Karma
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...