Deployment Architecture

Does data loss occur when using DBConnect if two records have the same timestamp?

julietjake
Explorer

Does data loss occur when using DBConnect if two records have the same timestamp?

For instance, if DBConnect only picks up the first record on first pass, would the second record with the identical timestamp be lost at the next polling interval as DBConnect is only looking for records with a later timestamp?

Splunk 6.1.5
DBConnect 1.1.6

Tags (1)
0 Karma

jcoates_splunk
Splunk Employee
Splunk Employee

Hi, that is a possibility when using time as a rising column if the records are coming in faster than the granularity level of your timestamp can represent. It's one of several reasons why I don't recommend using time as a rising column. Others include daylight savings time and locales.

If time's all you have to work with, then it's all you have, but row id's are way better.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...