<?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: Log Output obfuscates our logs related to splunk plugin in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Log-output-obfuscates-our-logs-related-to-Splunk-plugin/m-p/628661#M107888</link>
    <description>&lt;P&gt;You can't remove anything from the logs already ingested by Splunk, but you can prevent unwanted events from being indexed.&lt;/P&gt;&lt;P&gt;If you're running Splunk 9.x, have a look at Settings-&amp;gt;Ingest Actions.&amp;nbsp; This GUI defines the props and transforms needed to selectively filter events.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 27 Jan 2023 18:19:31 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2023-01-27T18:19:31Z</dc:date>
    <item>
      <title>Log output obfuscates our logs related to Splunk plugin</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Log-output-obfuscates-our-logs-related-to-Splunk-plugin/m-p/628651#M107887</link>
      <description>&lt;P&gt;We have been having a constant stream of log output related to the tier 3 "splunk" plugin, looking to see how to remove this as it is making our bundles difficult to analize and solve issues.&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screen Shot 2023-01-27 at 11.06.43.png" style="width: 999px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/23594i61BB5F5B5C3F0A81/image-size/large?v=v2&amp;amp;px=999" role="button" title="Screen Shot 2023-01-27 at 11.06.43.png" alt="Screen Shot 2023-01-27 at 11.06.43.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;There is a constant stream of jenkins_console comming from most of our backend microservices, is there anyway to remove this from our logs?&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;
&lt;P&gt;Fernando&lt;/P&gt;
&lt;P&gt;Devops SquareTrade&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2023 19:43:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Log-output-obfuscates-our-logs-related-to-Splunk-plugin/m-p/628651#M107887</guid>
      <dc:creator>Fer</dc:creator>
      <dc:date>2023-01-27T19:43:31Z</dc:date>
    </item>
    <item>
      <title>Re: Log Output obfuscates our logs related to splunk plugin</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Log-output-obfuscates-our-logs-related-to-Splunk-plugin/m-p/628661#M107888</link>
      <description>&lt;P&gt;You can't remove anything from the logs already ingested by Splunk, but you can prevent unwanted events from being indexed.&lt;/P&gt;&lt;P&gt;If you're running Splunk 9.x, have a look at Settings-&amp;gt;Ingest Actions.&amp;nbsp; This GUI defines the props and transforms needed to selectively filter events.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2023 18:19:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Log-output-obfuscates-our-logs-related-to-Splunk-plugin/m-p/628661#M107888</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-01-27T18:19:31Z</dc:date>
    </item>
  </channel>
</rss>

