Splunk® DB Connect

Release Notes

Acrobat logo Download manual as PDF


This documentation does not apply to the most recent version of Splunk® DB Connect. For documentation on the most recent version, go to the latest release.
Acrobat logo Download topic as PDF

Release notes

Version 3.10.0 of Splunk DB Connect was released on August 29, 2022.

New and changed features

Version 3.10.0 of Splunk DB Connect contains the following new or changed features:

  • Improved scalability on Splunk Cloud Search Head clusters (Noah only, Enterprise and Classic will execute only inputs/outputs defined on particular node)
  • Added support for the latest version of java 17 and 18
  • Added support for the AdoptOpenJDK
  • Added support for the Zulu JDK
  • Added functionality to change your key store password from the UI
  • Bug fixes

Fixed issues

Version 3.10.0 of Splunk DB Connect fixes the following issues. If no issues appear below, no issues have yet been fixed.


Date resolved Issue number Description
2022-07-11 DBX-5655 dbxlookup not populating any table columns without the 'output' keyword being specified
2022-07-07 DBX-5654 User is unable to connect to CyberArk while using Splunk App for DB Connect.
2022-07-07 DBX-5666 Health Check: dbxquery command conf's filename property should be java.path, but it is: dbxquery_bridge.py now.
2022-05-17 DBX-5653 dbxquery command doesn't respect RBAC

Known issues

Version 3.10.0 of Splunk DB Connect contains the following known issues. If no issues appear below, no issues have yet been reported.


Date filed Issue number Description
2023-05-26 DBX-5787 Inputs containing interval in a Non Standard cron expression cause failures

Workaround:
Splunk Modular Inputs only support Standard cron expressions, as DB Connect does.

To fix the issue you can modify the cron expression for the affected Input in $SPLUNK_HOME/etc/apps/splunk_app_db_connect/local/inputs.conf and $SPLUNK_HOME/etc/apps/splunk_app_db_connect/local/db_inputs.conf, then restart Splunk.

You can also fix it by following the steps below:

  1. Disable the Input.
  2. Adjust Interval to be a Standard cron expression.
  3. Enable the Input.
2023-03-28 DBX-5771 Disable/enable connections cause "Unable to process JSON" error

Workaround:
In case the problem persists after migrating to a version that is supposed to be free of this bug, you will need to clear your browser caches.
2022-12-08 DBX-5789 Allow Inputs and Outputs names to contain dots characters
2022-11-30 DBX-5790 Database account get locked after password rotation
2022-10-27 DBX-5728 Keystore password getting tampered for non US-ASCI customers
2022-10-19 DBX-5715 Upgrading DBX to 3.10 fails with 'Cannot run program "keytool": error=2, No such file or directory' when $JAVA_HOME isn't part of $PATH

Workaround:
add $JAVA_HOME to $PATH for the user running splunk so that the command "keytool" can be found in $PATH

or upgrade to DBX 3.11+ instead

2022-10-19 DBX-5714 warning on startup for "Invalid key in stanza" for key "run_only_one" on Splunk 8.1.x

Workaround:
None needed, this option is for later splunk versions, but doesn't break anything on older ones, it's safe to ignore the warning.
2022-10-10 DBX-5706 Issue with Input names containing dashes "-"
Last modified on 20 July, 2023
  NEXT
babel

This documentation applies to the following versions of Splunk® DB Connect: 3.10.0


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