Splunk Stream

Installation and Configuration Manual

Download manual as PDF

This documentation does not apply to the most recent version of StreamApp. Click here for the latest version.
Download topic as PDF

Configure universal forwarder for Splunk_TA_stream

Send data to _internal index

Splunk Stream automatically configures universal forwarders to send data from Splunk_TA_stream to your _internal index over the Wire Data modular input at installation time. No additional universal forwarder configuration is required.

Manage Splunk_TA_stream stats data

Splunk_TA_stream (Stream forwarder) sends operational statistics and log data to _internal index. Splunk App for Stream uses this data to populate built-in dashboards, including the Stream Estimate dashboard.

There are three event types that Splunk_TA_stream sends to _internalindex:

  • stream:stats
  • stream:log
  • streamfwd*


The streamfwd* event type comes from the stream forwarder's local log file. The forwarder monitors that log file along with other files in the $SPLUNK_HOME/var/log/splunk/ directory. Though it is useful for troubleshooting locally, the data that streamfwd* contains is the same as the data that stream:log contains. Therefore, you can safely blacklist the streamfwd* event type to avoid indexing duplicate data.

For more information, see Whitelist or blacklist specific incoming data in the Getting Data In manual.

Modify universal forwarder data limits

By default, the Splunk universal forwarder sends a maximum of 256 Kbps of data to indexers. Depending on your streamfwd configuration, your deployment might generate more data than this.

To modify or remove the default universal forwarder limit:

1. Edit $SPLUNK_HOME/etc/apps/SplunkUniversalForwarder/local/limits.conf.

2. Modify the [thruput] stanza. For example:

[thruput]
maxKBps = 0
PREVIOUS
streamfwd.conf
  NEXT
Ingest pcap files

This documentation applies to the following versions of Splunk Stream: 6.5.0, 6.5.1, 6.6.0, 6.6.1, 6.6.2, 7.0.0, 7.0.1, 7.1.0, 7.1.1


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters