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
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.