Splunk® DB Connect

Release Notes

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.

Release notes

Version 3.11.0 of Splunk DB Connect was released on October 28, 2022.

New and changed features

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

  • Ability to create identities using Hashicorp Vault
  • Password synchronization when using CyberArk and HashiCorp identities
  • Password updates when updating CyberArk or Hashicorp identities
  • Server reboot progress notification when updating keystore password
  • UX improvements
  • Bug fixes

Fixed issues

Version 3.11.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-11-15 DBX-5714 warning on startup for "Invalid key in stanza" for key "run_only_one" on Splunk 8.1.x
2022-10-25 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
2022-10-13 DBX-5706 Issue with Input names containing dashes "-"

Known issues

Version 3.11.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-04-17 DBX-5788 Not allow to edit the description field in the Input configuration
2023-03-23 DBX-5766 Unable to write records java.net.SocketTimeoutException: Read timed out

Workaround:
Set dedicatedIoThreads = 8 in $SPLUNK_HOME/etc/system/local/inputs.conf

Allows the HEC to process multiple requests simultaneously, must not be greater than the number of CPU cores.

Set parallelIngestionPipelines = 2 in $SPLUNK_HOME/etc/system/local/server.conf

Multiple pipeline sets increase forwarder throughput and allow the forwarder to process multiple inputs simultaneously.

Set batch_upload_size = 500 in $SPLUNK_HOME/etc/apps/splunk_app_db_connect/local/db_inputs.conf

Number of rows to be uploaded to HEC in one batch.

Set maxHecContentLength = 5242880 in $SPLUNK_HOME/etc/apps/splunk_app_db_connect/local/dbx_settings.conf

Maximum size of each batch when uploading it to the HEC.

Note: A patch will be released with version 3.12.2.

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
Last modified on 20 July, 2023
  Release notes

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


Was this topic useful?







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