Splunk® Enterprise

Release Notes

Splunk Enterprise version 8.0 is no longer supported as of October 22, 2021. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see How to upgrade Splunk Enterprise.
This documentation does not apply to the most recent version of Splunk® Enterprise. For documentation on the most recent version, go to the latest release.

Fixed issues

Splunk Enterprise 8.0.3 was released on April 1, 2020. This release includes fixes for the following issues.

Issues are listed in all relevant sections. Some issues might appear more than once. To check for additional security issues related to this release, visit the Splunk Security Portal.

Search issues

Date resolved Issue number Description
2020-03-05 SPL-184223, SPL-181448 mstats - The same search query with mstats produces different results each time it is run
2020-03-04 SPL-184234, SPL-183532 Search head performance degraded after upgrade from 8.0.2- to 8.0.2 and 7.3.4- to 7.3.4
2020-03-02 SPL-183469, SPL-182410 IDX crashing Frequently with Crashing thread: BatchSearch
2020-03-01 SPL-183804, SPL-182397, SPL-162429 Search fails with "Error in 'table' command: Invalid argument:"
2020-02-14 SPL-183324, SPL-141209 batch mode and cursored search return different results when the search string contains index-scoped time ranges which conflict with the time-picker time range
2020-02-05 SPL-181525, SPL-182841, SPL-182404, SPL-182843 Issue with maps viz, geostats in combination with |append or |inputlookup append=t, some pie chart not showing on map
2020-01-17 SPL-181834, SPL-181612 Searching for lookup default_match - Consider wildcards
2020-01-13 SPL-169655, SPL-173709, SPL-171705, SPL-176220, SPL-175476, SPL-175474 After Upgrade Fields not displaying unless order of fields match fields_list in transforms.conf
2020-01-12 SPL-181155, SPL-177255 Searching for lookup default_match value includes default_match value in lispy

Saved search, alerting, scheduling, and job management issues

Date resolved Issue number Description
2020-03-02 SPL-182489, SPL-179997 Datamodel missing fields from | datamodel Command
2020-02-03 SPL-182429, SPL-159082 Scheduled search producing warning for Invalid Cron Schedule ss_id=";;"

Charting, reporting, and visualization issues

Date resolved Issue number Description
2020-03-10 SPL-179770, SPL-177890 Pagination Issue in dashboard
2020-02-20 SPL-176861, SPL-175517 fieldformat value in dashboard shows as epoch time until it sorted
2020-02-16 SPL-183077, SPL-181033 _time is shown as GMT on Visualization when Time zone is set to default on Windows
2020-02-11 SPL-182113, SPL-179348 autoLB not switching IDX when reaching frequency limit
2020-02-05 SPL-181525, SPL-182841, SPL-182404, SPL-182843 Issue with maps viz, geostats in combination with |append or |inputlookup append=t, some pie chart not showing on map
2020-01-27 SPL-181933, SPL-181372 Bootstrap modal is not working in dashboard

Data model and pivot issues

Date resolved Issue number Description
2020-03-02 SPL-182489, SPL-179997 Datamodel missing fields from | datamodel Command

Indexer and indexer clustering issues

Date resolved Issue number Description
2020-02-25 SPL-183851, SPL-182286 Intermittent crashes due to corrupted buckets slowing down fixup tasks - Follow up of SPL-182014
2020-02-03 SPL-182121, SPL-182014 60 Indexers in a cluster are crashing sporadically -Crashing thread: cachemanagerDownloadExecutorWorker-10
2020-01-30 SPL-182233, SPL-180406 Cluster Master UI states search and replication factors SF/RF are not met, but there are no fixup tasks listed
2020-01-27 SPL-181617, SPL-180200 Some cluster peers did not try to restart when new bundle was applied

Distributed search and search head clustering issues

