For detailed installation instructions, see Install Splunk Stream.
Splunk Stream includes the following components:
• splunk_app_stream: splunk_app_stream provides configuration management for Splunk_TA_stream. You can use splunk_app_stream to configure event capture for multiple network protocols. See Supported Protocols.
• Splunk_TA_stream: Splunk_TA_stream contains the Stream Forwarder (streamfwd binary), which passively captures event data from network devices, and sends that data to Splunk Enterprise indexers using a "Wire Data" modular input.
• Independent Stream forwarder: Splunk Stream supports independent Stream forwarder installation on compatible Linux machines. Independent Stream Forwarder deployment is useful, for example, for capturing network data from Linux hosts that you want to monitor as part of a network service in a Splunk IT Service Intelligence (ITSI) deployment. No Splunk platform components are required on the machine where you install Stream Forwarder.
Important: You must be running splunkd with "root" privileges for the streamfwd binary to capture data. To set privileges on *nix:
On Windows, you must be running as administrator or install winpcap separately.
All captured events have "source=stream:stream-id" and "sourcetype=stream:protocol", where ID is typically the name of a protocol. For example, "sourcetype=stream:http."
Splunk Stream version 7.1.2 requires Splunk Enterprise version 6.4.0 or later.
For complete Splunk Stream documentation, see Splunk Stream documentation.
As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 50GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps and add-ons from Splunk, our partners and our community. Find an app or add-on for most any data source and user need, or simply create your own with help from our developer portal.