Getting Data In

Universal Forwarder as buffer only

jstockt
New Member

If the intention of using a Universal Forwarder is only for a buffer to the Indexer, is it worth having one?
Theory: Should there be a need to take the Indexer down for maintenance, the UF could continue to receive data and then catch the Indexer back up when maintenance is complete.
Is there any other method (outside of maybe Clustered Indexer) to ensure that log data continues to flow (from say 300 inputs) to somewhere while the Indexer server is down for a short period?

0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

The Universal Forwarder is more than just a buffer. Without it, how would you monitor the logs on remote (to Splunk) systems?

Another method to ensure data flows while an indexer is down for service is to have multiple indexers. If the UF is configured to forward to all indexers (and it should) then it will have an alternative path if one indexer is down. In the normal case, your data will be distributed across several indexers for better search performance.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

0 Karma

richgalloway
SplunkTrust
SplunkTrust

The Universal Forwarder is more than just a buffer. Without it, how would you monitor the logs on remote (to Splunk) systems?

Another method to ensure data flows while an indexer is down for service is to have multiple indexers. If the UF is configured to forward to all indexers (and it should) then it will have an alternative path if one indexer is down. In the normal case, your data will be distributed across several indexers for better search performance.

---
If this reply helps you, Karma would be appreciated.
0 Karma
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...