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 (1)
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
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...