Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Getting Data In
- :
- Timestamp format
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I have log files which have timestamp format like
04/10/2012 07:50:09 - dd/mm/yyyy HH:MM:SS
but indexer thinks it's a mm/dd instead of dd/mm. Logs are monitored by forwarder which has a props.conf
[source::E:\Logging\]
TIME_FORMAT = %d/%m/%Y %H:%M:%S
But still nothing changed. Data with timestamp, for example 04/10/2012 I can find for April, but not for October. Any suggestions?
Splunk forwarder version - 4.3.4, splunk indexer - 4.3
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The TIME_FORMAT needs to specified in your props.conf. Furthermore, it is relevant to the Splunk server that does the parsing. In other words, if your using a universal forwarder, you need to edit your props.conf on the indexer.
The alternative is to use a heavy forwarder to do parsing.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The TIME_FORMAT needs to specified in your props.conf. Furthermore, it is relevant to the Splunk server that does the parsing. In other words, if your using a universal forwarder, you need to edit your props.conf on the indexer.
The alternative is to use a heavy forwarder to do parsing.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ok, got it. Will try to configure the indexer
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
and one more thing - this issue started from October only, for last months I didn't have such problem
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Make your Splunk investment work harder with Optimization Advisor
How Splunk AI Assistant Is Transforming Investigations: Insights from .conf26
Make Your Machine Data AI-Ready in Splunk
