-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] Provide help for migrating Logs UI settings #189646
[Logs] Provide help for migrating Logs UI settings #189646
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
0d6c498
to
564309f
Compare
This reverts commit b98490c.
564309f
to
b1adcd2
Compare
/ci |
Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs) |
…ings-migration-help
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to work well 👍
Do you know what the expectations around spaces and the upgrade assistant are? Should it enumerate the deprecations for all spaces? Or is the user expected to visit it once in every space?
...s/observability_solution/logs_shared/server/routes/deprecations/migrate_log_view_settings.ts
Show resolved
Hide resolved
x-pack/plugins/observability_solution/logs_shared/server/deprecations/log_sources_setting.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/observability_solution/logs_shared/server/deprecations/log_sources_setting.ts
Outdated
Show resolved
Hide resolved
@weltenwort Thanks for the review.
I couldn't find any explicit documentation over spaces and migrations. However, when I looked at other migrations that interacted with Saved Objects they seemed to also be done in this manner (once per space). My assumption was also that we probably don't want to land one big migration across spaces given how users use it for segmentation and configuration, it could be surprising. Potentially one space is ready for migration, one isn't yet etc. |
Good point. Ideally the upgrade assistant would list a separate problem for each space. I just wondered if that needs to be included in the deprecation factory or outside of it by the assistant itself. |
Summary after speaking to some core folks / investigating: It doesn't look like a "migrate all spaces" approach will be possible with the functionality we have available at the moment.
We'll keep the "once per space" approach for now, and we can amend things if platform guidance changes. |
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for the thoroughness
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
History
To update your PR or re-run it, just comment with: cc @Kerry350 |
Assigned lists due to the api called is defined here: https://github.com/elastic/kibana/blob/4ed9e5173c6d56a949c15fcb8aa223cfc64fc5f1/x-pack/test/security_solution_cypress/cypress/tasks/api_calls/exceptions.ts#L54 \cc @elastic/security-detection-engine Assigned Logs Shared due to elastic#189646 \cc @elastic/obs-ux-logs-team Assigned logstash due to https://github.com/elastic/kibana/blob/4ed9e5173c6d56a949c15fcb8aa223cfc64fc5f1/x-pack/plugins/logstash/kibana.jsonc#L4 \cc @elastic/logstash Assigned metris ui due to https://github.com/elastic/kibana/blob/4f85a9989373fae228ab7969b671b6817d5ecf79/x-pack/plugins/observability_solution/infra/kibana.jsonc#L4 \cc @elastic/obs-ux-logs-team & @elastic/obs-ux-infra_services-team Contributes to: elastic#194817
## Summary Hopefully assigning to not too large of a reviewers list. ### Reasons for Assignments Assigned lists due to the api called is defined here: https://github.com/elastic/kibana/blob/4ed9e5173c6d56a949c15fcb8aa223cfc64fc5f1/x-pack/test/security_solution_cypress/cypress/tasks/api_calls/exceptions.ts#L54 \cc @elastic/security-detection-engine Assigned Logs Shared due to #189646 \cc @elastic/obs-ux-logs-team Assigned logstash due to https://github.com/elastic/kibana/blob/4ed9e5173c6d56a949c15fcb8aa223cfc64fc5f1/x-pack/plugins/logstash/kibana.jsonc#L4 \cc @elastic/logstash Assigned metris ui due to https://github.com/elastic/kibana/blob/4f85a9989373fae228ab7969b671b6817d5ecf79/x-pack/plugins/observability_solution/infra/kibana.jsonc#L4 \cc @elastic/obs-ux-logs-team & @elastic/obs-ux-infra_services-team Contributes to: #194817 --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Elastic Machine <[email protected]>
Summary
This implements #186824.
A new API has been added so that automated corrective actions can be applied.
UI / UX