Other Usage

Why sistats doesn't work after lookup?

maayan
Path Finder

Hi,

I wrote a report that merge the result with lookup table to add fields (like machineName). the lookup table contain the field,source.
then, I do sistats as the following:

index=....search query... 
| lookup lk_table_name.csv source AS source
| sistats values(*) as * by TimeStamp,source

if I write sistats command after the lookup command the new fields from the lookup table disappear. 

if i write the sistats before the lookup command everything is ok but then i have other problem when i try to parse the summary index:
index=summary search_name="query_SummaryIndex_Main"
| stats values(*) as * by TimeStamp,source

what should i do? why sistats doesnt work after lookup?


thanks,
Maayan

Labels (2)
0 Karma
1 Solution

maayan
Path Finder

stupid solution but works- write stats before and after lookup:

| stats values(*) as * by TimeStamp,source

| lookup mylookup_table.csv source AS source

| stats values(*) as * by TimeStamp,source

View solution in original post

0 Karma

maayan
Path Finder

stupid solution but works- write stats before and after lookup:

| stats values(*) as * by TimeStamp,source

| lookup mylookup_table.csv source AS source

| stats values(*) as * by TimeStamp,source

0 Karma
Get Updates on the Splunk Community!

Earn a $35 Gift Card for Answering our Splunk Admins & App Developer Survey

Survey for Splunk Admins and App Developers is open now! | Earn a $35 gift card!      Hello there,  Splunk ...

Continuing Innovation & New Integrations Unlock Full Stack Observability For Your ...

You’ve probably heard the latest about AppDynamics joining the Splunk Observability portfolio, deepening our ...

Monitoring Amazon Elastic Kubernetes Service (EKS)

As we’ve seen, integrating Kubernetes environments with Splunk Observability Cloud is a quick and easy way to ...