Getting Data In

Timeparsing issues

walsborn
Path Finder

Hello all,

I'm having a time parsing issue that I don't know how to fix and am looking for some help.

My inputs on the syslog looks like this:

[monitor]
index = *
no_appending_timestamp = true
host_segment = 5
disabled = false

My Props for this source type is configured by a TA.  But the problem I'm having in the logs were from changes in our syslog system.

The new log looks like Dec 14 08:50:19 bxxm-itb.net.xxx.xxx 1,2021/12/14 08:50:18,

How do I configure props to tell splunk to ignore the first timestamp, skip the host fqdn and then parse the second time?

Labels (4)
0 Karma
1 Solution

gcusello
SplunkTrust
SplunkTrust

Hi @walsborn,

you have to add to your props.conf the following options:

[your_sourcetype]
TIME_PREFIX = ,
TIME_FORMAT = %Y/%m/%d %H:%M:%S

Ciao.

Giuseppe

View solution in original post

walsborn
Path Finder

That did it @gcusello , thank you.

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @walsborn,

you have to add to your props.conf the following options:

[your_sourcetype]
TIME_PREFIX = ,
TIME_FORMAT = %Y/%m/%d %H:%M:%S

Ciao.

Giuseppe

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!

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

Catalog Is Now Generally Available on Splunk Cloud Platform

A Unified View of Your Data  Security logs, application events, business data, and historical telemetry often ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...