UEBA behavior-based detections not appeared on Content Management UI.
After the UEBA Content App is installed on the ES search head cluster, behavior-based detections do not appear in Content Management UI.
The following symptoms were observed:
Inspect the network request when loading the Content Mangement UI. Filter and compare these two requests from the same page load:
A positive match looks like this:
The bare call returns exactly 30 entries, and `DA-ESS-UEBAContent` is not among them.
The `appsandservices` call returns the full app list, including `DA-ESS-UEBAContent`.
Verify the issue applicability:
Count the apps whose names sort alphabetically before `DA-ESS-UEBAContent`, using the directory listing of `$SPLUNK_HOME/etc/apps` on a member.
ls -1 "$SPLUNK_HOME/etc/apps" | sort -f | nl -ba
If there are 30 or more, the issue applies.
Any on-prem deployment with more than 30 installed apps where the environment's custom app names sort alphabetically before DA-ESS-UEBAContent (extremely common — any A-* / B-* / C-* prefix will do it).
Problematic example below from test lab:

This is a known issue, the fix is included in ES 8.8 release.
Workaround:
Option 1:
Rename apps: Modify the names of apps listed alphabetically before DA-ESS-UEBAContent, ensuring that DA-ESS-UEBAContent appears within the first 30 apps when sorted alphabetically.
Option 2:
Manage detections elsewhere: Manage the detections and saved searches from Searches, Reports, and Alerts. All detections and saved searches in the DA-ESS-UEBAContent app remain functional and accessible there.
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
03-Oct-2026
|
Initial Release |