test: update dashboard test cases and remove unused files (#9944)
PR Type
Tests
Description
Enable previously skipped dashboard tests
dashboard-filter.spec.js,dashboard-html-chart.spec.js,dashboard.spec.jsUpdate relative time and endpoint in filter spec
Remove
visualization-vrl.spec.jsand CI workflow entryFix panel deletion call in
dashboard.spec.js
Diagram Walkthrough
flowchart LR DF["dashboard-filter.spec.js updated"] --> CW["CI workflow updated"] HC["dashboard-html-chart.spec.js enabled"] --> CW DS["dashboard.spec.js updates"] --> CW VRL["visualization-vrl.spec.js removed"] --> CW
File Walkthrough
Relevant files Tests
dashboard-filter.spec.js
Update filter spec timing and endpoint
tests/ui-testing/playwright-tests/Dashboards/dashboard-filter.spec.js
- Changed default time range from 6 weeks to 30 days
- Enabled custom value search test (removed skip)
- Updated response listener to
/ _values_streamendpoint+4/-4 dashboard-html-chart.spec.js
Enable HTML chart variable test
tests/ui-testing/playwright-tests/Dashboards/dashboard-html-chart.spec.js
- Enabled variable replacement test (removed skip)
- No other logic changes
+1/-1 dashboard.spec.js
Enable dynamic filter test and remove drilldown test
tests/ui-testing/playwright-tests/Dashboards/dashboard.spec.js
- Enabled dynamic filter test (removed skip)
- Fixed panel deletion call to
dashboardPanelEdit.deletePanel
- Removed skipped drilldown feature test block
+2/-54 visualization-vrl.spec.js
Remove VRL visualization tests
tests/ui-testing/playwright-tests/Dashboards/visualization-vrl.spec.js
- Deleted VRL visualization test file entirely
- Removed all VRL-related test cases
+0/-425 Configuration changes
playwright.yml
Remove VRL test from CI workflow
.github/workflows/playwright.yml
- Removed
visualization-vrl.spec.jsfrom CI run_files list
- Updated workflow to skip VRL tests
+0/-1
Modern observability platform: 10x easier, 140x lower storage cost, high performance, petabyte scale - Elasticsearch/Splunk/Datadog alternative for logs, metrics, traces, frontend monitoring and more.
OpenObserve (O2 for short) is a cloud-native observability platform built specifically for logs, metrics, traces, analytics, frontend monitoring and more. Start with a single binary that scales to terabytes, or deploy in High Availability mode for petabyte-scale workloads.
Why OpenObserve?
1. Simplicity
It is straightforward and easy to operate compared to other observability tools that require understanding and tuning numerous settings. Get OpenObserve up and running on a single node in under 2 minutes. No PhD required.
2. Cost Efficiency
You can reduce your log storage costs by ~140x compared to Elasticsearch. Yes, you read that right - 140x, not a typo. This is achieved through columnar storage format (Parquet), aggressive compression, and S3-native architecture. See the detailed comparison below where we ingested the same amount of data in OpenObserve and Elasticsearch and found OpenObserve storage cost to be ~140x lower. Your CFO will love you.
3. Performance
OpenObserve delivers better performance than Elasticsearch while using 1/4th the hardware resources. Users report faster search performance and significantly faster analytics queries. The columnar storage format (Parquet) with intelligent partitioning and caching reduces the search space by up to 99% for most queries. Built in Rust for memory safety and high performance, OpenObserve handles thousands of concurrent users querying a single cluster simultaneously.
4. Single Binary Platform
Consolidate metrics, logs, and traces on one single, efficient platform. OpenObserve comes with its own UI, eliminating the need for multiple installations. One binary to rule them all.
🎥 Introduction Video
🏗️ Architecture
OpenObserve achieves 140x lower storage costs and high performance through its modern architecture:
This architecture delivers 140x cost savings while providing better performance than Elasticsearch.
Scale & Deployment
High Availability & Disaster Recovery
Deploy in High Availability mode with clustering for mission-critical workloads requiring maximum uptime and performance.
Low RPO/RTO: OpenObserve’s stateless architecture with S3-backed storage enables very low Recovery Point Objective (RPO) and Recovery Time Objective (RTO). Stateless nodes can be rapidly restarted, and data durability is guaranteed by S3’s 99.999999999% (11 nines) durability. That’s a lot of nines.
Read detailed architecture documentation →
Read enterprise deployment guide →
🌟 Capabilities
For a full list of features, check the documentation.
⚡️ Quick start
🐳 Docker:
For other ways to quickly install OpenObserve or use OpenObserve cloud, check quickstart documentation.
For installing OpenObserve in High Availability mode, check High Availability deployment documentation.
🏆 Production Ready
OpenObserve is battle-tested in production environments worldwide (and by “battle-tested”, we mean real production traffic, not just our test lab):
Read customer stories →
📷 Screenshots
OpenObserve includes a powerful web UI for logs, traces, dashboards, alerts, and more.
Logs Search
Distributed Tracing
Trace details page with full request flow visualization:
Dashboards
Frontend Monitoring
Real user monitoring with session replay:
See more screenshots
Home
Golden Metrics from Traces
More Dashboard Examples
Performance Analytics
Error Tracking
Alerts
Streams
Ingestion
Pipeline
Functions
🔐 Security & Compliance
Security Features
Compliance Certifications
OpenObserve meets the stringent security and compliance requirements of regulated industries including finance, healthcare, and government.
⚖️ License
Open Source Edition: Licensed under AGPL-3.0. We chose AGPL to ensure that improvements to OpenObserve remain open source and benefit the entire community. This license protects the commons while still allowing free commercial use.
Enterprise Edition: Licensed under a commercial Enterprise License Agreement, not AGPL. This provides additional flexibility for enterprise deployments and eliminates any concerns about AGPL requirements.
For more details:
💼 Enterprise Support
OpenObserve is built as a true open source project, and we’re committed to the community. The open source version is feature-complete and production-ready - it includes logs, metrics, traces, dashboards, alerts, pipelines, and everything you need to run observability at scale. It will always remain actively maintained and free to use without restrictions.
Enterprise Edition
For organizations requiring enterprise-grade features and support, we offer an Enterprise edition with:
Enterprise Features:
Enterprise Support & SLAs:
Pricing:
For enterprise inquiries and custom deployments, contact our sales team.
🤝 Contributing
We welcome contributions from the community! Whether you’re fixing bugs, adding features, improving documentation, or sharing feedback, your help makes OpenObserve better for everyone.
To get started, please read our Contributing Guide which covers:
🌍 Community
The best way to get help, share ideas, and connect with other OpenObserve users is through our community channels. We’re a friendly group of developers, operators, and observability enthusiasts.
🔗 Join us on Slack
Our Slack community is the most active place for:
Join the conversation →
📱 Join OpenObserve community on WeChat
Other ways to connect
❓ FAQ
How does OpenObserve achieve 140x lower storage costs?
Through a combination of Parquet columnar storage format (efficient compression), S3-native architecture (leveraging inexpensive object storage). See the detailed comparison chart in the “Why OpenObserve?” section above.
What are the limitations?
All data in OpenObserve is immutable - once ingested, it cannot be modified or deleted (only entire retention periods can be dropped). This is by design and is actually a feature for logs and compliance requirements, ensuring data integrity and audit trails.
Is this production-ready?
Yes. OpenObserve is running in production with thousands of deployments worldwide, including environments processing in excess of 2 PB/day. See our customer stories for real-world examples.
How does query performance compare to Elasticsearch?
OpenObserve delivers better performance than Elasticsearch for most workloads. Users report faster search performance and significantly faster analytics queries, all while using 1/4th the hardware resources. The columnar storage format (Parquet) is particularly effective for complex aggregations and analytics workloads.
Is there a steep learning curve?
No. OpenObserve is designed to be intuitive from day one:
Most users are productive within hours, not weeks. Some even claim minutes, but we’ll let you be the judge.
🔐 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:
Generate the SBOM:
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:
Generate the SBOM: