<?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: Universal Forwarder + nullQueue in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-nullQueue/m-p/144325#M29472</link>
    <description>&lt;P&gt;No, since nullQueue tranformations take place during the parsing phase, this configuration is only valid on either a Heavy Forwarder or an Indexer.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings"&gt;http://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;/K&lt;/P&gt;</description>
    <pubDate>Fri, 15 Nov 2013 14:38:49 GMT</pubDate>
    <dc:creator>kristian_kolb</dc:creator>
    <dc:date>2013-11-15T14:38:49Z</dc:date>
    <item>
      <title>Universal Forwarder + nullQueue</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-nullQueue/m-p/144324#M29471</link>
      <description>&lt;P&gt;I'm trying to remove some of the events that should be forwarded to the frontend.&lt;BR /&gt;
From a configuration perspective everything is OK.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;transforms.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[nullMon]
REGEX = .
DEST_KEY = queue
FORMAT = nullQueue

[routeRemains]
REGEX = .
DEST_KEY=_TCP_ROUTING
FORMAT= tcp_out
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;props.conf&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source_log]
TRANSFORMS = nullMon, routeRemains
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;But I'm receiving everything on the destination host.&lt;BR /&gt;
Does the Universal Forwarder allow the use of nullQueues?&lt;/P&gt;</description>
      <pubDate>Fri, 15 Nov 2013 14:30:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-nullQueue/m-p/144324#M29471</guid>
      <dc:creator>ruisantos</dc:creator>
      <dc:date>2013-11-15T14:30:04Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder + nullQueue</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-nullQueue/m-p/144325#M29472</link>
      <description>&lt;P&gt;No, since nullQueue tranformations take place during the parsing phase, this configuration is only valid on either a Heavy Forwarder or an Indexer.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings"&gt;http://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;/K&lt;/P&gt;</description>
      <pubDate>Fri, 15 Nov 2013 14:38:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-nullQueue/m-p/144325#M29472</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-11-15T14:38:49Z</dc:date>
    </item>
    <item>
      <title>Re: Universal Forwarder + nullQueue</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-nullQueue/m-p/144326#M29473</link>
      <description>&lt;P&gt;No, you'd need to configure this transform on an indexer or heavy forwarder.  See &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0/Indexer/Howindexingworks"&gt;http://docs.splunk.com/Documentation/Splunk/6.0/Indexer/Howindexingworks&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Nov 2013 14:40:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Universal-Forwarder-nullQueue/m-p/144326#M29473</guid>
      <dc:creator>fervin</dc:creator>
      <dc:date>2013-11-15T14:40:52Z</dc:date>
    </item>
  </channel>
</rss>

