Splunk Search

Multiple Outputs - One Fails, Both Fail

jharms70
New Member

Hi there,

I have a HF which has two outputs - one to a set of Splunk indexers and one to a TCP-based syslog server.

The "stream" going to the index servers are the raw Windows logs, while the "stream" going to syslog is a clone of the original event which has been altered. We make use of the null queue to stop the cloned event being indexed by index servers as well.

We had a scenario where the syslog server was unavailable. This resulted in the queues filling up and logs not being forward to BOTH destinations.

I had a look through the outputs.conf doco and the following item looked like a likely fix if it were applied:

blockOnCloning (default is true).

Am I correct in assuming that with this set to false in outputs.conf, that the HF will still send data to the indexers in the event that the syslog server goes offline?

Thanks
Jono

Tags (1)
0 Karma

jharms70
New Member

Found this https://answers.splunk.com/answers/626616/why-data-is-not-been-routing-to-second-group-when.html

Seems to answer my question. Any rep from Splunk to confirm would be ace though.

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!

Quantify Your Splunk Investment Impact: Introducing Savings Metrics to Value Insights

Building on the foundation established in our initial Value Insights releases, we are introducing the Savings ...

Event Series: Telemetry Pipeline Management

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...