• What's New
  • What's new in Splunk 3.1
    • Form search
    • Search language simplification
    • Archiving
• Known Issues
  • Known Issues for release 3.1.5
    • General Issues and Recommendations
    • Search & Navigation
    • Administration
    • Toolbar
• Changelogs by Version
  • 3.1.5
    • Resolved issues from 3.1.4
    • New issues in this release
  • 3.1.4
    • New features
    • Resolved issues from 3.1.3
    • New issues in this release
  • 3.1.3
    • Resolved issues from 3.1.2
    • New issues in this release
  • 3.1.2
    • Resolved issues from 3.1.1
    • New issues in this release
  • 3.1.1
    • New features
    • Resolved issues from 3.1
    • New issues in this release
  • 3.1
    • New features
    • Resolved issues from 3.0.x
    • New issues in this release
• Credits
  • Credits
  • APSW
  • boost
  • elementree
  • expat
  • fpconst
  • gadfly
  • libarchive
  • libiconv
  • libxml2
  • libxslt
  • log4py
  • numeric
  • openLDAP
  • OpenSSL
  • pcre
  • popt1.7
  • pyopenssl
  • pysqlite
  • python
  • pyxml
  • SOAPppy 0.11.6
  • sqlite
  • twisted
  • xmlwrapp 0.5.0
  • zope
  • zlib

3.1.5

Resolved issues from 3.1.4

• Legitimate searches below malformed searches in your savedsearch.conf file are no longer ignored.
• Reports and graphs are now correctly displayed on the dashboard. However, in some instances dashboards may still not display properly. If you upgrade to 3.1.5 and your dashboards still do not display properly, work around this issue by deleting, recreating, and re-adding your searches to the dashboards.
• Email alert attachments now contain all results from the associated search.
• Splunk will now run correctly even if you have non-database buckets in colddb.
• LDAP usernames and mapping attributes are now interpreted by Splunk in a case-insensitive manner.

New issues in this release

• If you specify a non-numeric value for process_every_n_events in $SPLUNK_HOME/etc/bundles/local/eventdiscover.conf, Splunk will crash.
• Users who are not members of the admin role cannot save a report search and add it to a dashboard. To work around this, a user who is a member of the admin role can create the search and share it. Non-admin users can then add that search to their dashboards.