- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ingest Action to include message
I am using ingest action to filter the log message before being indexed in splunk..
I want to include the message that matches only the keyword :ERROR: and :FATAL: rest all of the messages should not be indexed.
Whereas in splunk ingest action has the filter to only exclude message not the include
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

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
https://docs.splunk.com/Documentation/Splunk/latest/Forwarding/Routeandfilterdatad
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.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
we are using splunk cloud UI
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Doesn't matter. You can make an app with those settings and deploy it to your Cloud instance.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
You might then be able to apply a regex pattern to say to NOT not match ERROR or FATAL, therefore keep them, and discard the rest.
Try this
^(?!.*(ERROR|FATAL)).*$
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I tried this but still i am seeing other events being ingested apart from :ERROR: and :FATAL:
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Suggestions made by @PickleRick are probably best to go with.
In terms of it still not working - you will most likely need to adjust the reg-ex pattern based on your logs.
