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.2.0 of Splunk DB Connect was released on October 22, 2019.

New and changed features

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

  • Support for Microsoft JDBC up to version 7.2.1.
  • Support for both Python 3 and Python 2 environments.
  • New optional configuration stanzas in $SPLUNK_HOME/etc/apps/splunk_app_db_connect/local/dbx_settings.conf that can be enabled to make Splunk DB Connect more efficient in a Splunk platform clustered environment:
    • hecUris: A list of HEC servers/ports, separated by comma.
    • hecToken: A HEC token listing, when it is the same HEC token, configured on multiple indexers.
  • Enhanced backward compatibility support for indexed events. Users can now keep indexed event field names the same as in DBX 2.x.

Fixed issues

Date resolved Issue number Description
2019-08-02 DBX-4585 Output does not work if column's name contains special characters i.e. dot, space

Known issues

Version 3.2.0 of Splunk DB Connect contains the following known issues:


Date filed Issue number Description
2020-04-29 DBX-5040 tail_rising_column_init_ckpt_value missing from spec file, creating "Invalid key in stanza" warning on startup of splunk

Workaround:
add the following line underneath the [<name>] heading in $SPLUNK_HOME/etc/apps/splunk_app_db_connect/README/db_inputs.conf.spec:
tail_rising_column_init_ckpt_value = <string>
2020-03-10 DBX-4968 DB Connect 3.2.0 checks for a uniqueKey parameter when using UPSERT when it does not need to
2019-08-05 DBX-4799 DB Connect 3.1.4 Not working with Solaris Adaptive Server Enterprise/16.0 SP02 PL07
2018-06-01 DBX-4616 Need to add extra backlash (escape) in GUI to be able to get literal backslash in query, but this breaks the query in the configuration file, preventing it from running after saving

Workaround:
Create query using GUI, then edit after in configuration file to remove extra backslash

 

Last modified on 15 December, 2020
  NEXT
CLogger

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