Release notes
New and changed features
Version 3.1.3 of Splunk DB Connect does not have any new or changed features.
Fixed issues
Date resolved | Issue number | Description |
---|---|---|
2018-03-01 | DBX-4454 | Invalid rising column index value when non-indexable columns are skipped |
2018-02-15 | DBX-4527 | dbxquery cannot start on Splunk Enterprise 7+ if users set a time zone in their preferences |
Known issues
Date filed | Issue number | Description |
---|---|---|
2018-11-21 | DBX-4707 | Update dropwizard dependency to fix CVE |
2018-08-22 | DBX-4638 | Empty host on the connection and the input will fail the input |
2018-08-22 | DBX-4637 | HEC error message is not logged |
2018-07-16 | DBX-4623 | Compatibility issue with splunk_app_db_connect 3.1.3 and TA-Proofpoint-TAP 1.3.117 keeps DBX from loading. Workaround: Remove or Downgrade TA-Proofpoint-TAP |
2018-06-04 | DBX-4618 | Host metadata can be missing in HTTP events |
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-22 | DBX-4614 | DBX 3.1.3 inputs throwing "HTTP Error 400: Bad Request" error when large field length is encountered Workaround: Skip the record containing the large record or take a substring of the column. Upgrade Splunk: - from 7.0.x to 7.0.5 - from 7.1.x to 7.1.3 - from 7.x to 7.2.0 |
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-04-18 | DBX-4603 | On Windows systems, hitting debug/refresh endpoint with DB Connect installed makes splunkweb not restart Workaround: Restart splunk through services.msc |
2018-03-27 | DBX-4589 | java.io.IOException: Push back buffer is full Workaround: In some cases reducing the amount of data returned, by limiting the timeframe of returned events in the search will work |
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-19 | DBX-4387 | Splunk cannot be restarted via web interface, deployer or deployment server on Windows Workaround: Use the CLI or the services control panel (services.msc) to restart Splunk |
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 |
CLogger |
This documentation applies to the following versions of Splunk® DB Connect: 3.1.3
Feedback submitted, thanks!