Getting Data In

Filter _internal events that get forwarded

belka
Path Finder

My company has a lot of small, independent offices that have a handful of machines in each locations. The problem is there are literally hundreds of locations, many of them rural with low bandwidth.

I'd like to filter what gets sent to index=_internal by the UniversalForwarder. I know that a Heavy forwarder can do that, but I've already provisioned thousands of Windows machines with Splunk and the _internal index is clogging some of the pipes. Any suggestion how to get just warnings and alerts for _internal instead of bandwidth-filling info events?

0 Karma

kristian_kolb
Ultra Champion

Perhaps this can be of help? Either stop forwarding the _internal events from the forwarders altogether with the forwardedindex setting in outputs.conf, or configure the logging levels for the various components through log.cfg;

http://docs.splunk.com/Documentation/Splunk/latest/Admin/outputsconf
http://docs.splunk.com/Documentation/Splunk/6.0.1/Troubleshooting/WhatSplunklogsaboutitself

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Accelerate Splunk App Development with AI

  Learn how to automate the repetitive parts of your build cycle.   Watch On-Demand   Replay the Accelerate ...

Splunk Agent Observability: Measuring AI Value with Splunk Tokenomics on AWS

The AI landscape is moving faster than ever, and our latest 2026 State of Observability report provides the ...

Enterprise Security Watch Party: What’s New in 8.8 - Recap

Splunk Community HQ hosted a Splunk Enterprise Security Watch Party: What’s New In ES 8.8 last Thursday. I had ...