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!

Event Series: Splunk Observability Metrics Cost Optimization

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...