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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...