Splunk® DB Connect

Deploy and Use Splunk DB Connect

Acrobat logo Download manual as PDF

Acrobat logo Download topic as PDF


Instead of configuring inputs, outputs and lookups in one inputs.conf file, in DB Connect 3, inputs, outputs and lookups are configured in discrete files db_inputs.conf, db_outputs.conf and db_lookups.conf. This increases configurability and performance.

Note: Modifying inputs.conf file stanzas outside of the DB Connect app, such as in the search app or manager context, is not supported.

# @copyright@
# The file contains the specification for all db connect modular inputs
# # server - the modular input that runs java server

config_file = <string>
# required
# If the value is an absolute path, taskserver will treat it as the config_file path.
# If the value is a relative path, taskserver will prepend SPLUNK_HOME and generate the actual config_file path.
# On UNIX systems, a path is absolute if its prefix is "/".
# On Microsoft Windows systems, a path is absolute if its prefix is a drive specifier followed by "\\", or if its prefix is "\\\\".

keystore_password = <string>
# required
# Specifies the java keystore password
# The keystore contains the certificate to set up the HTTPS connection to the
# task server.

interval = <integer>
# required
# Specifies the interval used by Splunkd to monitor Java server. If Java process
# is stopped, Splunkd will spawn a new Java process.
Last modified on 24 February, 2021

This documentation applies to the following versions of Splunk® DB Connect: 3.4.0, 3.4.1, 3.4.2

Was this documentation topic helpful?

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters