[ML] Adds link to anomaly detection job creation from the alerting rule form

[darnautov]

Summary

Closes #173654

Adds an option to create a new anomaly detection job from the job selector control.

Checklist

• 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
• 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)
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

[elasticmachine]

Pinging @elastic/ml-ui (:ml)

[qn895]

Tested and LGTM, but I wonder if it's better to either have the select open the link in another tab, or have a prompt message with the link before the selection box.

With the current flow, user would come in, fill out info, select ---Create new---, and be redirected to the job creation page. But effectively they would have to navigate back to the rule later on and lose the info filled out.

Screen.Recording.2023-12-29.at.10.15.09.mov

The spacing before the Alert when hint also looks odd

[darnautov]

@elasticmachine merge upstream

[darnautov]

hi @qn895, thanks for the feedback!

it's better to either have the select open the link in another tab

Kibana is a SPA, so opening the same window is significantly faster and provides a better UX.

or have a prompt message with the link before the selection box.

It'll consume additional vertical space and require the user to read the warning, while we should have this option available at all times. Having the creation entry directly in the relevant control seems like a better option IMO.

With the current flow, user would come in, fill out info, select ---Create new---, and be redirected to the job creation page. But effectively they would have to navigate back to the rule later on and lose the info filled out.

It redirects the user to the Job wizard page, and at the last step of the wizard, we have a button to create an alerting rule, that opens a flyout with a populated job field.

The spacing before the Alert when hint also looks odd

It is controlled by the alerting flyout and looks the same for all alerting rules.

[peteharverson]

Tested latest changes and LGTM

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 92ad113

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
ml	1886	1889	+3

Async chunks

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

id	before	after	diff
ml	3.6MB	3.6MB	+2.0KB
securitySolution	11.3MB	11.3MB	+6.4KB
securitySolutionServerless	354.9KB	361.2KB	+6.3KB
total			+14.6KB

Page load bundle

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

id	before	after	diff
ml	78.2KB	78.2KB	+2.0B
securitySolutionServerless	40.6KB	40.6KB	-1.0B
total			+1.0B

Unknown metric groups

ESLint disabled line counts

id	before	after	diff
ml	553	552	-1

Total ESLint disabled count

id	before	after	diff
ml	556	555	-1

History

• 💚 Build #185364 succeeded cc28878
• 💛 Build #185239 was flaky ab3ff54
• 💚 Build #185119 succeeded 80da1c4

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

cc @darnautov