Release notes
Fixed issues
Fixed date | Defect number | Description |
---|---|---|
2017-05-15 | DBX-4109 | The maximum 100 rows of event data gets inserted when using output data from a saved search. |
2017-05-15 | DBX-4093 | Disabling a lookup causes the lookup to disappear from the UI and you can no longer edit existing lookups. |
2017-05-15 | DBX-4083 | The inputs migrated from DB Connect 2 get wrapped regardless of the query wrapping settings in the original release. |
Known issues
Publication date | Defect number | Description |
---|---|---|
2017-05-29 | DBX-4154 | Inputs from table containing Non-ASCII characters are not indexed correctly by Splunk DB Connect. Workaround: User needs to set the JVM option as |
2017-05-08 | DBX-4124 | The task server will not restart without restarting Splunk if the system Java is not supported. Restarting Splunk will restart the task server using the specified and supported local Java. |
2017-05-15 | DBX-4139 | If the HEC setting is disabled, it will not be enabled automatically when you restart task server. You have to enable the HEC manually under Splunk settings. |
2017-05-15 | DBX-4081 | Timezone override in props.conf is ignored. Workaround:The JVM option user.timezone needs to set to GMT. To set this option go to configuration>settings>JVM options, add following option -Duser.timezone=GMT |
2017-05-15 | DBX-4032 | The migration scripts copies all the jar files under $SPLUNK_HOME/etc/apps/splunk_app_db_connect/bin/libs of DB Connect 2 to $SPLUNK_HOME/etc/apps/splunk_app_db_connect/drivers of DB Connect 3 even some of them are not JDBC drivers.
|
2017-05-15 | DBX-4024 | The 'testQuery' setting in db_connection_types.conf is no longer working in DB Connect 3.
|
2017-04-16 | DBX-4019 | Events indexed by DB Connect 3.0.0 do not include the automatic time fields date_hour, date_minute, date_year, date_month, and date_mday. Additionally, props.conf overrides cannot be used to alter the indexed time. Workaround:
Use calculated fields to extract those fields on search time: |
2017-02-14 | DBX-3841 | DB Connect 3.0.0 does not support a new installation of Splunk Add-on for MySQL or Splunk Add-on for Nagios Core. Additionally, the template files included in Splunk Add-on for McAfee, Splunk Add-on for Oracle Database, and Splunk Add-on for Microsoft SQL will not work if copied into DB Connect 3. |
2017-02-09 | DBX-3831 | Task server startup error messages are unclear when user does not have write access to checkpoint folder |
2017-02-08 | DBX-3823 | When upgrading from version 2.4 to 3.0 on Ubuntu, the RPC task server is not reliably killed and may prevent starting the new server. |
2017-02-09 | DBX-3829 | Connection used by scheduled jobs will not be refreshed when identity was updated. |
2017-01-26 | DBX-3809 | A disabled output definition can still be used in an alert action. |
2017-01-21 | DBX-3783 | If an input has just been deleted, a new input with the same name cannot be created. |
2017-01-20 | DBX-3781 | Once a column has been chosen as input timestamp, current index time option cannot be chosen. |
2017-01-20 | DBX-3779 | [MySQL] The connection fails when the hostname field contains a space character. |
2017-01-20 | DBX-3778 | app.conf and dbx_settings.conf are not replicated in search head cluster environments |
2017-01-19 | DBX-3746 | customized JAVA_HOME setting is ignored by dbxoutput when launched from modular alert. |
2017-01-13 | DBX-3720 | Informix and DB2 drivers conflict. |
2017-01-09 | DBX-3706 | Creating an input with an already-used name does not cause a warning message. |
2016-12-16 | DBX-3616 | Output is not supported when using Cisco CIS JDBC driver. |
2016-12-15 | DBX-3613 | Could not load tables with no category/schema from CIS. |
2016-12-15 | DBX-3610 | "TIMESTAMP WITH TIME ZONE" and "TIMESTAMP WITH LOCAL TIME ZONE" can not be used in rising column input. |
2016-12-06 | DBX-3570 | Reload API will reload both output and input tasks. |
2016-11-01 | DBX-3371 | Incorrect output result preview for multiple values |
2016-10-11 | DBX-3256 | Failure to enable client certification because a key or certificate is missing in local/certs does not produce an error message. |
2016-04-21 | DBX-2820 | RPC server failure provides incomplete information in the error log. |
2016-02-12 | DBX-2623 | v1 to v2 migration scripts fail on special characters. |
Credits |
This documentation applies to the following versions of Splunk® DB Connect: 3.0.3
Feedback submitted, thanks!