Solved: How to modify syslog source type to handle rfc3339... - Splunk Community

Getting Data In

We pass messages with rsyslog using the rfc3339 time format. It has microseconds, and it has a timestamp. But noticed a few issues:

The time zone is not parsed out of the message. If I remove the microseconds from the timestamp, it would work fine.
The host does not get parsed out. Seems to be a problem with the syslog-host transform which does not like the timezone. Dropping the timezone fixes this problem but I would rather keep it.

What would be the best way to proceed?

Modify the syslog source type?
Create a new source type?
Report the issue and hope for a fix?

1 Solution

Solution

The best approach (IMO) is to create a new sourcetype that parses the data.

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

View solution in original post

Solution

The best approach (IMO) is to create a new sourcetype that parses the data.

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

Get Updates on the Splunk Community!

Aligning Observability Costs with Business Value: Practical Strategies

Join us for an engaging Tech Talk on Aligning Observability Costs with Business Value: Practical ...

Mastering Data Pipelines: Unlocking Value with Splunk

In today's AI-driven world, organizations must balance the challenges of managing the explosion of data with ...

Splunk Up Your Game: Why It's Time to Embrace Python 3.9+ and OpenSSL 3.0

Did you know that for Splunk Enterprise 9.4, Python 3.9 is the default interpreter? This shift is not just a ...