<?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: Ingest Action to include message in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Ingest-Action-to-include-message/m-p/686982#M114511</link>
    <description>&lt;P&gt;I tried this but still i am seeing other events being ingested apart from :ERROR: and :FATAL:&lt;/P&gt;</description>
    <pubDate>Thu, 09 May 2024 07:56:37 GMT</pubDate>
    <dc:creator>yuvaraj_m91</dc:creator>
    <dc:date>2024-05-09T07:56:37Z</dc:date>
    <item>
      <title>Ingest Action to include message</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Ingest-Action-to-include-message/m-p/686958#M114500</link>
      <description>&lt;P&gt;I am using ingest action to filter the log message before being indexed in splunk..&lt;BR /&gt;&lt;BR /&gt;I want to include the message that matches only the keyword :ERROR: and :FATAL: rest all of the messages should not be indexed.&lt;/P&gt;&lt;P&gt;Whereas in splunk ingest action has the filter to only exclude message not the include&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2024 05:56:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Ingest-Action-to-include-message/m-p/686958#M114500</guid>
      <dc:creator>yuvaraj_m91</dc:creator>
      <dc:date>2024-05-09T05:56:24Z</dc:date>
    </item>
    <item>
      <title>Re: Ingest Action to include message</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Ingest-Action-to-include-message/m-p/686976#M114501</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;/P&gt;&lt;P&gt;You might then be able to apply a regex pattern to say to &lt;STRONG&gt;NOT&lt;/STRONG&gt; not match ERROR or FATAL, therefore keep them, and discard the rest.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Try this&amp;nbsp;&lt;BR /&gt;^(?!.*(ERROR|FATAL)).*$&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2024 07:24:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Ingest-Action-to-include-message/m-p/686976#M114501</guid>
      <dc:creator>deepakc</dc:creator>
      <dc:date>2024-05-09T07:24:37Z</dc:date>
    </item>
    <item>
      <title>Re: Ingest Action to include message</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Ingest-Action-to-include-message/m-p/686982#M114511</link>
      <description>&lt;P&gt;I tried this but still i am seeing other events being ingested apart from :ERROR: and :FATAL:&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2024 07:56:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Ingest-Action-to-include-message/m-p/686982#M114511</guid>
      <dc:creator>yuvaraj_m91</dc:creator>
      <dc:date>2024-05-09T07:56:37Z</dc:date>
    </item>
    <item>
      <title>Re: Ingest Action to include message</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Ingest-Action-to-include-message/m-p/686983#M114512</link>
      <description>&lt;P&gt;If you're not hellbent of doing it with Ingest Actions, you can just use transforms to filter out all events except for the ones you want&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/Forwarding/Routeandfilterdatad" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/latest/Forwarding/Routeandfilterdatad&lt;/A&gt;&lt;/P&gt;&lt;P&gt;In your case you'd need to first have a "match-all" transform rerouting all data to nullQueue, and then a transform maching only ERROR/FATAL events sending the events to indexQueue.&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2024 08:00:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Ingest-Action-to-include-message/m-p/686983#M114512</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-05-09T08:00:17Z</dc:date>
    </item>
    <item>
      <title>Re: Ingest Action to include message</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Ingest-Action-to-include-message/m-p/686984#M114513</link>
      <description>&lt;P&gt;we are using splunk cloud UI&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2024 08:04:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Ingest-Action-to-include-message/m-p/686984#M114513</guid>
      <dc:creator>yuvaraj_m91</dc:creator>
      <dc:date>2024-05-09T08:04:16Z</dc:date>
    </item>
    <item>
      <title>Re: Ingest Action to include message</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Ingest-Action-to-include-message/m-p/686985#M114514</link>
      <description>&lt;P&gt;Doesn't matter. You can make an app with those settings and deploy it to your Cloud instance.&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2024 08:05:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Ingest-Action-to-include-message/m-p/686985#M114514</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-05-09T08:05:36Z</dc:date>
    </item>
    <item>
      <title>Re: Ingest Action to include message</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Ingest-Action-to-include-message/m-p/686991#M114515</link>
      <description>&lt;P&gt;Suggestions made by&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/231884"&gt;@PickleRick&lt;/a&gt;&amp;nbsp; are probably best to go with.&amp;nbsp;&lt;/P&gt;&lt;P&gt;In terms of it still not working - you will most likely need to adjust the reg-ex pattern based on your logs.&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2024 08:41:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Ingest-Action-to-include-message/m-p/686991#M114515</guid>
      <dc:creator>deepakc</dc:creator>
      <dc:date>2024-05-09T08:41:04Z</dc:date>
    </item>
  </channel>
</rss>

