Splunk Search

DBConnect fetch not to consider latest value of rising column

pradeepkumarg
Influencer

The rising column I'm using is a time stamp and at times there are many records with the same value and if the fetch happens in the middle of those records, DBConnect is missing the rest of the records coming with the same value.

How can I limit the fetch not to consider the latest value so that all of them are fetched in the next run.

Example rising column value - dateUpdated - 2014-08-05 13:39:00.0

0 Karma
1 Solution

pradeepkumarg
Influencer

pradeepkumarg
Influencer

I found the answer mentioned in the below thread solves the purpose

http://answers.splunk.com/answers/68699/database-table-doesnt-have-rising-column-totally

Get Updates on the Splunk Community!

Splunk Certification Support Alert | Pearson VUE Outage

Splunk Certification holders and candidates!  Please be advised of an upcoming system maintenance period for ...

Enterprise Security Content Update (ESCU) | New Releases

In September, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...

New in Observability - Improvements to Custom Metrics SLOs, Log Observer Connect & ...

The latest enhancements to the Splunk observability portfolio deliver improved SLO management accuracy, better ...