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.1.4 of Splunk DB Connect was released on January 9, 2019.

New and changed features

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

  • Support for OpenJDK 8
  • A retry mechanism for sending data to the HTTP event collector (HEC)
  • Updated user experience for Splunk 7.1.x compatibility
  • Support for time range in the lookup page search bar
  • Support for Postgres driver 42.2.5
  • Support for Splunk 7.2.x

Fixed issues

Date resolved Issue number Description
2018-11-29 DBX-4589 java.io.IOException: Push back buffer is full
2018-11-22 DBX-4707 Update dropwizard dependency to fix CVE
2018-11-22 DBX-4623 Compatibility issue with splunk_app_db_connect 3.1.3 and TA-Proofpoint-TAP 1.3.117 keeps DBX from loading.
2018-11-08 DBX-4603 On Windows systems, hitting debug/refresh endpoint with DB Connect installed makes splunkweb not restart
2018-11-08 DBX-4588 All source types from props.conf does not show on DBX 3.1.1
2018-11-07 DBX-4638 Empty host on the connection and the input will fail the input
2018-10-11 DBX-4637 HEC error message is not logged
2018-04-05 DBX-4387 Splunk cannot be restarted via web interface, deployer or deployment server on Windows

Known issues

Version 3.1.4 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>
2019-09-30 DBX-4838 dbxquery returning wrong results
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

 

2018-05-16 DBX-4612 Cron expression using both "day of month" and "day of week", isn't supported when used in "Execution Frequency"

Workaround:
Don't use combination of "day of month" and "day of week" field. In some cases you could just use the day of week for the scheduling, depending on where the data is coming from. Although this might not be applicable to all situations.
2018-03-13 DBX-4585 Output does not work if column's name contains special characters i.e. dot, space

Workaround:
Edit the conf file to wrap the field with the DB quote identifier such as back quote for MySQL or square brackets for SQL Server
2017-09-08 DBX-4436 dbxquery fails with an OutOfMemoryError when returning large data set i.e. GB of data
2017-07-16 DBX-4382 Output is slow when upsert is enabled
2017-07-12 DBX-4377 File permission check returns false positive on Windows
2017-03-26 DBX-3985 Kerberos health check is not supported in windows
2016-12-14 DBX-3610 "TIMESTAMP WITH TIME ZONE" and "TIMESTAMP WITH LOCAL TIME ZONE" can not be used in rising column input

Workaround:
Use cast/convert to convert the timestamp with timezone to a timestamp
2016-10-18 DBX-3309 dbxquery command returns misordered columns
Last modified on 29 April, 2020
  CLogger

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


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