Splunk Search

Subsearch using loadjob not working

jamesvz84
Communicator

I try the following search:

| loadjob savedsearch="admin:app1:app1_view1" | fields hostname

This returns "hostname05" as a result.

I then try to embed this as a subsearch:

| loadjob savedsearch="admin:winapp:perfmon_results" | search object=Processor counter="% Processor Time" [| loadjob savedsearch="admin:app1:app1_view1" | fields hostname]

This return no results, however, if I do this:

   | loadjob savedsearch="admin:winapp:perfmon_results" | search object=Processor counter="% Processor Time" hostname="hostname05"

It returns many results. Why is the subsearch not working? Do I need to call loadjob differently? I've tried with and without the initial pipe.

Tags (2)
0 Karma

sansay
Contributor

Subsearch calling loadjob does not work. You get "Error in 'SearchOperator:loadjob': Cannot find artifacts for savedsearch_ident 'user:app:saved_search_name'.
Here is the query I used:
| loadjob savedsearch="user:app:saved_search_name_1" | append [| loadjob savedsearch="user:app:saved_search_name_2"]

0 Karma

somesoni2
Revered Legend

Try this.

| loadjob savedsearch="admin:winapp:perfmon_results" | search object=Processor counter="% Processor Time" [| loadjob savedsearch="admin:app1:app1_view1" | fields hostname | format "" "" "" "" "" ""]
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

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...