[Uptime] Ml detection of duration anomalies

[shahzad31]

Summary

Fixes: #60619

Ml detection of duration anomalies

Testing:
User can enable Anomaly detection on duration chart of each monitor by clicking enable anomaly detection

if they don't have ML feature available they will see the flyout with asking to start Trial

Otherwise, they can create job by clicking create new job

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
• This was checked for keyboard-only and screenreader accessibility
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser
• This was checked for cross-browser compatibility, including a check against IE11

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[shahzad31]

Requested some ML changes

@jgowdyelastic i took care of your feedback.

[jgowdyelastic]

ML code changes LGTM

[lukeelmers]

App Arch code change LGTM

[justinkambic]

Smoke testing summary:

• I loaded the page as a super user and made sure that ML worked with a platinum/trial license, and that it was not enabled for lower license levels.
• I defined two spaces, one with access to ML and one without, and made sure users with sufficient permissions could define anomaly detection jobs, and that the feature was disabled otherwise.
• I made sure I could navigate to the ML plugin and view the jobs I've defined.
• I didn't observe anomalies myself, because my dataset was insufficient. I've seen this part of the feature demoed and it seems to work, but we should have a long-term testing cluster available that we can point our dev builds to.

Additional functional feedback I encountered while testing:

Not something to hold the review up on, but an enhancement we can add later: I activated a trial license and came back here. I closed the flyout and re-opened it and assumed the state would change to reflect the new license. We should see if it's possible to get that updated license state without refreshing the page (maybe after NP migration):

When trying to create an ML job with a user with insufficient permissions, I am noticing that the button is disabled (good) but we can probably make it better by adding an explanation via a tooltip. I'm fine with discussing this as a separate design issue that we'd address in a follow-up.

Note

I'm approving this now to get that out of the way, I have found several minor things like typoes and spacing issues that should be adjusted. Assuming there won't be any more large changes I am LGTM WFG on this one.

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 2750e60

History

• 💚 Build #35655 succeeded 6eade46
• 💚 Build #35389 succeeded 3e50e16
• 💚 Build #35376 succeeded a7af917
• 💔 Build #35342 failed 68cfc26
• 💔 Build #35270 failed b323b8c

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