All Apps and Add-ons

DBConnet V3 "rising column" execution schedule

thunder_wu
Path Finder

After defining a "rising column" for the dbinput query, then dbinput will run the defined query to load data. How is the schedule for execution?

select * from table A where fieldX > ?

If it take less than 1 second to run the query, does it mean the next run will be kicked off right after the previous run? Any configuration for waiting time before kicking off next one?

 

 

Labels (2)
Tags (1)
0 Karma
1 Solution

Richfez
SplunkTrust
SplunkTrust

It's in the installation and configuration docs.

https://docs.splunk.com/Documentation/DBX/3.4.0/DeployDBX/Createandmanagedatabaseinputs#Parameter_se...

I generally see people use this at 60 seconds or higher Execution Frequency, but as long as the DB is fast, the DB connection is fast, and you don't mind wasting resources for no reason, you can go as low as you want.  🙂

Happy Splunking!

-Rich

 

View solution in original post

Richfez
SplunkTrust
SplunkTrust

It's in the installation and configuration docs.

https://docs.splunk.com/Documentation/DBX/3.4.0/DeployDBX/Createandmanagedatabaseinputs#Parameter_se...

I generally see people use this at 60 seconds or higher Execution Frequency, but as long as the DB is fast, the DB connection is fast, and you don't mind wasting resources for no reason, you can go as low as you want.  🙂

Happy Splunking!

-Rich

 

Get Updates on the Splunk Community!

[Live Demo] Watch SOC transformation in action with the reimagined Splunk Enterprise ...

Overwhelmed SOC? Splunk ES Has Your Back Tool sprawl, alert fatigue, and endless context switching are making ...

What’s New & Next in Splunk SOAR

Security teams today are dealing with more alerts, more tools, and more pressure than ever.  Join us on ...

Your Voice Matters! Help Us Shape the New Splunk Lantern Experience

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...