Splunk Enterprise

help on subsearch with join command

jip31
Motivator

hi

I need to improve the subsearch below

I explain : the piece of code in the subsearch count the number of core of the machine

So this count is always the same no matter the time

So I wonder if it would better to put these results in a csv lookup and to query the csv lookup instead to query on the index?

or is there some other tracks for improve this search?

Thanks

index=toto sourcetype=tutu type=* runq 
| fields host _time runq type 
| stats max(runq) as runq by host _time 
| join host 
    [ search index=toto sourcetype=tutu type=* 
    | fields host cpu_core
    | search host=1328 
    | stats max(cpu_core) as nbcore by host ] 
| eval Vel = (runq / nbcore) 
| eval _time = strftime(_time, "%d-%m-%y %H:%M:%S") 
| sort - _time 
| rename host as Host, _time as Heure 
| table Heure Host Vel 
| sort - Vel

 

 

Tags (1)
0 Karma

isoutamo
SplunkTrust
SplunkTrust

Hi

using lookup instead of query "static" values from index is almost always better/more efficient way.

There are many conf presentation which cover this issue. In most cases you should avoid to use join and instead use stats. Here is some links to those 

r. Ismo

0 Karma

jip31
Motivator

Hi, many thanks

Tags (1)
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!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...