-
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
[Reporting] Breaking: Remove setting for Reporting index #113803
[Reporting] Breaking: Remove setting for Reporting index #113803
Conversation
Pinging @elastic/kibana-reporting-services (Team:Reporting Services) |
e0ee54e
to
20eb83b
Compare
💚 Build Succeeded
Metrics [docs]Page load bundle
To update your PR or re-run it, just comment with: |
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.
Did not test locally but these changes look good to me 🍻
Couple of questions:
- Do we have telemetry on how often this setting is being used in the wild?
- How are we helping "broken" users to migrate?
@jloleysens we do NOT have telemetry to see how often this setting is used. The meta issue on this is here: #82020 I presume this is a high-visibility breaking change as it affects other plugins as well.
Spaces should be used when multitenancy is needed. The system indices were customizable in 7.x, which is the same release cycle that introduced Spaces. From the meta issue:
This is an issue for Reporting: reports are not importable into Kibana. The only way a user will be able to view historical reports that were in a custom index is to download them to another form of storage before upgrading to 8.0. |
Thread on this topic: #82020 (comment) |
Summary
Address #101964 for Reporting