<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Splunk DB Connect: Why is the timestamp specified in inputs.conf not being parsed? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-DB-Connect-Why-is-the-timestamp-specified-in-inputs-conf/m-p/163284#M98080</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I am trying to import data from a MySQL database.&lt;/P&gt;

&lt;P&gt;While the import works fine, the time field gets populated with the time that the event is being imported, but not the 'datetime' field that I have specified in the database (in my case V_Date).&lt;/P&gt;

&lt;P&gt;inputs.conf / [$SPLUNK_HOME/var/lib/splunk/persistentstorage/dbx]&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[dbmon-tail://CTM/CTM Violations]
host = CTM
index = development_index
output.format = kv
output.timestamp = 0
query = SELECT VIOLATION_ID,V_DATE,VIOLATION_TYPE_ID,V_CLIENT_ID,VIOLATION_SOURCE, VIOLATION_FREQUENCY,V_LICENCE_ID,V_MODULE_ID\r\nFROM VIOLATIONS {{WHERE $rising_column$ &amp;gt; ?}}
sourcetype = CTM Violations
tail.rising.column = VIOLATION_ID
interval = auto
table = CTM Violations
disabled = 0
output.timestamp.column = V_DATE
output.timestamp.format = yyyy-MM-dd HH:mm:ss
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I have also tried without the&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;output.timestamp.column = V_DATE
output.timestamp.format = yyyy-MM-dd HH:mm:ss
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Date Column is V_DATE // V_DATE datetime.&lt;/P&gt;

&lt;P&gt;I tried creating a props.conf file at a second stage.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[host::CTM]
DATETIME_CONFIG = NONE
SHOULD_LINEMERGE = false
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Any suggestions?&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 19:04:48 GMT</pubDate>
    <dc:creator>dimitris_vergos</dc:creator>
    <dc:date>2020-09-28T19:04:48Z</dc:date>
    <item>
      <title>Splunk DB Connect: Why is the timestamp specified in inputs.conf not being parsed?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-DB-Connect-Why-is-the-timestamp-specified-in-inputs-conf/m-p/163284#M98080</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I am trying to import data from a MySQL database.&lt;/P&gt;

&lt;P&gt;While the import works fine, the time field gets populated with the time that the event is being imported, but not the 'datetime' field that I have specified in the database (in my case V_Date).&lt;/P&gt;

&lt;P&gt;inputs.conf / [$SPLUNK_HOME/var/lib/splunk/persistentstorage/dbx]&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[dbmon-tail://CTM/CTM Violations]
host = CTM
index = development_index
output.format = kv
output.timestamp = 0
query = SELECT VIOLATION_ID,V_DATE,VIOLATION_TYPE_ID,V_CLIENT_ID,VIOLATION_SOURCE, VIOLATION_FREQUENCY,V_LICENCE_ID,V_MODULE_ID\r\nFROM VIOLATIONS {{WHERE $rising_column$ &amp;gt; ?}}
sourcetype = CTM Violations
tail.rising.column = VIOLATION_ID
interval = auto
table = CTM Violations
disabled = 0
output.timestamp.column = V_DATE
output.timestamp.format = yyyy-MM-dd HH:mm:ss
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I have also tried without the&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;output.timestamp.column = V_DATE
output.timestamp.format = yyyy-MM-dd HH:mm:ss
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Date Column is V_DATE // V_DATE datetime.&lt;/P&gt;

&lt;P&gt;I tried creating a props.conf file at a second stage.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[host::CTM]
DATETIME_CONFIG = NONE
SHOULD_LINEMERGE = false
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Any suggestions?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 19:04:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-DB-Connect-Why-is-the-timestamp-specified-in-inputs-conf/m-p/163284#M98080</guid>
      <dc:creator>dimitris_vergos</dc:creator>
      <dc:date>2020-09-28T19:04:48Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk DB Connect: Why is the timestamp specified in inputs.conf not being parsed?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-DB-Connect-Why-is-the-timestamp-specified-in-inputs-conf/m-p/163285#M98081</link>
      <description>&lt;P&gt;Can you supply an example of the results of the SQL query? That may not help, but it may give us more to work with.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Mar 2015 18:35:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-DB-Connect-Why-is-the-timestamp-specified-in-inputs-conf/m-p/163285#M98081</guid>
      <dc:creator>cpetterborg</dc:creator>
      <dc:date>2015-03-04T18:35:19Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk DB Connect: Why is the timestamp specified in inputs.conf not being parsed?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-DB-Connect-Why-is-the-timestamp-specified-in-inputs-conf/m-p/163286#M98082</link>
      <description>&lt;P&gt;Here you go,&lt;/P&gt;

&lt;P&gt;ID            V_ID      C_ID       C_IP                     L_ID     V_DATE                    V_F   V_M&lt;BR /&gt;
90050   1         6      31.5.253.88    8   2015-03-04 14:26:56 58  1&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 19:05:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-DB-Connect-Why-is-the-timestamp-specified-in-inputs-conf/m-p/163286#M98082</guid>
      <dc:creator>dimitris_vergos</dc:creator>
      <dc:date>2020-09-28T19:05:09Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk DB Connect: Why is the timestamp specified in inputs.conf not being parsed?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-DB-Connect-Why-is-the-timestamp-specified-in-inputs-conf/m-p/163287#M98083</link>
      <description>&lt;P&gt;In my personal opinion, time formatting is easier to do in SQL than SPL, so I prefer to do it there when working with DB Connect 1.&lt;/P&gt;

&lt;P&gt;If you use DB Connect 2, it has a UI to help you set the right time format when you build your input.&lt;/P&gt;</description>
      <pubDate>Sat, 11 Apr 2015 20:49:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-DB-Connect-Why-is-the-timestamp-specified-in-inputs-conf/m-p/163287#M98083</guid>
      <dc:creator>jcoates_splunk</dc:creator>
      <dc:date>2015-04-11T20:49:22Z</dc:date>
    </item>
  </channel>
</rss>

