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.13.0 of Splunk DB Connect was released on May 5, 2023.

New and changed features

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

  • High availability of DB Connect on top of Splunk Enterprise with a Search Head Cluster
  • Setup HTTP Event Collectors from the UI
  • Install JDBC Add-ons from the DB Connect application
  • Remove connection timezone from the UI
  • Checkpoint query validation enhancements
  • UI enhancements
  • Bug fixes

Fixed issues

Version 3.13.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
2023-04-18 DBX-5788 Not allow to edit the description field in the Input configuration

Known issues

Version 3.13.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-09-06 DBX-5812 Issues in the dbxlookup query having the '$' sign in it

Workaround:
  1. Use replace command to avoid $ symbol | eval <field> = replace(<field> , "\\$" , "<DOLLAR-SYMBOL>").
  2. Set the $ symbol again after the dbxlookup as | rex mode=sed field=<field> "s/<DOLLAR-SYMBOL>/$/g".

Also, as a second way, you can ingest the data from databases into Splunk using DB Connect's Inputs feature and aggregate the data in the SPL query by using join command.

2023-07-20 DBX-5800 Indexing time is not converted to server time zone using database column as indexing time
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.

Third-party software attributions

Some of the components included in this add-on are licensed under free or open source licenses. We wish to thank the contributors to those projects.

A complete listing of third-party software information for this add-on is available as a Document file for download:
Splunk DB Connect third-party software credits.

Last modified on 15 September, 2023
 

This documentation applies to the following versions of Splunk® DB Connect: 3.13.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