3.4.6
This documentation does not apply to the most recent version of Splunk.
This documentation applies to the following versions of Splunk:
3.4.6 , 3.4.8 , 3.4.9 , 3.4.10 , 3.4.11 , 3.4.12
3.4.6
The following issues are resolved in this release:
- File system change monitor (fschange) whitelist now works correctly as documented. (SPL-18079)
- File system change monitor input now accepts a custom host attribute. (SPL-16020)
- Failed bind to LDAP no longer causes saved searches to be disabled. (SPL-17732)
- An issue with upgrade during the "Perform migration and upgrade without previewing configuration changes? [y/n]" step has been resolved. (SPL-18193)
- UDP inputs now open correctly when SplunkDesktop and LightForwarder are disabled in Splunk Web.(SPL-17728)
- An issue with indexing lagging behind when using many forwarders has been resolved. (SPL-18858)
- The 'splunk clean eventdata' command now properly deletes cached items in Splunk Web and now properly cleans file system monitor data. (SPL-18504, SPL-18401)
- Non-Splunk directories under /defaultdb no longer cause instability. (SPL-18535)
- Splunk now reports disk usage correctly in Splunk Web. (SPL-17302)
- Show source now works correctly on Windows for events from remote sources. (SPL-18505)
- Extra spaces in
fieldactions.conf no longer cause display issues in Splunk Web. (SPL-16132)
- An issue on Windows with regex backslashes in props.conf has been resolved. (SPL-18262)
- An issue with the
splunkmon process has been resolved. (SPL-18272)
- Linebreaking is now handled correctly for XML files. (SPL-18034)
- LDAP group names containing ampersand (&) no longer result in a traceback. (SPL-16867) A follow-on issue with display of information in Splunk Web is still being worked.
- Exporting to CSV format now obeys the 'fields' command correctly. (SPL-16562)
- Admin users can now edit or delete saved searches owned by any other user. (SPL-18009)
- An issue with monitoring the 64-bit Windows ForwardedEvents event log has been resolved. (SPL-18766)
- An issue with the stability of
splunk-optimize has been resolved. (SPL-18712)
- CLI searches now correctly process non-ASCII characters in search results. (SPL-18579)