[Lens] Support drilldowns in charts with only one dimension (when it is a formula)

[drewdaemon]

If I have a chart with only one dimension (metric) which is a formula then the drilldowns are not applied.

We could possibly allow them but then there is the question on which filters should be applied:

• If I have something like func(field) then it can create a field: exists filter
• If I have something like func(field1) + func(field2) ? Could be 2 filters with field1: exists and field2: exists but does it make sense?

[elasticmachine]

Pinging @elastic/kibana-visualizations @elastic/kibana-visualizations-external (Team:Visualizations)

[stratoula]

@drewdaemon they are supported

Am I missing something?

[stratoula]

The problem is not general but only if formulas are applied (it works fine with quick functions)

[stratoula]

I checked this issue and it happens for the following reason:

1. Formula creates 2 columns
   • (Part of which if I understand correctly is hidden and has configuration that is important for the visible column
   • The visible column

The look like that

``` [ { "id": "c0df5a54-b17a-475c-8dde-8da22af9c696X0", "name": "Part of min(AvgTicketPrice)", "meta": { "type": "number", "field": "AvgTicketPrice", "index": "kibana_sample_data_flights", "params": { "id": "number", "params": { "pattern": "$0,0.[00]" } }, "source": "esaggs", "sourceParams": { "hasPrecisionError": false, "indexPatternId": "d3d7af60-4c81-11e8-b3d7-01146121b73d", "id": "0", "enabled": true, "type": "min", "params": { "field": "AvgTicketPrice" }, "schema": "metric" } } }, { "id": "c0df5a54-b17a-475c-8dde-8da22af9c696", "name": "min(AvgTicketPrice)", "meta": { "type": "number", "params": { "id": "number" } } } ] ```

When we are checking if a filter is compatible to create a drilldown we are using the visible column (this makes sense to me) and the reason it returns incompatible is simply because it fails here https://github.com/elastic/kibana/blob/main/src/plugins/data/public/actions/filters/create_filters_from_value_click.ts#L84

The Part of column has this information, so I wonder which is the best approach here. Why the visible column doesnt have this information? Should we pass it from the partial column to the visible one or should we create the filter from the partial column?

@dej611 you know formulas better than me. Can you take a look?

[stratoula]

Another update on this:

• metrics with formula and drilldown work fine.
• if I have a formula like that min(field1) - min(field2) which filter should be created?

The same behavior exists if I have a bar chart with a formula (and no x-axis/split dimension)

I am changing to an enhancement.

[ninoslavmiskovic]

hi @drewdaemon and @stratoula ,

I had some time to check this out on the 8.9 version (see recording):

Skaermoptagelse.2023-05-11.kl.21.36.06.mov

I want to make sure I understand this 💯 , so apologies for going into too many details perhaps 😃

I have two metric visualizations both of them with exactly the same drill-downs.

• One with "Quick function"
• One with formula

The one with formula is not working with drill-down as mentioned by both of you above ⬆️

My take from the user perspective is that the drill-down should behave the same way regardless of how the calculation is done (formula or quick function). Currently, the user does not get any information why the drill-down he/she just setup on a metric with formula is not working

@stratoula : Could you perhaps elaborate on this: "metrics with formula and dropdowns work fine." Do you mean metric with quick functions?

WDYT ?

[stratoula]

@ninoslavmiskovic

1. I had a typo, metrics with formulas and drilldowns work fine. What doesnt work are metrics with math i.e. min(field) + max(field).
2. When we say metric we mean the metric dimension not the chart :)

[ninoslavmiskovic]

@stratoula

Thanks 🙏 I was looking at this late last night. With your explanation and a read, it makes more sense. 😊

• I removed the suggestion for the title change.

I still think it would make sense to support:

• When a user writes a formula like func(field) we should create an existing filter like @drewdaemon suggests.

For metrics with math i.e. min(field) + max(field). :

• Would it make sense to display the formula query on a panel with a filter icon, as we do with ESQL charts on a dashboard, and perhaps write some information that the drill-down filter is not applicable?
• I recommend that we involve UX, because we have the same challenge with Lens suggestions created with ESQL (eval).

[stratoula]

• As I explain above this is the goal [Lens] Support drilldowns in charts with only one dimension (when it is a formula) #151726 (comment) but it has some technical limitations.
• About the formulas that it will be difficult to create drilldowns I feel that the best approach is to hide the drilldowns that are incomatible rather than adding another icon. We are doing the same for other cases (i.e. TSVB non timeseries charts)

[ninoslavmiskovic]

I am okay with the approach of hiding the drill-downs that are incompatible.

FWIW I was referring to this icon that we already use (ESQL), which perhaps we could also use to display formula queries. This way the user does not have to go to Lens to figure out the formula query. (Perhaps this could be a separate enhancement request)

[markov00]

In order to provide better transparency of priorities, issues that will not be prioritized within the next 24 months are being closed.

Tracking request in Lens general improvements ice box #184459