Design embedded Jaeger UI with GitLab

Problem to solve

We currently simply open Jaeger in a new tab, because we ran into security issues with iframing Jaeger which we couldn't solve within a single release: https://gitlab.com/gitlab-org/gitlab-ee/issues/4753#note_107283934

We discussed how to address some of the challenges with iframing here: https://gitlab.com/gitlab-org/gitlab-ce/issues/59422

Since it looks like we will be able to address the security concerns, we should proceed with how to embed Jaeger in an iframe.

Intended users

Further details

https://www.jaegertracing.io/docs/next-release/frontend-ui/#embedded-mode

Proposal

We should take a two step approach here:

1. iframe the whole Jaeger UI, as a first iteration
2. Build our own "search" panel, then iframe just the trace panel. As part of this, we should also add a button to open the whole UI if you want to get access to features not available in embedded mode, like comparisons and dependencies.

Proposed design for the first step, iframe the Jaeger UI design not yet confirmed

Add Jaeger within an iframe on the Tracing page:

Remove the external link icon next to Tracing when Jaeger has been enabled:

Permissions and Security

Documentation

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references