[ML] Anomaly Detection: Adds a page to list supplied job configurations

[alvarezmelissa87]

Summary

This PR adds a page in the UI for 'Supplied configurations'
Dependent on this fix to the endpoint schema going in first: #191633

NOTE: This item will be added to the side-nav of oblt serverless once this update is in: #190458 - replaced by #192050

Adds dedicated UI page for preconfigured job packages - subitem of the Anomaly Detection navigation:

When they can't be run in the ML UI:

When selected - flyout opens to reveal package assets:

Clicking the Run data recognizer button shows matching data views (if any) with link to job creation:

Empty table when no matching dataviews are found:

Jobs tab of flyout:

kibana tab of flyout:

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Flaky Test Runner was used on any tests changed
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

[alvarezmelissa87]

@szabosteve - pinging you for feedback on the copy used. 🙏

[peteharverson]

Maybe something like These jobs can be created in the {appName} app.?

[peteharverson]

As discussed offline, note that the Logs jobs can't be created in the Serverless oblt project, so we'll need to remove the text about using the jobs in the Logs app on serverless.

[peteharverson]

Is it possible to add in the check for serverless, and remove the text for 'These supplied configurations can be used in Logs' if on serverless?

[alvarezmelissa87]

@peteharverson - for serverless security, the tags have been updated to only show compatible modules so there's no need to do anything on the browserside to check.

As for oblt - do those need to be shown if they can't be used at all? Should we just remove the 'observability' tag which will ensure they aren't shown in this view at all? cc @jgowdyelastic

For example, those won't show up as they are filtered out by tag in the modules endpoint.

[alvarezmelissa87]

Removed copy in oblt in b21695c

[jgowdyelastic]

A viewer user gets this error when attempting to view the page. I think we should allow them to access the page, but any links to create jobs should be disabled.

[alvarezmelissa87]

@peteharverson, @szabosteve - Thank you so much for taking a look! Would you be up for resolving the comments once you confirm the suggested update has been added? Would help reduce the noise. Thank you! 🙏

[alvarezmelissa87]

A viewer user gets this error when attempting to view the page. I think we should allow them to access the page, but any links to create jobs should be disabled.

Good call! Updated in cdb1656

[peteharverson]

Gave this another test against cdb1656 (stateful, and serverless oblt). Overall looks good and resolved most of my previous comments.

Only items left from my testing are:

• Info callout for Logs and Metrics jobs - any chance of adding links to the apps (nice to have, not essential), and hiding the text referring to Logs on serverless oblt
• Running the data recognizer check against data views if possible, as suggested in [ML] Anomaly Detection: Adds a page to list supplied job configurations #191564 (comment)

[alvarezmelissa87]

@jgowdyelastic - all updates added in c81e7f6

[alvarezmelissa87]

@elasticmachine merge upstream

[szabosteve]

UI text LGTM!

[peteharverson]

Test latest changes locally and on cloud, and LGTM

[jgowdyelastic]

I'm seeing 404 errors from this call in the console if the dashboard doesn't exist.

I think we should catch these and just return an empty array if they can't be found.

[alvarezmelissa87]

These errors are actually not thrown from here - findByIds has it's own error handling internally in src/plugins/dashboard/public/services/dashboard_content_management/lib/find_dashboards.ts and returns the caught error in an object with a 'status' and 'error' property. The response is type FindDashboardsByIdResponse - which is defined in that same file I shared. That's why here - we simply filter out the results with error status.

I think if we want to do something to remove the logged 404s, it will need to be in a separate PR and would need to chat with whoever maintains that service.

[jgowdyelastic]

Styling nit pick, the kibana objects are listed in bold but the jobs are not. It would be good to be consistent. It's quite noticeable when switching tabs.

[alvarezmelissa87]

Styling nit pick, the kibana objects are listed in bold but the jobs are not. It would be good to be consistent. It's quite noticeable when switching tabs.

Good point - updated to make the style consistent in 7d8cbbd

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: c05ad0c
• Cloud Deployment
• Kibana Serverless Image: docker.elastic.co/kibana-ci/kibana-serverless:pr-191564-c05ad0c73c8c

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
ml	2026	2036	+10

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
aiAssistantManagementSelection	90.6KB	90.8KB	+126.0B
lists	143.1KB	143.3KB	+126.0B
ml	4.6MB	4.6MB	+20.2KB
securitySolution	19.7MB	19.7MB	+583.0B
total			+21.0KB

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
ml	101	102	+1

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
core	418.6KB	418.8KB	+161.0B
ml	78.7KB	79.1KB	+388.0B
securitySolutionEss	16.3KB	16.4KB	+55.0B
securitySolutionServerless	21.4KB	21.5KB	+55.0B
total			+659.0B

Unknown metric groups

async chunk count

id	before	after	diff
ml	110	111	+1

ESLint disabled line counts

id	before	after	diff
ml	563	564	+1

Total ESLint disabled count

id	before	after	diff
ml	566	567	+1

History

• 💚 Build #233570 succeeded 7d8cbbd
• 💚 Build #233526 succeeded 1022636
• 💛 Build #233471 was flaky 9a0214e
• 💚 Build #233292 succeeded c81e7f6

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @alvarezmelissa87

[jgowdyelastic]

LGTM

[alvarezmelissa87]

Link to this view will be added to observable/stateful nav in this PR