-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Logs UI] Replace legacy elasticsearch client usage #73978
Comments
Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui) |
@weltenwort correct me if I'm wrong, but if we're moving to the data plugin in the client and using search strategies, we will no longer need to worry about this migration, right? See: #76677 |
That should cover most of it, yes. To be sure I'd still recommend to search through our plugin codebase, though. |
Scratch that, I did find a few legacy usages in this file: https:/elastic/kibana/blob/master/x-pack/plugins/infra/server/lib/log_analysis/log_entry_categories_analysis.ts |
@jasonrhodes could we get these last bits prioritized? Should be a pretty small lift to get this closed. |
@sgrodzicki I think we should just knock this out ASAP when @weltenwort or @Kerry350 have some bandwidth in between other tasks, since this should be pretty small. |
Summary
With the removal of the legacy Elasticsearch client in the Kibana Platform, we need to replace all usage with calls to the
data
plugin'ssearch
or with the new client as described in the migration guide.The text was updated successfully, but these errors were encountered: