[Logs UI] Move ML job setup to flyout

[katrin-freihofner]

We want to move the existing ML job setups to a flyout. This will prepare us for the upcoming merge of (log rate and category) anomalies to one overview and is also more consistent compared to our current solution.

The new setup should work like this:

This means the following changes:

• if ML is not yet set up, both tabs (log rate and categories) should show an empty state and open the flyout with the setup screen

• all warning/error/success states can stay in the setup as we have them right now

• Please ignore the button leading back from the setup to the job list for now - we will need this once we can provide the ML job list

Design issue
Figma prototype
Figma design file

[elasticmachine]

Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui)

[jasonrhodes]

@afgomez can you explain why this is currently blocked here in the comments? Thanks!

[afgomez]

@jasonrhodes sure.

The content for the initial setup screen is yet to be defined. Without content the flyout in the initial setup will fly over an empty screen.

[katrin-freihofner]

What is missing is the case where no ML jobs are set up but the user has a premium license (or free trial). For the other cases, we have a solution #64921

[mukeshelastic]

Just to make sure I understood this correctly, the content we are looking for here is the one that is displayed on the main screen when the user clicks on anomalies and categories when no ML jobs have been set up for them and the user has the correct license ( or free valid ongoing trial).

If that's what we are looking for then.. here is a possible content.. We can run this by docs folks for grammar later..

" To show log <anomalies/categories>, machine learning jobs need to be set up." Button with a link to flyout is shown and the button text says: "ML setup"

[afgomez]

Just to make sure I understood this correctly, the content we are looking for here is the one that is displayed on the main screen when the user clicks on anomalies and categories when no ML jobs have been set up for them and the user has the correct license

That is correct :)

I'll go ahead and write the content