All Apps and Add-ons

Splunk Machine Learning Toolkit: Prediction, merge searches, and timechart

singh3and12
Path Finder

Hi,
I am trying to do prediction using MLTK toolkit in Splunk, so preferably I am using forecasting series and algorithm as ARIMA to predict.
I have two searches which I want to merge and create a single output, which displays a timechart using Yaxis CPU_Load and on X axis Count of P2 incidents during that CPU_Load using Time. So I need to merge infra i.e CPU load w.r.t P2 incident and they are from 2 different indexes and then that search I will use in MLTK under Arima to predict.
Could you please help me out to correct the search we can merge them to get the expected result, I have already used append and join but didn't get the expected output.

Below is search 1:

index="xyz"  source_host="abc" search_name=search_update_acn_tier3_os_monitoring metric_label="Processor : CPU Load Average 15 Alert" | timechart max(metric_value) as "CPU_Load"  

Search 2:

index="defservice" impact="2 - High"  sourcetype=csv | timechart  count(incident) as "P2" 

The way I was merging it :

index="xyz"  source_host="abc" search_name=search_update_acn_tier3_os_monitoring metric_label="Processor : CPU Load Average 15 Alert" | timechart max(metric_value) as "CPU_Load"  |append [search index="defservice" impact="2 - High"  sourcetype=csv | timechart  count(incident) as "P2"]

Any correction to this would be appreciated... as when I run this one query is giving normalize value not the actual value as in statistics could it be modified to get the expected outcome.

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...