Getting Data In

Splunk doesn't recognize timestamp properly when importing data from DB

ArsenyKapralov
Path Finder

Hi

I'm importing simple events from Oracle table. I don't have specific field with timestamp in database table and while I'm trying to import data I have a GMT time in the timestamp except GMT+4 as my (and server) timezone should be.

I tried to fix this with such code in props.conf in etc/system/local but didn't succeed:

[sourcetype_name]
TZ=Europe/Moscow

How can I fix this and make correct timestamps?

0 Karma

pmdba
Builder

If your database is on the correct time zone and you haven't figured out any other way to get Splunk to adjust, I'd recommend adding the timestamp to your SQL query, based on sysdate, so that it comes into Splunk with the proper local timezone adjustment:

select to_char(sysdate,'DD-MM-YYYY HH24:MI:SS') "time", ... 
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!

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