<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: difference betwen output and outputnew in splunk lookup in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/difference-betwen-output-and-outputnew-in-splunk-lookup/m-p/112937#M29679</link>
    <description>&lt;P&gt;The answer to your two numbered questions is: Yes, &lt;CODE&gt;stats&lt;/CODE&gt; represents the field in the event, and &lt;CODE&gt;description&lt;/CODE&gt; will be the new field generated. The difference between &lt;CODE&gt;OUTPUT&lt;/CODE&gt; and &lt;CODE&gt;OUTPUTNEW&lt;/CODE&gt; is if the &lt;CODE&gt;description&lt;/CODE&gt; field already exists in your event, &lt;CODE&gt;OUTPUT&lt;/CODE&gt; will overwrite it and &lt;CODE&gt;OUTPUTNEW&lt;/CODE&gt; won't.&lt;/P&gt;

&lt;P&gt;As for the rest of it, my recommendations would be:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Give global permission to everything first, get everything to work, and then change the permissions and see what breaks.&lt;/LI&gt;
&lt;LI&gt;Make sure that &lt;CODE&gt;default&lt;/CODE&gt; is a valid sourcetype in your data (if it's a host, source or rule, the syntax is different, check &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Propsconf"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/Propsconf&lt;/A&gt; for details).&lt;/LI&gt;
&lt;LI&gt;I wonder whether the name &lt;CODE&gt;LOOKUP-test_lkup&lt;/CODE&gt; is confusing things. The string after &lt;CODE&gt;LOOKUP-&lt;/CODE&gt; is supposed to be a unique literal, and &lt;CODE&gt;test_lkup&lt;/CODE&gt; is used elsewhere for other things. Try &lt;CODE&gt;LOOKUP-random&lt;/CODE&gt; and see whether that helps.&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Good luck.&lt;/P&gt;</description>
    <pubDate>Fri, 05 Sep 2014 12:53:01 GMT</pubDate>
    <dc:creator>aweitzman</dc:creator>
    <dc:date>2014-09-05T12:53:01Z</dc:date>
    <item>
      <title>difference betwen output and outputnew in splunk lookup</title>
      <link>https://community.splunk.com/t5/Splunk-Search/difference-betwen-output-and-outputnew-in-splunk-lookup/m-p/112936#M29678</link>
      <description>&lt;P&gt;Could anyone please let me clear with the following basic questions?&lt;BR /&gt;
 1. What is the difference between output and outputnew in lookup?&lt;BR /&gt;
 2. lookup status_desc status OUTPUT description &lt;BR /&gt;
    Here status represent the field in events?&lt;BR /&gt;
    description is the new field going to be add based on status rite?&lt;/P&gt;

&lt;P&gt;And Im getting the following error while Im working with lookup&lt;BR /&gt;
"Could not find all of the specified destination fiels in the lookup table for conf '(?::){0}PerfmonMk*:*' and lookup table test_lkup"&lt;/P&gt;

&lt;P&gt;And initially I haven't give global permission to lookup. Will it cause any issue?&lt;BR /&gt;
Now I have removed all the things. Eventhough Im getting the error ??&lt;/P&gt;

&lt;P&gt;props.conf&lt;BR /&gt;
[default]&lt;BR /&gt;
LOOKUP-test_lkup = test_lkup sourcetype OUTPUT flag&lt;/P&gt;

&lt;P&gt;transforms.conf&lt;BR /&gt;
[test_lkup]&lt;BR /&gt;
filename = test_lkup.csv&lt;/P&gt;

&lt;P&gt;test_lkup.csv&lt;BR /&gt;
sourcetype,flag&lt;BR /&gt;
A,true&lt;BR /&gt;
B,true&lt;BR /&gt;
C,true&lt;/P&gt;

&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 17:30:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/difference-betwen-output-and-outputnew-in-splunk-lookup/m-p/112936#M29678</guid>
      <dc:creator>splunkn</dc:creator>
      <dc:date>2020-09-28T17:30:08Z</dc:date>
    </item>
    <item>
      <title>Re: difference betwen output and outputnew in splunk lookup</title>
      <link>https://community.splunk.com/t5/Splunk-Search/difference-betwen-output-and-outputnew-in-splunk-lookup/m-p/112937#M29679</link>
      <description>&lt;P&gt;The answer to your two numbered questions is: Yes, &lt;CODE&gt;stats&lt;/CODE&gt; represents the field in the event, and &lt;CODE&gt;description&lt;/CODE&gt; will be the new field generated. The difference between &lt;CODE&gt;OUTPUT&lt;/CODE&gt; and &lt;CODE&gt;OUTPUTNEW&lt;/CODE&gt; is if the &lt;CODE&gt;description&lt;/CODE&gt; field already exists in your event, &lt;CODE&gt;OUTPUT&lt;/CODE&gt; will overwrite it and &lt;CODE&gt;OUTPUTNEW&lt;/CODE&gt; won't.&lt;/P&gt;

&lt;P&gt;As for the rest of it, my recommendations would be:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Give global permission to everything first, get everything to work, and then change the permissions and see what breaks.&lt;/LI&gt;
&lt;LI&gt;Make sure that &lt;CODE&gt;default&lt;/CODE&gt; is a valid sourcetype in your data (if it's a host, source or rule, the syntax is different, check &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Propsconf"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/Propsconf&lt;/A&gt; for details).&lt;/LI&gt;
&lt;LI&gt;I wonder whether the name &lt;CODE&gt;LOOKUP-test_lkup&lt;/CODE&gt; is confusing things. The string after &lt;CODE&gt;LOOKUP-&lt;/CODE&gt; is supposed to be a unique literal, and &lt;CODE&gt;test_lkup&lt;/CODE&gt; is used elsewhere for other things. Try &lt;CODE&gt;LOOKUP-random&lt;/CODE&gt; and see whether that helps.&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Good luck.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Sep 2014 12:53:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/difference-betwen-output-and-outputnew-in-splunk-lookup/m-p/112937#M29679</guid>
      <dc:creator>aweitzman</dc:creator>
      <dc:date>2014-09-05T12:53:01Z</dc:date>
    </item>
  </channel>
</rss>

