[Logs UI] Anomalies tab doesn't show links to manage jobs in the ML UI unless anomalies are found

[weltenwort]

Problem description

The "Anomalies" tab has links to the underlying ML jobs only on the level of the rows that correspond to anomalies. If there are no anomalies in the selected time range, no link to the ML UI is shown.

Proposed solution

In order to provide an anomaly-independent link we could add a link to the ML UI's anomaly explorer on each existing job's card in the flyout:

The link could point to a filtered view of the anomaly explorer such as /app/ml#/explorer?_g=(ml:(jobIds:!('kibana-logs-ui-default-default-log-entry-categories-count')),refreshInterval:(display:Off,pause:!f,value:0),time:(from:'2020-06-01T11:20:26.000Z',mode:absolute,to:'2020-07-20T09:52:29.000Z'))&_a=(query:(query_string:(analyze_wildcard:!t,query:'*'))).

[elasticmachine]

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

[katrin-freihofner]

Quick dev-tools-based-mockup 😀

[jasonrhodes]

@weltenwort is this a bug that we're going to address for 7.9 or an enhancement for 7.10?

[weltenwort]

Since we lost that link with the flyout refactoring I was about to treat it as a bug. What would you prefer?

[afgomez]

/cc @jasonrhodes, @weltenwort, @katrin-freihofner

I want to make sure I'm getting this task right.

@weltenwort commented on the PR about the destination of the links.

The task has mixed purposes. On one hand it talks about adding a link to manage the job on the ML app (which is Felix's comment in the PR). On the other hand it's filed as a bug to restore the following link to the anomaly explorer:

I understood the second point, but maybe I misunderstood it. Which one is it? Do we want a link to the job settings? Do we want to restore the link? In case it's the first, do we want a separate task to restore the link?