Getting Data In

Why is Splunk Connect for Syslog (SC4S) removing domain name?

twellinghurst
Engager

We are migrating our syslog server to Splunk Connect 4 Syslog running on a RHEL server inside a Docker container. The syslog messages are being forwarded to Splunk, however, SC4S is stripping the domain name off of the device names, causing issues with interfaces that are sending log messages.

For example, the host - "hostname.contoso.com", will have the host= hostname, while the hostname 
"lo0.hostname.contoso.com.", will have the host = lo0.

It appears SC4S is doing some sort of split on the first period (.) in the hostname and only keeping the first item in the array.

Is it possible to tell SC4S to use the FQDN as the hostname?

We are using reverse DNS on the SC4S instance - ie. SC4S_USE_REVERSE_DNS=yes

Any help is much appreciated!!

Labels (1)
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!

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...

Build and Launch AI Agents from Your Splunk Workflows

  Register We’ve all been there: juggling alerts, runbooks, and endless manual searches. What if you could ...

Splunk Cloud Application Management in Terraform

Register   On Tuesday, August 4 at 11AM PDT / 2PM EDT, we’re diving into how you can bring Infrastructure as ...