Kibana: [Infra + Logs UI] Proposal: Add source switching UI

Created on 11 Jul 2018  路  8Comments  路  Source: elastic/kibana

Summary

The currently used set of source aliases and configuration should be selectable in the UI. It can be disabled or completely hidden if only one source is present in the configuration (see #20428).

Rationale

With the introduction of the data source concept with the integration package manager there is a strong use-case for having representing these data sources in the Infra and Logs UIs. Of these there can be multiple per Kibana space, so a source selector that displays the name and description could make sense.

Mockups

:warning: these are only preliminary mockups

grafik

Logs UI Metrics UI logs-metrics-ui Backlog design

Most helpful comment

Sounds like we'll eventually want @hbharding to help us shape this, not a priority yet but we'll look at it again for later releases. :+1:

All 8 comments

Alternatively, a one-to-one mapping between a Kibana space and a source might be desirable. :thinking:

@weltenwort re. the one-to-one mapping, a space might need multiple sources? If a space hasn't configured any source, it will get the default source?

multiple sources: sure, shouldn't be a problem technically. I see that mainly as a UX decision.

default source: either that or the user is shown a prompt to configure an initial source for the space

@elastic/infra-logs-ui This ticket is a year old. Do we think this is still a priority?

For the Logs UI, the main complexity is in achieving a good UX for this. Most of the underlying capabilities have been implemented by now.

Sounds like we'll eventually want @hbharding to help us shape this, not a priority yet but we'll look at it again for later releases. :+1:

This would be a great feature for our environment as well.
As for as UX goes, I don't see a problem with just using a simple drop down menu like the index pattern one in discover.

Another feature possibility is tying certain filters to certain datasources.
Eg, An Apache Logs datasource could have a pinned filter of event.module: apache
I think this is beyond the scope of this proposal though.

Another feature possibility is tying certain filters to certain datasources.

Agreed - that could be very useful

Was this page helpful?
0 / 5 - 0 ratings