<?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: eventtype from an inputlookup in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/eventtype-from-an-inputlookup/m-p/113980#M1172</link>
    <description>&lt;P&gt;Eventtypes cannot contain pipes or subsearches.&lt;/P&gt;</description>
    <pubDate>Thu, 09 Jul 2015 02:51:08 GMT</pubDate>
    <dc:creator>martin_mueller</dc:creator>
    <dc:date>2015-07-09T02:51:08Z</dc:date>
    <item>
      <title>eventtype from an inputlookup</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/eventtype-from-an-inputlookup/m-p/113979#M1171</link>
      <description>&lt;P&gt;I am making an app and wanted to have some dummy data tagged as an example to the end user.&lt;/P&gt;

&lt;P&gt;So I have eventtypes.conf as&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;[installed_applications]&lt;BR /&gt;
search = | inputlookup dummy_installed_applications&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;Now this search works as a standard search but will not work as an eventtype.&lt;/P&gt;

&lt;P&gt;Any suggestions?&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jul 2015 02:11:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/eventtype-from-an-inputlookup/m-p/113979#M1171</guid>
      <dc:creator>phoenixdigital</dc:creator>
      <dc:date>2015-07-09T02:11:09Z</dc:date>
    </item>
    <item>
      <title>Re: eventtype from an inputlookup</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/eventtype-from-an-inputlookup/m-p/113980#M1172</link>
      <description>&lt;P&gt;Eventtypes cannot contain pipes or subsearches.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jul 2015 02:51:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/eventtype-from-an-inputlookup/m-p/113980#M1172</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2015-07-09T02:51:08Z</dc:date>
    </item>
    <item>
      <title>Re: eventtype from an inputlookup</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/eventtype-from-an-inputlookup/m-p/113981#M1173</link>
      <description>&lt;P&gt;Very unfortunate&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jul 2015 22:26:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/eventtype-from-an-inputlookup/m-p/113981#M1173</guid>
      <dc:creator>phoenixdigital</dc:creator>
      <dc:date>2015-07-15T22:26:01Z</dc:date>
    </item>
    <item>
      <title>Re: eventtype from an inputlookup</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/eventtype-from-an-inputlookup/m-p/113982#M1174</link>
      <description>&lt;P&gt;Well, it's intrinsic to what an eventtype actually is:&lt;/P&gt;

&lt;P&gt;It's a set of search filters that determines what eventtypes an event gets annotated with. You use it two ways - either to filter based on the eventtype, or to look at the eventtype field in events returned by any search.&lt;/P&gt;

&lt;P&gt;A &lt;CODE&gt;| inputlookup&lt;/CODE&gt; doesn't make sense in this concept. Have you considered a macro?&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jul 2015 23:16:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/eventtype-from-an-inputlookup/m-p/113982#M1174</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2015-07-15T23:16:26Z</dc:date>
    </item>
  </channel>
</rss>