Date resolved Issue number Description
2020-03-06 SPL-178006, SPL-175784 Application does not exist error for bundle application with full mode when deploy app contains an empty default folder
2020-03-06 SPL-184164, SPL-173029 KV store backup/restore - large collection hangs at "Busy" status when trying to restore from a backup
2020-03-06 SPL-178008, SPL-174856 Out-of-sync issues can occur when using full or local_only push modes to push configurations from the deployer to the search head cluster
2020-03-04 SPL-183475, SPL-181508 Negative values returned by one SH in Average KVstore Latency graph in MC
2020-02-14 SPL-179682, SPL-177024 SearchOrchestation framework should not run subsearches multiple times.
2020-02-10 SPL-181954, SPL-181703 Alert suppression removal during captaincy changes may cause SHC instability.

Universal forwarder issues

Date resolved Issue number Description
2020-02-27 SPL-184043, SPL-157269 High CPU usage originating from Splunk UF on macOS devices

Splunk Web and interface issues

Date resolved Issue number Description
2020-02-19 SPL-183229, SPL-178521 idpCert.pem certificate gets malformed using Metadata XML File
2020-02-16 SPL-183077, SPL-181033 _time is shown as GMT on Visualization when Time zone is set to default on Windows
2020-02-13 SPL-182060, SPL-178515 Unable to view SAML settings when idpCerts is deleted
2020-02-07 SPL-182773, SPL-182139 Degradation in Web UI performance with large number of Knowledge Objects and Users
2020-02-05 SPL-182638, SPL-181165 Splunkweb does not start as per repro but we fail to report it failed to start.

REST, Simple XML, and Advanced XML issues

Date resolved Issue number Description
2020-02-07 SPL-182773, SPL-182139 Degradation in Web UI performance with large number of Knowledge Objects and Users

Authentication and authorization issues

Date resolved Issue number Description
2020-02-19 SPL-183229, SPL-178521 idpCert.pem certificate gets malformed using Metadata XML File
2020-02-13 SPL-182060, SPL-178515 Unable to view SAML settings when idpCerts is deleted

PDF issues

Date resolved Issue number Description
2020-03-06 SPL-183432, SPL-182193 PDF - timecharts are being cut when sent as PDF

Admin and CLI issues

Date resolved Issue number Description
2020-03-10 SPL-183144, SPL-184201 Create/edit field transformation after toggling type throws error
2020-03-06 SPL-181948, SPL-181290 Splunk does not set realtime_schedule to 0 after enabling summary indexing for a scheduled report

Uncategorized issues

Date resolved Issue number Description
2020-03-13 SPL-177345, SPL-170703 splunkd.log "ERROR SearchParser - Missing a search command before '*'" error message without context
2020-03-05 SPL-181178, SPL-181055 Floating numbers from dsfjob eval function
2020-03-05 SPL-183328, SPL-181223 When enabling CORS support HTTP headers are rejected
2020-02-27 SPL-183394, SPL-182112 After upgrading HWF to 8.0.0~8.0.2, useAck causing duplicate data.
2020-02-21 SPL-183089, SPL-132957 Report created by user name with space in can not be accelerated
2020-02-19 SPL-183180, SPL-179817 scheduled view object not deleted when source dashboard deleted
2020-02-18 SPL-181717, SPL-178172 Disabling replication of kvstore collection for automatic lookup causes "Could not load lookup=..." errors to appear
2020-02-14 SPL-183342, SPL-180575 Splunk streaming cli RealTime searches consume high memory and don't stream results until Job finalizes
2020-02-13 SPL-181055, SPL-181178 Eval operations in DFS are rounding results to the nearest integers instead of displaying results as floating point numbers.
2020-02-06 SPL-182939, SPL-172272 Language localization needs to apply for placeholder 'Username' and 'Password' text on login page
2020-01-27 SPL-182047, SPL-170497 Updating HEC turns on useACK (breaks input)
2020-01-23 SPL-180432, SPL-168459 Splunkd Server Memory growth over time on ES search head
2020-01-23 SPL-181465, SPL-172622 Cluster map visualization is not accurate after upgrade to 7.2.x
2020-01-17 SPL-181464, SPL-165762 Invalid latest_time: latest_time must be after earliest_time when DST is reached
Last modified on 16 December, 2020
Timestamp recognition of dates with two-digit years fails beginning January 1, 2020   Deprecated and removed in version 8.0

This documentation applies to the following versions of Splunk® Enterprise: 8.0.3


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters