Skip to content
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

Migrate Beats Management server-side #67980

Closed
joshdover opened this issue Jun 2, 2020 · 1 comment · Fixed by #70930
Closed

Migrate Beats Management server-side #67980

joshdover opened this issue Jun 2, 2020 · 1 comment · Fixed by #70930
Assignees
Labels
Feature:Legacy Removal Issues related to removing legacy Kibana Feature:New Platform Feature:NP Migration Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@joshdover
Copy link
Contributor

Required to remove legacy, we need to migrate the server-side of the beats_management plugin to the KP.

@joshdover joshdover added Feature:New Platform Feature:NP Migration Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc labels Jun 2, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform (Team:Platform)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Legacy Removal Issues related to removing legacy Kibana Feature:New Platform Feature:NP Migration Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants