Fixed Issues in Splunk UBA
This version of Splunk UBA was released on January 22, 2020 and fixes the following issues.
Date resolved | Issue number | Description |
---|---|---|
2020-03-26 | UBA-13412 | Unable to create Anomaly Action rules when specifying filter - Error from /uba/anomalyRules Cannot read property 'body' of undefined |
2020-01-07 | UBA-12964 | User and device attributions time out and do not load |
2019-12-17 | UBA-13121 | Deactivated custom models may get "Last Execution Time per Model" indicator Error |
2019-12-17 | UBA-13455 | An error may appear when a time range is selected from the Scope menu on pages containing anomaly and device information. |
2019-12-09 | UBA-13309 | Custom data ingest requires switching to ETLv1 |
2019-12-06 | UBA-13332 | On the restored UBA host the uiServer.host= in site property file shows the backup hostname |
2019-12-03 | UBA-12736 | Too many TriggeringEventsCalculator jobs running |
2019-12-03 | UBA-12111, UBA-14199, UBA-13051 | Impala jdbc connections leak |
2019-11-25 | UBA-13355 | Datasources aren't automatically starting after a stop-all/start-all |
2019-11-18 | UBA-13187 | Some Custom Model raised Anomaly with incorrect anomaly categories |
2019-11-06 | UBA-11603 | Spark stop needs to run 'stop-all-spark.py' on all workers |
2019-11-06 | UBA-13265 | UBA stale Spark workers jvms cause spark restarts |
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.1
Feedback submitted, thanks!