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
We are writing to inform you about important changes to the notebooks feature in the dashboards-observability component:
Deprecation Timeline:
Version 2.19: The legacy notebooks feature will be deprecated.
Version 3.0: The legacy notebooks feature will be completely removed.
Storage Changes:
Legacy notebooks are stored in the .opensearch-observability index.
New notebooks (from version 2.17 onwards) are stored in the .kibana index.
Migration Path:
If you are using legacy notebooks and wish to continue using them in version 3.0:
a. Upgrade to version 2.17 or later (but before 3.0).
b. Migrate your notebooks from the legacy storage to the new storage.
Action Required:
Users with legacy notebooks should plan to migrate their data before upgrading to version 3.0.
We strongly recommend that all users transition to the new notebook storage system as soon as possible to ensure a smooth experience in future releases. We appreciate your understanding and support as we continue to improve the OpenSearch ecosystem. If you have any questions or concerns, please don't hesitate to reach out to our community channels.
Deprecation Notice: dashboards-observability - legacy notebooks feature
We are writing to inform you about important changes to the notebooks feature in the dashboards-observability component:
Deprecation Timeline:
Storage Changes:
.opensearch-observability
index..kibana
index.Migration Path:
a. Upgrade to version 2.17 or later (but before 3.0).
b. Migrate your notebooks from the legacy storage to the new storage.
Action Required:
We strongly recommend that all users transition to the new notebook storage system as soon as possible to ensure a smooth experience in future releases. We appreciate your understanding and support as we continue to improve the OpenSearch ecosystem. If you have any questions or concerns, please don't hesitate to reach out to our community channels.
For more information, please refer to: #2311
Thank you for your continued support of OpenSearch.
The text was updated successfully, but these errors were encountered: