[Lens] Deep Link into a prefilled editor

[AlonaNadler]

Currently, when a solution team needs to implement a chart they turn to the elastic chart team. In the future, we want to be able to embed Lens inside a solution and allow users of the solution to jump to Lens in case they want to explore further, in a similar way to what the Metric Explorer does with TSVB
Metric explorer:

which opens in TSVB:

(Observability team is ready to make the switch to the metric explorer as soon as we have rate)

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[wylieconlon]

We now have a simpler way of doing the Discover -> Lens navigation (#67415), but we haven't yet defined the requirements for solutions that would want to link to Lens.

The simplest option we can offer is the same as Discover, where the solution could ask Lens to visualize a field from an index pattern, and we'll build the default suggestion.

Alternatively, we could offer an API that gives more control. For example, the pre-filled information might contain:

• Index pattern
• List of fields + aggregations
• Preferred chart type

Can you help clarify the scope @AlonaNadler? Do you have an idea of what solution teams are expecting?

[wylieconlon]

There are two separate implementation ideas that we can consider:

a: Expand the scope of apps that can navigate into Lens using internal state, not part of the URL. This is how we did the action to open Lens from Discover, and completely hides the state from our users.

b. Public facing URL parameters: I think this is more like what we are talking about here #75316, where the URL is able to provide enough state information that we can construct a full visualization. This is more complicated to support.

[flash1293]

This is possible now (#84416). Actual integrations will be tracked separately