[Infra][Hosts UI] Schema selection

[crespocarlos]

Summary

Following up on the work from #226332, we need to add a component to the page to allow users to select the schema.

Suggestion: A simple select below the unified search bar called "Schema"

Options: OpenTelemetry and Elastic System Integration

Designs

Acceptance criteria

• The toggle should always appear.
• The schema selector should show how many available schemas are available based on the current query
• When loading the app, the schema selector should default to ECS (if only ECS available), OTel (if only OTel available) or OTel (when both are available)
• Once a schema is selected, it should persist for further queries in the current session
• When opening the schema selector, it should only show available schemas for the current query
• If the user changes the query and the currently selected schema has no hosts, we should show the selected schema is invalid
• When a given schema is selected, it should only show Hosts which have data for a given schema (i.e. data will be filtered by something like event.dataset : "otel.generic" etc for OTel

TBC w @MiriamAparicio + @crespocarlos

• If the endpoint from #226332 returns a single schema, it should automatically be persisted in a context

Content

Schema selector tooltip copy
Select which data collection schema your entities are observed with.

See documentation for more information.

[crespocarlos]

@roshan-elastic I wonder if you have any suggestions for the UI.

[roshan-elastic]

Hey @crespocarlos,

I've left a comment in the parent issue to discuss this .

[roshan-elastic]

Hey @crespocarlos - maybe we can do something like this?

One thing I want to be cautious about is setting a high-bar that we're unable to replicate/migrate users off if we move to a experiences made in Dashboards and Discover so one for discussion.

[crespocarlos]

Hey @roshan-elastic how important is the count?

[roshan-elastic]

Hey @crespocarlos - in an ideal world, I'd love to do this. My worry is that we're setting a high-bar that will be hard to replicate if we move to a Dashboards and Discover (DnD) world.

Perhaps we should think about what might be feasible in a world where there are two dashboards and try and to work backwards so we don't set a bar which is super hard to transition from?

Here are my assumptions:

• A 'count' might be difficult because that's probably pretty specific to entity-specific dashboards (it might work for 'hosts' but it wouldn't work for a K8s overview dashboard). We should probably remove this.

• Whilst 'you have data available in another schema' will be super useful, I'm not sure how this might be feasible in a DnD world (assuming we have separate dashboards per schema and Graham's point that it is unlikely we'll have a schema selector at all). I think we should probably remove this too.

What do you think?

[crespocarlos]

@roshan-elastic , those are good points, and I agree with them.

While I do like the look and feel, IMHO, we should try to keep it simple.

As you said, the whole schema detection logic doesn't seem like something we want to do in a dashboard-based experience, given the complexities behind it.

[roshan-elastic]

Cool @crespocarlos - let's just make it a drop-down or a toggle or something then. No need for counts or alerting users of data available in the other 'mode'.