Difference between outputlookup and outputcsv

[splunkn]

Could anyone tell me the difference between outputlookup and outputcsv?

If there no differences, is there any specifications to use the above in various circumstances?

Regards,
Naga

[alacercogitatus · Accepted solution]

There is a major difference. outputlookup will use the defined transforms or the filename you give it and put the CSV file in the lookups folder of the current App context. You can use this lookup in other commands using the lookup command. Changes to the lookup are replicated on the SHC.

outputcsv just dumps the CSV to the file system in $SPLUNK_HOME/var/run/splunk/. You can't use it later, and changes are not replicated in a SHC.

http://docs.splunk.com/Documentation/Splunk/6.2.4/SearchReference/Outputcsv
http://docs.splunk.com/Documentation/Splunk/6.2.4/SearchReference/Outputlookup

[ejwade]

@alacercogitatusdo you know if Splunk has a cleanup/garbage collection for these CSVs, or do they live forever?

[JCISplunker]

Can you clarify "You can't use it later" comment for outputcsv command? The data is very much accessible through | inputcsv - I use this all the time.

[kasu_praveen]

Yes. we can access the results with |inputcsv command.

I guess the major differences are
1) Location where it stores
2) SHC replication

[alacercogitatus]

@splunkn, instead of giving me Karma points, use the Up arrow to vote on the answer. This does two things. 1) It won't take away your Karma and 2) shows others it was a valuable answer. Your points have been returned, but thanks!