<?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: NullQ output to a File? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/NullQ-output-to-a-File/m-p/182756#M36622</link>
    <description>&lt;P&gt;Sadly no. There is no "write to file" processor.&lt;/P&gt;</description>
    <pubDate>Mon, 27 Oct 2014 08:36:34 GMT</pubDate>
    <dc:creator>Ayn</dc:creator>
    <dc:date>2014-10-27T08:36:34Z</dc:date>
    <item>
      <title>NullQ output to a File?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/NullQ-output-to-a-File/m-p/182755#M36621</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have applied NullQ and IndexQ filtering on my log files at Heavy Forwarder. But the client demands, we do not want to throw away the data but also don't want to index it. For sanity testing, is it possible to send the nullQ output to a flat file which will be stored on a per-day basis?&lt;/P&gt;

&lt;P&gt;i.e. instead of writing nullqueue in the transforms, can I write name of file or location?&lt;BR /&gt;
DEST_KEY = queue&lt;BR /&gt;
FORMAT = nullQueue&lt;/P&gt;</description>
      <pubDate>Mon, 27 Oct 2014 04:55:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/NullQ-output-to-a-File/m-p/182755#M36621</guid>
      <dc:creator>meenal901</dc:creator>
      <dc:date>2014-10-27T04:55:29Z</dc:date>
    </item>
    <item>
      <title>Re: NullQ output to a File?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/NullQ-output-to-a-File/m-p/182756#M36622</link>
      <description>&lt;P&gt;Sadly no. There is no "write to file" processor.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Oct 2014 08:36:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/NullQ-output-to-a-File/m-p/182756#M36622</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2014-10-27T08:36:34Z</dc:date>
    </item>
    <item>
      <title>Re: NullQ output to a File?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/NullQ-output-to-a-File/m-p/182757#M36623</link>
      <description>&lt;P&gt;Can this be possible:&lt;/P&gt;

&lt;P&gt;I route the unwanted data to DEST_KEY=SYSLOG, localhost:541&lt;BR /&gt;
Then by using SYSLOGNG monitor the 541 port and redirect to a flat file instead of another Splunk instance?&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
Meenal&lt;/P&gt;</description>
      <pubDate>Thu, 13 Nov 2014 08:42:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/NullQ-output-to-a-File/m-p/182757#M36623</guid>
      <dc:creator>meenal901</dc:creator>
      <dc:date>2014-11-13T08:42:36Z</dc:date>
    </item>
  </channel>
</rss>

