All Apps and Add-ons

Time formatting issue while migrating dbConnect inputs from v1.1.5 to v3.1.2

pkeller
Contributor

I'm in the process of manually migrating over 100 database inputs from dbx 1.1.5 to 3.1.2 and have run into an issue with time formatting.

The dbx 1.1.5 query formats the date time fields as epoch, yet the same query formats the fields as: YYYY-MM-DD HH:MM:SS.NNN

The query is very small: (Oracle database)

SELECT (select sysdate from dual) as "collection_time", lastconnectiontime,agentname as "src_host", version FROM table_name

The output I get is:

[ dbConnect 3.1.2 ]
2018-04-06 09:12:00.958, collection_time="2018-04-06 02:12:00.0", LASTCONNECTIONTIME="2016-11-21 17:33:49.523", src_host="xxxxxxxxxxxx", VERSION="1.1.1.1"

[ dbConnect 1.1.5 ]
collection_time=1522980720.000 LASTCONNECTIONTIME=1479749629.523 src_host=xxxxxxxxxxxx VERSION=1.1.1.1

So, really two questions, the most important being, how do I adjust the 3.1.2 query so that I get the identical date/time format as the 1.1.5 query

The other question ... is it possible to modify the 3.1.2 query remove the leading date/time the query was executed either by a conf setting in the app or some other dbxquery option. (2018-04-06 09:12:00.958)

0 Karma

p_gurav
Champion

Can you tell what other input settings you are using?
Also did you follow migration steps given here:
http://docs.splunk.com/Documentation/DBX/latest/DeployDBX/MigratefromDBConnectv1

0 Karma
Get Updates on the Splunk Community!

Splunk Developers: Go Beyond the Dashboard with These .Conf25 Sessions

  Whether you’re building custom apps, diving into SPL2, or integrating AI and machine learning into your ...

Index This | How do you write 23 only using the number 2?

July 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this month’s ...

Splunk ITSI & Correlated Network Visibility

  Now On Demand   Take Your Network Visibility to the Next Level In today’s complex IT environments, ...