You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Release 3.0] Planned Breaking Changes for 3.0 in Plugin
As mentioned in this META Issue, we want to track and increase transparency around the breaking changes planned for the 3.0 release across participating plugins.
Please kindly document all planned breaking changes related to your plugin for 3.0 here, by sharing detailed information about the changes, expected impact, and any guidance for users or other teams to adapt to the changes.
If needed, please also prepare PRs on documentation-website changes as part of the 3.0 release process.
Overall, this would help us deliver a smooth and seamless upgrade experience.
Thanks.
The text was updated successfully, but these errors were encountered:
We are not deprecating the Observability backend in 3.0 version.
## Deprecation and remove post cohesion in 3.0
This plugin supports dashboards-observability for CRUD operations on the Observability index. Based on the proposal from in dashboards-observability 3.0 plan many components have already been migrated to the .kibana index and the rest are on path of removal in 3.0. Hence, we propose to remove the observability backend plugin in 3.0 release.
Path to deprecation for Backend Observability Plugin
Today Observability backend only supports the dashboards-observability plugin for storage operations. It acts as a backend wrapper on OpenSearch with security based access for auth. This plugin can be removed if all our existing plugin objects are moved to .kibana. OpenSearch security plugin and Dashboards core handle the auth and access for the .Kibana index.
Currently, post the cohesion project we still have some un-migrated objects in the observability index. Move existing un-migrated objects to .kibana index.
Logs Explorer
Saved Visualizations
Saved Searches
Observability Dashboards
Notebooks
Migrate all Applications analytics objects to .kibana.
[Release 3.0] Planned Breaking Changes for 3.0 in Plugin
As mentioned in this META Issue, we want to track and increase transparency around the breaking changes planned for the 3.0 release across participating plugins.
Please kindly document all planned breaking changes related to your plugin for 3.0 here, by sharing detailed information about the changes, expected impact, and any guidance for users or other teams to adapt to the changes.
If needed, please also prepare PRs on documentation-website changes as part of the 3.0 release process.
Overall, this would help us deliver a smooth and seamless upgrade experience.
Thanks.
The text was updated successfully, but these errors were encountered: