Splunk Search

Need help on appendcols _time issue

jip31
Motivator

hello

When I run the search below, its gives me "4" in results at the _time span = 11h

 

`index`  earliest=@d+7h latest=@d+19h 
| bin _time span=1h 
 | stats dc(sign_id) as "Signal inc" by _time

 

 

jip31_0-1648036551795.png

But

 

`index` earliest=@d+7h latest=@d+19h 
| stats avg(citrix) as citrix by sam _time 
| eval PbPerf=if(citrix>200,1,0) 
| search PbPerf > 0 
| bin _time span=1h 
| stats dc(sam) as "W" by _time 
| appendcols 
    [ search `index` earliest=@d+7h latest=@d+19h 
    | bin _time span=1h 
    | stats count as W by _time] 
| appendcols 
    [ search `index` earliest=@d+7h latest=@d+19h 
    | bin _time span=1h 
    | stats dc(signaler_id) as "Signal inc" by _time ] 
| appendcols 
    [ search `index` earliest=@d+7h latest=@d+19h 
    | bin _time span=1h 
    | stats count as "TEA" by _time] 
| fillnull value=0 
| eval time=strftime(_time,"%H:%M") 
| sort time 
| fields - _time _span _origtime 
| transpose 0 header_field=time column_name=KPI 
| sort + KPI

 

 my problem is that I must use this search with other search in order to display results by _time span

So when I execute this search with other searches, the results for th primary search is always 4 but it's display the _time span = 11h but for the _time span= 8h!!!

whats is the problem please? 

Tags (2)
0 Karma
1 Solution

ITWhisperer
SplunkTrust
SplunkTrust

As you know, appendcols does not correlate the values in the rows, it just adds data rows in the order returned i.e. the first row returned will be added to the first row of the current set, this means the results can get out of line. Try using timechart which will generate the "missing" time periods.

`index` earliest=@d+7h latest=@d+19h 
| stats avg(citrix) as citrix by sam _time 
| eval PbPerf=if(citrix>200,1,0) 
| search PbPerf > 0 
| timechart span=1h dc(sam) as "W"
| appendcols 
    [ search `index` earliest=@d+7h latest=@d+19h 
    | timechart span=1h count as W] 
| appendcols 
    [ search `index` earliest=@d+7h latest=@d+19h 
    | timechart span=1h dc(signaler_id) as "Signal inc" ] 
| appendcols 
    [ search `index` earliest=@d+7h latest=@d+19h 
    | timechart span=1h count as "TEA"] 
| fillnull value=0 
| eval time=strftime(_time,"%H:%M") 
| sort time 
| fields - _time _span _origtime 
| transpose 0 header_field=time column_name=KPI 
| sort + KPI

View solution in original post

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

As you know, appendcols does not correlate the values in the rows, it just adds data rows in the order returned i.e. the first row returned will be added to the first row of the current set, this means the results can get out of line. Try using timechart which will generate the "missing" time periods.

`index` earliest=@d+7h latest=@d+19h 
| stats avg(citrix) as citrix by sam _time 
| eval PbPerf=if(citrix>200,1,0) 
| search PbPerf > 0 
| timechart span=1h dc(sam) as "W"
| appendcols 
    [ search `index` earliest=@d+7h latest=@d+19h 
    | timechart span=1h count as W] 
| appendcols 
    [ search `index` earliest=@d+7h latest=@d+19h 
    | timechart span=1h dc(signaler_id) as "Signal inc" ] 
| appendcols 
    [ search `index` earliest=@d+7h latest=@d+19h 
    | timechart span=1h count as "TEA"] 
| fillnull value=0 
| eval time=strftime(_time,"%H:%M") 
| sort time 
| fields - _time _span _origtime 
| transpose 0 header_field=time column_name=KPI 
| sort + KPI
0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...