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_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 (C) 2005-2016 Splunk Inc. All Rights Reserved. # The file contains the specification for all db connect modular inputs # # server - the modular input that runs java server [server://<name>] config_file = <value> # If the value is an absolute path, taskserver will treate 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 = <value> # optional # Indicates what password the java keystore will be generated with interval = <int> # optional # Indicates the interval used by Splunkd to monitor Java server. If Java process is stopped, Splunkd will spawn a new Java process.
This documentation applies to the following versions of Splunk® DB Connect: 3.0.0, 3.0.1, 3.0.2, 3.0.3
Feedback submitted, thanks!