Getting Data In

How to configure props.conf and transforms.conf on Windows heavy forwarder to remove unwanted characters in rsyslog logs?

feliz
New Member

Hi there,

We have a Windows Heavy Forwarder which gets Windows logs. We want to send these logs to an external Rsyslog Server, using transforms.conf and props.conf:

transforms.conf

[syslog_routing]
REGEX = .
DEST_KEY = _SYSLOG_ROUTING
FORMAT = rsyslog

props.conf

`[syslog_test]

TRANSFORMS-routing = syslog_routing`

outputs.conf

`[syslog]
defaultGroup = rsyslog

[syslog:rsyslog]
server = rsyslog_server:514
type=tcp
timestampformat = %b %e %H:%M:%S`

On the rsyslog, we get these kind of entries:

Nov 12 15:46:34 192.168.135.10 #011Source Port:#011#0118089#015#015
Nov 12 15:46:34 192.168.135.10 #011Destination Address:#01110.0.0.1#015#015
Nov 12 15:46:34 192.168.135.10 #011Destination Port:#011#01164756#015#015
Nov 12 15:46:34 192.168.135.10 #011Protocol: #011#0116#015#015

So the question is, how to get rid of all the #11 and #15?

Thanks!

0 Karma

yannK
Splunk Employee
Splunk Employee

If the #11 an d #15 are in your initial raw data, try a sedcmd in the props.

0 Karma

feliz
New Member

Hey, thanks for your answer.

We tried to add SEDCMD-fix_space = s/#011/ /g, with no success...
We also tried to send with stanza tcpout, both on Heavy Forwarder and Indexer , as

`[tcpout]
defaultGroup=syslog_routing
indexAndForward=true
sendCookedData=false

[tcpout:raw_tcp_receiver]
server=rsyslog_server:514`

with no luck.

Edit: same result with SEDCMD-fix_space = s/\#011/ /g, in case that the # character was not interpreted.

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!

Observability Simplified: Combining User Experience, Application Performance & ...

Tech Talk Observability Simplified: Combining User Experience, Application Performance & Network ...

Event Series May & June: From Network Visibility to Service Intelligence

Unifying the Network: Moving from Alert Noise to Service Intelligence with Splunk ITSI In today’s hybrid ...

Global Splunk User Group Events: May + June 2026

Your Splunk Community Awaits: Discover Upcoming User Group Events Worldwide    Staying ahead in the fast-paced ...