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!

Level Up Your .conf25: Splunk Arcade Comes to Boston

With .conf25 right around the corner in Boston, there’s a lot to look forward to — inspiring keynotes, ...

Manual Instrumentation with Splunk Observability Cloud: How to Instrument Frontend ...

Although it might seem daunting, as we’ve seen in this series, manual instrumentation can be straightforward ...

Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform

 Are you ready to revolutionize your IT operations? As digital transformation accelerates, the demand for ...