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!

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...

Shape the Future of Splunk: Join the Product Research Lab!

Join the Splunk Product Research Lab and connect with us in the Slack channel #product-research-lab to get ...

Auto-Injector for Everything Else: Making OpenTelemetry Truly Universal

You might have seen Splunk’s recent announcement about donating the OpenTelemetry Injector to the ...