[APM] Show license callout for ML integration and option to start trial

[formgeist]

Summary

Related to #50879

Currently, when a user clicks on the integrations to create a ML job for a particular service, we surface just a warning message to the user saying "Job creation failed" because of licensing issue. Instead of just surfacing the error message, we should give customers the option to enable a ML trial license.

Solution

Note: The mocks below feature a new consistent header design that is yet to be implemented. I've added an example of how the context menu will be placed adjacent to the existing Integrations context menu.

Move the Machine Learning options to a new Anomaly detection context menu

• Create a new Anomaly detection context menu
• Remove Machine Learning options from the Integrations menu
• Place the Anomaly detection context menu adjacent to the Integrations context menu (this will eventually become the Alerts context menu)

Show trial option for users who are not currently appropriate license

Show EuiCallout in primary with the following setup:

• Title: Start free 14-day Platinum license trial
• Copy:

In order to access APM's anomaly detection feature, you must be subscribed to an Elastic Platinum license. With it, you'll have the ability to run Machine Learning jobs to view detected anomalies in your APM data.

• Link button EuiButton primary with copy Start free 14-day trial - links to License management page

[elasticmachine]

Pinging @elastic/apm-ui (Team:apm)

[formgeist]

Updated screen and description with revised copy for the callout. @nehaduggal Are we happy with the title of the callout, it wasn't part of the copy changes?

[cauemarcondes]

@formgeist I'm running ES with a Basic license and the action to create a new ML job isn't available.

The ML integration checks if it's enabled and available, in my case it's enabled but not available, so there's no way to create a new job. How can I simulate the problem?

[formgeist]

I think a prerequisite for this is to make the Machine Leaning options available in the integrations menu even if you don't have the appropriate license, in order to promote them to users enticing them to upgrade. It's been a while since we've looked at this, and we'll soon be bringing a new set of jobs in, so I'm wondering if this is the way to do it. I have a chat with @nehaduggal in a bit, I'll raise it then and see what we agree on as the right approach.

[formgeist]

Discussed this with @nehaduggal earlier and we agreed that we want to separate the ML jobs out into its own options dropdown outside the current "integrations" and in there have a callout option to start trial for users with a license that does not support ML.

Opened design issue elastic/apm#209 to come up with designs for this, which I'll hopefully have ready within the next days or so.

[sorenlouv]

we agreed that we want to separate the ML jobs out into its own options dropdown outside the current "integrations"

I think this makes sense. If ML links are removed Integrations dropdown will only contain the watcher links (soon to be alerting). So I suggest having a dedicated watcher/alerting button as well.

Currently the Integrations dropdown is exactly the same on the transactions and error pages - even though transaction page doesn't support watcher, and error page doesn't support ML. What do you think about only having the buttons where they are needed? When we eventually add ML jobs for both transactions and errors I think having separate button will still make sense, since they'll be creating different jobs.

tldr: Instead of a single Integrations button we should have two different buttons: "ML" and "Alerting".

[formgeist]

I think this makes sense. If ML links are removed Integrations dropdown will only contain the watcher links (soon to be alerting). So I suggest having a dedicated watcher/alerting button as well.

That's the plan; to have a dedicated Alerts

Currently the Integrations dropdown is exactly the same on the transactions and error pages - even though transaction page doesn't support watcher, and error page doesn't support ML. What do you think about only having the buttons where they are needed? When we eventually add ML jobs for both transactions and errors I think having separate button will still make sense, since they'll be creating different jobs.

I see the Integrations menu and the soon-to-be Anomaly detection and Alerts options as related to the Service, not tied to the views. Both aforementioned new options should be available from any view within a given service IMO, but whether we limit the available options to only be ones that are relevant for the exact view you're in, I'm not so sure that's apparent to the user. For alerts we have a specific flow for creating an alert based on the visualization we show, e.g. the Transaction duration threshold alert type.

[formgeist]

@cauemarcondes I've updated the description with the revised design mocks and implementation details. Let me know if you have any comments or feedback.

[elasticmachine]

Pinging @elastic/ml-ui (:ml)

[formgeist]

Superseeded by #70691