Getting Data In

splitting data coming from Universal forwarder to external syslog

ssyed2009
New Member

We are forwarding data coming from our universal forwarders to an external Syslog server.

Our current Dataflow Architecture

Universal Forwarder -> Regional Heavy Forwarder -> Final Heavy forwarder -> Indexer

the data is received from the universal forwarder and an output sends the data to Regional Heavy Forwarder. There is another output that sends the data to the final Heavy forwarder. Once the data gets to the final heavy forwarder we have outputs that output data to indexer and duplicate stream to external Syslog.

ISSUE
The event count in the external Syslog server from the duplicate stream is almost half than the data that was indexed by Splunk. So from Splunk to our external Syslog server, we are dropping events.

ASK
I would like to know if there is a tstat command or something is Splunk that would give some metrics of how much data is being sent to the external source from a particular outputs.conf.

To send data to external syslog we are using the below solution

props.conf
[sourcetype]
TRANSFORMS-sample = sample_syslog_trend

transforms.conf
[sample_syslog_trend]
REGEX = .
DEST_KEY = _SYSLOG_ROUTING
FORMAT = sample_syslog

outputs.conf
[syslog:sample_syslog]
server = hostname/ipaddress:514
sendCookedData = false

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!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

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 ...