Splunk® Data Stream Processor

Install and administer the Data Stream Processor

Download manual as PDF

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

Hardware and Software Requirements

The Data Stream Processor officially supports the following hardware and software versions.

Forwarders versions

The Data Stream Processor 1.0.0 officially supports Splunk Forwarders 7.1.0 and above.

Browser versions

The Data Stream Processor 1.0.0 officially supports these browsers:

  • Chrome 77.0 and above
  • Safari (latest)
  • Firefox (latest)
  • Microsoft Edge 11 and above


Operating system versions

The Data Stream Processor 1.0.0 officially supports the following Linux Operating Systems.

  • Red Hat: 7.x and 8.0
  • Centos: 7.x
  • Ubuntu: 18.04

Splunk Enterprise versions

The Data Stream Processor 1.0.0 officially supports sending data to Splunk Enterprise 7.1.0+ instances hosted on Linux.

Hardware Requirements

We recommend a clustered deployment of five nodes, with each node having the following specifications:

Hardware Specifications
CPU cores 8 physical cores, 16 recommended
Network speed 10 Gb/s or higher
Memory 64 GB, 128 GB recommended
Storage 1 TB
Disk space Enough disk space in /var to support 24 hours of data retention.

To reduce the latency of communication between DSP components, all nodes in the DSP cluster should be interconnected via a low-latency network. For example, in cloud deployments, components must be placed in the same region. While nodes may span availability zones, DSP does not currently guarantee services will be effectively deployed.

PREVIOUS
Installation checklist for DSP
  NEXT
Install the Data Stream Processor

This documentation applies to the following versions of Splunk® Data Stream Processor: 1.0.0


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