Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Getting Data In
- :
- Re: Can I block a sourcetype from being indexed?
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We have a huge sudden input of a specific sourcetype and it is overloading the license. Can we somehow block it or set it to drop so they do not get indexed and make us go over our license? Any ideas welcome, but we do not use iptables and are not able to block it at the network level, so it would have to be something in Splunk.
Thanks
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A simple configuration like this should work. Depending on if you have forwarders (and if there are lightweight or not) may change where you need to deploy these settings to.
props.conf
[my_out_of_control_sourcetype]
TRANFORMS-dropall = drop_events
transforms.conf
[drop_events]
DEST_KEY = queue
REGEX = .
FORMAT = nullQueue
Simply replace "my_out_of_control_sourcetype" with the name of the sourectype you want to silence.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For some reason, this seems to have stopped working. Any other ideas? Thank you!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A simple configuration like this should work. Depending on if you have forwarders (and if there are lightweight or not) may change where you need to deploy these settings to.
props.conf
[my_out_of_control_sourcetype]
TRANFORMS-dropall = drop_events
transforms.conf
[drop_events]
DEST_KEY = queue
REGEX = .
FORMAT = nullQueue
Simply replace "my_out_of_control_sourcetype" with the name of the sourectype you want to silence.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That's weird. It shouldn't have worked and then stopped working. Have you confirmed that no other part of your configuration changed? Are you blocking based on sourcetype or based on a host entry? Posting your exact config may be helpful too.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For some reason, this seems to have stopped working. Any other ideas?
Thank you!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
excellent! Thank you! seems to be working great.
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Index This | What travels the world but is also stuck in place?
Discover New Use Cases: Unlock Greater Value from Your Existing Splunk Data
Continue Your Journey: Join Session 2 of the Data Management and Federation Bootcamp ...
