Kibana Input controls old v/s new

[VVK (VVetsa)]

Hi,
We are using Kibana/Elasticsearch /eck managed for our dev/production (non customer facing UIs) to analyse many things.

Sometime back kibana depricated beta version / non-guaranteed (non production ready) versions of Input Controls. Now Kibana advocates such that when theme is dark, it is very difficult to see data in the old input control values( background/foreground of input control values being in white color). Indirectly forcing to switch to new controls.

We abided by shifting our visualisations to new version. They work neat w.r.t. functional correctness. Thanks.

In the old controls:
We used to read data from a data set, let's call 'master data for meta information' into Input Controls.

Advantage of this approach of 'master data for meta information':
The data set size is small. Unique values / dependent values etc...selections make the load on Elasticsearch to certain extent optimum. We could reduce load on elasticsearch considerably.

Now:
Visualisation data: Each row/entry of visualisable data set (let's call business data) was enriched with the 'master data for meta information'.

This enrichment enabled us for filtering much easier.

Usecase: When/how many cold/warm 'create contact' user interaction, time taken, timestamp per tenant in DC USEast/ affinity if any /provider AWS / customer during last week

In the above example: tenant , dc, provider / customer --> are master data
Business data is cold/warm , create/delete/update, tenant , contact , end user id of the end user. As you can imagine, enriched data is combination of above two.

We published visualisation for 'warm' end user interactions by default (meaning filter will be interactionType=warm)

This worked beautifully with old input control (having two data sets - business data set for graphic visualisations and master-data set for input).

Now when we shifted to new input controls:
Since, interactiontype field is not available in 'meta data' data set, nothing appears in new input controls.
In old deprecated input control, the global filter was not applied input filters, there by values coming in.
So, we shifted to business data set (for new control to have unique meta data), we can see marked increase in resource utilization on Elasticsearch and wait time.

Question to you:
In such condition, do you suggest any trick?.. Or will you consider having this feature request of ignoring global filter?

Regards,

[nickpeihl]

Hi @VVK. Thank you for sharing your valuable insights and use case. I have opened a Feature Request for ignoring global filters in Controls.

The issue with the dark theme being applied incorrectly on the Legacy Input Controls appears to have been fixed in Kibana 8.6.

[VVK (VVetsa)]

thanks.

[VVK (VVetsa)]

@nickpeihl

I went through the discussion and other references (8.2.0) aspects (feature request).

Let me add my two cents, of course it may have pros and cons.

Options should be given for.

• global time filter - ignore/consider
• global query bar - ignore/consider

Why?
As of today, in my use case: My master data gets pushed/synced daily once.
Business data 'almost realtime' / streamed.
But typical analysis/interpretation of data happens on daily basis (least count of timerange is a single day - default dashboard level). Later drilldowns kick-in.

Where does this/my approach fail?:
When global time filter range (start time to end time ) is lesser than a day and does not include sync time of master data, input controls may not show anything.

These aspects are issues of data set owner and should be immune to features of Kibana, is it not?. As of now we have workarounds like drill downs kick in when narrow down on time world.

Solution to above glitch:
It is application developer/data set owner issue(i.e. me). Taking my use case into consideration, any change (creation/deletion/update) in master data should also be done in near real time .

Your views are of course welcome.

[nickpeihl]

Hi @VVK. Do you mind adding your comments to the GitHub feature request? On GitHub we have a wider audience and and GitHub makes it easier to track these discussions.