Splunk® User Behavior Analytics

Release Notes

This documentation does not apply to the most recent version of Splunk® User Behavior Analytics. For documentation on the most recent version, go to the latest release.

Fixed Issues in Splunk UBA

This version of Splunk UBA was released on September 30, 2021 and fixes the following issues.


Date resolved Issue number Description
2022-03-18 UBA-14516 Health Monitor - An error occurred while retrieving data - Error from /uba/monitor Invalid Json response: Error in getting the response Parameters: {"queryStatus":true,"queryDataQualityStatus":true}
2021-09-10 UBA-14702 Custom Models TimeSeries models have not executed since upgrade to 5.0.4.1
2021-08-31 UBA-14669 UBA - Multiple Errors Status code DS-1, Status code DS-5, Status code DS_LAGGING_WARN
2021-08-30 UBA-14629 Need to handle upgrade for TimeSeries Custom Model
2021-08-27 UBA-14251 UBA triggers Anomalies Related to Job Search When Users Visit Unrelated Sites
2021-08-25 UBA-14675 Error when upgrading the standby system
2021-08-24 UBA-14379 Discrepancy between Threats and notable events in ES
2021-06-15 UBA-14390 New threats sent to ES have incorrect "status" field value
2021-05-26 UBA-14493 IP change steps not working
2020-12-22 UBA-14339 Custom Models TimeSeries model errors associated with missing skipOldAnomaliesThreshold
Last modified on 18 March, 2022
Known Issues in Splunk UBA   Remove Log4j from all Splunk UBA deployments

This documentation applies to the following versions of Splunk® User Behavior Analytics: 5.0.5


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