Splunk Search

dbconnect timestamp

sbsbb
Builder

I've a DBconnect on a MSSQL

My Timestamp in the DB looks like this : 2013-04-04 15:24:36.7170000

I've defined the folowing
output.timestamp.format = "yyyy-MM-dd HH:mm:ss.SSS"
output.timestamp.parse.format = "yyyy-MM-dd HH:mm:ss.SSS"

The output from Splunk is
1970-01-01 00:59:59.999 !

I've tried to truncate the input to 2013-04-04 15:24:36.717 first, but same result

Lazarix
Communicator

You can also do:

| convert timeformat="%Y/%m/%d" ctime(name of your date column) as NEWDATE

substitute the %Y/%m/%d for whatever time periods you want to show up.

0 Karma

Lazarix
Communicator

The alternative is to define a search macro for it instead.
I've found that there is no global way for Splunk to parse MySQL or MSSQL timestamps

0 Karma

sbsbb
Builder

ok that will always work, the same for a to_char in sql... but I doesn't want to make that for each date field and for each query...

0 Karma

sbsbb
Builder

I've found some possibility in oracle : alter session set NLS_DATE_FORMAT='DD-MON-YY'

But I'm not able to use that command in DBquery

0 Karma

sbsbb
Builder

I've found some possibility in oracle :
alter session set NLS_DATE_FORMAT='DD-MON-YY'

But I'm not able to use that command in DBquery

0 Karma
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!

At .conf26, Don’t Just See What’s Next. Help Shape It at Innovation Labs.

Long before a new capability reaches the keynote stage, it begins as an idea waiting to be tested. At ...

Forwarder Topology Guidance: Intermediate HF vs Intermediate UF

Why Universal Forwarders Should Not Be Used as Intermediate Forwarders A practical Splunk forwarding topology ...

Data Management Digest – August 2026

Data Management Digest   Welcome to the August 2026 edition of Data Management Digest! August was a big month ...