Release notes
Version 3.5.1 of Splunk DB Connect was released on April 16, 2021.
New and changed features
Version 3.5.1 of Splunk DB Connect contains the following new or changed features:
- Bug fixes.
Fixed issues
Version 3.5.1 of Splunk DB Connect fixes the following issues. If no issues appear below, no issues have yet been fixed.
Date resolved | Issue number | Description |
---|---|---|
2021-04-12 | DBX-5464 | DBX 3.4.2 tail_rising_column in db_inputs.conf not updating values on change |
2021-04-07 | DBX-5155 | Customer gets 'visualization not found' error when running queries in the SQL editor |
Known issues
Version 3.5.1 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 |
---|---|---|
2021-06-08 | DBX-5562 | Issue creating input using DB connect(3.5.1) with MySQL(8.0.x) |
2021-06-07 | DBX-5561 | The "Splunk Platform Upgrade Readiness App" and "Python Upgrade Readiness App" display a false positive result when running Splunk DB Connect. |
2021-05-27 | DBX-5548 | typo in dbx_app_migration.py causes issues with migration of inputs (DB_INPUTS_ALLOWED_LIST_3_0 // DB_INPUT_ALLOWED_LIST_3_0) Workaround: Change line 652 in ./bin/dbx_app_migration.py from: _add_create_stanza_action(service, "db_inputs", name, _filter_content(properties, DB_INPUT_ALLOWED_LIST_3_0), an_input.access) to _add_create_stanza_action(service, "db_inputs", name, _filter_content(properties, DB_INPUTS_ALLOWED_LIST_3_0), an_input.access) |
2021-04-30 | DBX-5515 | Changing the port from the default 9999 for dbxquery server breaks it, with error (Failed attempting to parse transport header: HTTP/1.1 400 HTTP/0.9 not supported) in search.log. Workaround: keep default port 9999. |
babel |
This documentation applies to the following versions of Splunk® DB Connect: 3.5.1
Feedback submitted, thanks!