[Logs and Metrics UI] What will it take to migrate our data access layer to Kibana Search Service?

[jasonrhodes]

In order to assess how much work this will be, we need to have some documentation guidance from the @elastic/kibana-app-arch team. @AlonaNadler can you direct us to the best place for that guidance?

[AlonaNadler]

@lizozom, @elastic-jb, and @lukasolson are working on documentation and can provide guidance.

[simianhacker]

I really think the data service should be as ubiquitous as core.elasticsearch. We shouldn't have to make any effort to ensure it's there similar to how core works today.

[jasonrhodes]

@lizozom / @elastic-jb / @lukasolson can you ping me or mention this issue when there are docs and examples ready for how to interact with the data plugin's API? Thanks!

[lukasolson]

Are you wanting to implement custom request/response handling or are you mostly just requesting data from Elasticsearch and returning it directly? If so, it should be just a matter of including the data plugin in your dependencies (or data_enhanced in X-Pack) and then using data.search.search() instead of the client exposed by core.

If you need custom request/response handling, there is a good example of a way to accomplish this in this PR: #75471. There's also a more simplified example here: https://github.com/elastic/kibana/tree/9111d5096566b0d3c6659895b40f01f66450520e/examples/search_examples

We are still working on getting more documentation but if you have specific questions please don't hesitate to ask in #kibana-app-arch or reach out directly to me or @lizozom.