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
Get Updates on the Splunk Community!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...