Getting Data In

How to edit my datetime.xml to extract the date from a filename to use as the date for indexed events?

moaf13
Path Finder

I have read multiple blogs and answers and couldn't find anything that helps.

The filename will be something like thisblah_blah_blah....161030.txt
I have checked my regex on regex101 and it works perfectly.

This is what I have,

props.conf

[filedate]
DATETIME_CONFIG = /etc/system/local/datetime.xml
category= Date_time
CHARSET=AUTO
disabled=false
pulldown_type = true

Datetime.xml

<datetime>
  <define name="_masheddate3" extract="year, month, day,">
        <text> ![CDATA[(?:^|source:|source::).*?([123]\d)([01]\d)([0123]\d)[^0-9]]]  </text>
  </define>
  <datePatterns>
        <use name="_masheddate3"/>
  </datePatterns>
</datetime>

And this the error message that i get from Splunkd.log

11-03-2016 12:44:36.860 -0400 ERROR AggregatorMiningProcessor - Uncaught exception in Aggregator, skipping an event: Error parsing regex XML file: C:\Program Files\Splunk\etc\system\local\datetime.xml - Couldn't find 'timePatterns' in config data for AggregatorProcessor. - data_source="C:\Users\ComputerName\Documents\Test2\blah_blah161030.txt", data_host="local", data_sourcetype="filedate"</code>

11-03-2016 12:44:36.860 -0400 ERROR AggregatorMiningProcessor - Uncaught exception in Aggregator, skipping an event: Error parsing regex XML file: C:\Program Files\Splunk\etc\system\local\datetime.xml - Couldn't find 'timePatterns' in config data for AggregatorProcessor. - data_source="C:\Users\ComputerName\Documents\Test2\blah_blah161030.txt", data_host="local", data_sourcetype="filedate"

I know Props.conf is working by looking at this error message, so the only issue is in datetime.xml...
The time is irrelevant to me. How do I make Splunk just get the date and ignore the time? If there is anyone that had success in this, please let me know!

0 Karma
1 Solution

sshelly_splunk
Splunk Employee
Splunk Employee

I would not mess with datetime, unless really required. This should be able to set your day, month year (I think:)) :

EXTRACT-time = (?\d{8}) in source
EVAL-_time = strptime(time,"%Y%m%d”)

It has been a while since i used this, but it might help. Note that the time of day for each event in that file will be midnight.

View solution in original post

maraman_splunk
Splunk Employee
Splunk Employee

I think Splunk complain because you don't specify any time in your datetime.xml
so you should add something that just set a time to a known value (perhaps at 00:00:00)

   1 <define name="Your Custom Name Time" >
   2          <text>set your time to 00:00:00 here</text>
   3  </define>
   4  
   5  <timePatterns>
   6       <use name="Your Custom Name Time"/>
   7 </timePatterns>
0 Karma

sshelly_splunk
Splunk Employee
Splunk Employee

I would not mess with datetime, unless really required. This should be able to set your day, month year (I think:)) :

EXTRACT-time = (?\d{8}) in source
EVAL-_time = strptime(time,"%Y%m%d”)

It has been a while since i used this, but it might help. Note that the time of day for each event in that file will be midnight.

maraman_splunk
Splunk Employee
Splunk Employee

This config is search time only
Time should be set at index time.

0 Karma

Lowell
Super Champion

Um, doesn't setting this at search time have a pretty significant performance implication? Additionally, since data is stored in reverse TIME order (emphasis on time) in the index, this means that what your search pull back will be based on the initial _time field (as it was stored in the index) and NOT search-time extracted _time field shown above.

I strongly recommend avoiding this solution. It's find if you want to extract it with some OTHER name, just don't use "_time".

0 Karma

abhishekdharga
Engager

Thanks it worked

0 Karma

moaf13
Path Finder

Update: I was able to fix that error or by pass it by adding,

<timePatterns>
<use name="_masheddate2"/>
</timePatterns>

However, when that happens, Splunk automatically sets timestamp as none
which basically forces it to index it at a current time.

0 Karma

kjetilho
Engager

guess you would need masheddate3 and not masheddate2

0 Karma
Get Updates on the Splunk Community!

Introducing Splunk Enterprise 9.2

WATCH HERE! Watch this Tech Talk to learn about the latest features and enhancements shipped in the new Splunk ...

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...