All Apps and Add-ons

DB Connect Rising Column Missing Records

joesrepsolc
Communicator

Problem:
I am using DB Connect (v3) and pulling in some Oracle OEM metrics. Finding that once I start using the rising column feature, based on a timestamp in the Oracle OEM tables, I'm dropping data.

Observations:
Some OEM metrics pull every 10min, others every 15min from the database. When I re-pull the data its incredible consistent (see image). I pull the DB Connect input every 5min based on a timestamp field in the data. I'm guessing that the rising column timestamp is being updated to now, when the raw data hasn't even made it into the Oracle metrics tables yet. The later on, when Oracles metric tables get the data, but that timestamp has already passed and DB Connect is no longer looking back in time for that data. If I re-pull all the source data from the table again, I see all the data is there, I'm just missing it with DB Connects rising column configuration.

Anyone know of a way for me to use an "offset" or somehow look back in time long enough to still ingest these records with DB connect? Not sure how to fix this and missing data in Splunk.

alt text

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Monitoring AI Agents with Splunk Observability Cloud

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...

[Puzzles] Solve, Learn, Repeat: Tiling

This puzzle (first published here) is based on finding groups of tessellated tiles (inspired by floor tiles I ...

SOK it to Me: Top 3 Benefits of Using Splunk Operator on Kubernetes that’ll Make ...

    Thursday, July 9, 2026  |  11:00AM–12:00PM PDT Duration: 1 hour (includes Q&A) Managing can feel like a ...