#5307 ### Summary From the issue description: > We would like to deprecate various old migrations. If these migrations are marked as deprecated in v0.14.0, then they will be officially removed from the app initialization logic in v0.17.0. > > The ramification of this is that users will not be able to upgrade directly from versions < 0.14.0 to versions >= v0.17.0. Instead, for example, a user on v0.13.0 would first need to upgrade to v0.14.0, and then from v0.14.0 they could upgrade to v0.17.0. > > Removing these migrations will reduce the risk that the behavior of some of these migrations, particularly those that reference data structures or logic in other parts of the application code base, accidentally changes in the future resulting in inconsistent migration behavior. ### Technical details This PR just marks certain sections of the code as deprecated. This deprecated logic will be removed some time after v0.17.0. ### 📣 Note to reviewers Please comment on any additional migrations that we would like to deprecate for v0.14.0 and I can include it in this PR. Or feel free to commit to this branch to mark additional migrations as deprecated. If you commit to this branch please use the `#[deprecated]` attribute if possible or include the word `deprecated` in a comment on the code; I plan on searching the source code for the word `"deprecated"` after v0.17.0 to remove the deprecated code, so this would help with that. ### Todo in v0.14.0 release We will want to include information in our official v0.14.0 release notes about... - The deprecation of migration/upgrade logic - The incompatibility of direct upgrades from < v0.14.0 to >= v0.17.0 - Instructions for upgrading from < v0.14.0 to >= v0.17.0 - Users will first need to upgrade to some version >= v0.14.0 and < v0.17.0. And then they will be able to upgrade to v0.17.0 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced error handling for the `delete-parquet` command, providing clearer feedback on deletion success or failure. - Added deprecation warnings for several commands and functions, indicating future removals. - **Bug Fixes** - Improved feedback for unsupported components in the `view` command. - **Documentation** - Added comments clarifying the deprecation status of certain migration logic and functions. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
🚀 10x easier, 🚀 140x lower storage cost, 🚀 high performance, 🚀 petabyte scale - Elasticsearch/Splunk/Datadog alternative for 🚀 (logs, metrics, traces).
OpenObserve (O2 for short) is a cloud-native observability platform built specifically for logs, metrics, traces, analytics, RUM (Real User Monitoring - Performance, Errors, Session Replay) designed to work at petabyte scale.
It is straightforward and easy to operate, in contrast to Elasticsearch, which requires understanding and tuning numerous settings. Get OpenObserve up and running in under 2 minutes.
OpenObserve serves as a seamless replacement for Elasticsearch for users who ingest data using APIs and perform searches. OpenObserve comes with its own user interface, eliminating the need for separate installation.
You can reduce your log storage costs by ~140x compared to Elasticsearch by using OpenObserve. Below, we present the results from pushing logs from our production Kubernetes cluster to both Elasticsearch and OpenObserve using Fluent Bit.
🎥 Introduction Video
🌟 Features:
- Logs, Metrics, Traces: Comprehensive support for various data types.
- OpenTelemetry Support: Full compatibility with OTLP for logs, metrics, and traces.
- Real User Monitoring (RUM): Includes performance tracking, error logging, and session replay.
- Dashboards, Reports, Alerts: Features over 18 different chart types for comprehensive data visualization for on-the-fly analysis and reporting along with alerting.
- Pipelines: Enrich, redact, reduce, normalize data on the fly. Stream processing for logs to metrics and more.
- Advanced Embedded GUI: Intuitive and user-friendly interface.
- SQL and PromQL Support: Query logs and traces with SQL, and metrics with SQL and PromQL.
- Single Binary or HA Installation: Install using a single binary for small deployments or in HA mode for large deployments.
- Versatile Storage Options: Supports local disk, S3, MinIO, GCS, Azure Blob Storage.
- High Availability and Clustering: Ensures reliable and scalable performance.
- Dynamic Schema: Adapts to your data structure seamlessly.
- Built-in Authentication: Secure and ready to use.
- Ease of Operation: Designed for simplicity and efficiency.
- Seamless Upgrades: Hassle-free updates.
- Multilingual UI: Supports 11 languages, including English, Spanish, German, French, Chinese, and more.
For a full list of features, check the documentation.
⚡️ Quick start
🐳 Docker:
docker run -d \
--name openobserve \
-v $PWD/data:/data \
-p 5080:5080 \
-e ZO_ROOT_USER_EMAIL="root@example.com" \
-e ZO_ROOT_USER_PASSWORD="Complexpass#123" \
public.ecr.aws/zinclabs/openobserve:latest
🐙 Docker Compose:
services:
openobserve:
image: public.ecr.aws/zinclabs/openobserve:latest
restart: unless-stopped
environment:
ZO_ROOT_USER_EMAIL: "root@example.com"
ZO_ROOT_USER_PASSWORD: "Complexpass#123"
ports:
- "5080:5080"
volumes:
- data:/data
volumes:
data:
For other ways to quickly install OpenObserve or use OpenObserve cloud, check quickstart documentation.
For installing OpenObserve in HA mode, check HA deployment documentation.
📷 Screenshots
Home
Logs
Traces (OpenTelemetry)
Golden metrics based on traces

Visualizations and Dashboards
Front end monitoring
Alerts
Streams
Ingestion
SBOM
Software Bill of Materials for OpenObserve
Rust
SBOM can be found here. You can analyze it using dependency track.
In order to generate the SBOM, you can use the following commands:
Install cargo-cyclonedx:
cargo install cargo-cyclonedx
Generate the SBOM:
cargo-cyclonedx cyclonedx
JavaScript
SBOM can be found here. You can analyze it using dependency track.
In order to generate the SBOM, you can use the following commands:
Install cyclonedx-npm:
npm install --global @cyclonedx/cyclonedx-npm
Generate the SBOM:
cd web
cyclonedx-npm > sbom.json
⚖️ License
OpenObserve is licensed under the AGPL-3.0 license. For more details, see the LICENSE.
🌍 Community
🔗 Join OpenObserve community on Slack
Easiest way to get support is to join the Slack channel.
📱 Join OpenObserve community on WeChat















