<?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 Docker logs control in Splunk in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Docker-logs-control-in-Splunk/m-p/389676#M69737</link>
    <description>&lt;P&gt;Hi there,&lt;BR /&gt;
Is there anyway on Splunk search peer or Forwarder to filter the data. Like log messages that contain DEBUG or INFO should be filtered before getting indexed in Splunk?&lt;/P&gt;</description>
    <pubDate>Tue, 16 Jul 2019 14:53:10 GMT</pubDate>
    <dc:creator>rashi83</dc:creator>
    <dc:date>2019-07-16T14:53:10Z</dc:date>
    <item>
      <title>Docker logs control in Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Docker-logs-control-in-Splunk/m-p/389676#M69737</link>
      <description>&lt;P&gt;Hi there,&lt;BR /&gt;
Is there anyway on Splunk search peer or Forwarder to filter the data. Like log messages that contain DEBUG or INFO should be filtered before getting indexed in Splunk?&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jul 2019 14:53:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Docker-logs-control-in-Splunk/m-p/389676#M69737</guid>
      <dc:creator>rashi83</dc:creator>
      <dc:date>2019-07-16T14:53:10Z</dc:date>
    </item>
    <item>
      <title>Re: Docker logs control in Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Docker-logs-control-in-Splunk/m-p/389677#M69738</link>
      <description>&lt;P&gt;yes, many ways, starting with monitor filtering while and black listing and all the way to filtering an  routing with props.conf and transforms.conf&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.3.0/Data/Whitelistorblacklistspecificincomingdata"&gt;https://docs.splunk.com/Documentation/Splunk/7.3.0/Data/Whitelistorblacklistspecificincomingdata&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.3.0/Forwarding/Routeandfilterdatad"&gt;https://docs.splunk.com/Documentation/Splunk/7.3.0/Forwarding/Routeandfilterdatad&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;and some more specific to your use case answers:&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/257216/how-to-filter-out-debug-logs-except-3-different-lo.html"&gt;https://answers.splunk.com/answers/257216/how-to-filter-out-debug-logs-except-3-different-lo.html&lt;/A&gt;&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/59370/filtering-events-using-nullqueue-1.html"&gt;https://answers.splunk.com/answers/59370/filtering-events-using-nullqueue-1.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;hope it helps&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jul 2019 19:35:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Docker-logs-control-in-Splunk/m-p/389677#M69738</guid>
      <dc:creator>adonio</dc:creator>
      <dc:date>2019-07-16T19:35:01Z</dc:date>
    </item>
    <item>
      <title>Re: Docker logs control in Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Docker-logs-control-in-Splunk/m-p/389678#M69739</link>
      <description>&lt;P&gt;Depends on how you ingest docker  logs, with the collectord you can annotate to drop some log lines, see &lt;A href="https://www.outcoldsolutions.com/docs/monitoring-docker/v5/annotations/#example-2-dropping-messages"&gt;https://www.outcoldsolutions.com/docs/monitoring-docker/v5/annotations/#example-2-dropping-messages&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jul 2019 05:53:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Docker-logs-control-in-Splunk/m-p/389678#M69739</guid>
      <dc:creator>outcoldman</dc:creator>
      <dc:date>2019-07-17T05:53:12Z</dc:date>
    </item>
  </channel>
</rss>

