Topics

Added support for upgrading from 2.x to 3.0.x. See the Upgrading from 2.x versions section of our Installation manual for how to migrate from 2.x to 3.0.x
Improved typeahead text in SplunkWeb search box
European dates are now supported
Added a Re-sync button to the LDAP configuration page in SplunkWeb
ODBC is replaced with DBI as the way to get database data into Splunk. The DBI scripts to pull database data are not yet bundled with Splunk, but they will be soon. Once those scripts are in, you'll use the new admin command to administer database inputs

Resolved issues from 3.0

Report and stats data now produces useful output from the CLI ( using "-format csv" produces csv formatted data)
View All link now links to the correct index
All Permalinks now link correctly
Added month to parsed date and time string
Added support for SNMP alerting. See the Sending SNMP traps page in our Admin manual for how to set up SNMP alerting
Fixed the issue that caused Splunk to not shut down if 127.0.0.1 was not bound to localhost
Savedsearches with spaces now correctly create alerts
Fixed issue where comma separated output wasn't escaping values- use the python application in the REST API to correct (REST API documentation in our Developer manual)
Brackets are now allowed in stanza names in .conf files
Fixed the archive processor. Compressed logs are now processed properly
Fixed bug that caused incorrect reporting (returning zero results) when there is click-navigated data present and the search box in SplunkWeb is empty
Reporting now reports correctly based on the click-navigated data
Files less than 256 bytes are now properly handled by the indexer

A small amount of database configurations with Active Directory are known to not work with Splunk's LDAP authentication. This will be fixed in 3.0.2
If you are using native install packages, install will appear to overwrite your $SPLUNK_HOME/etc directory. There is a backup, look here for directions to recover

Start | Prev: Known Issues | Next: 3.0