FAQs
Everything you need to know about OpenObserve. Can't find the answer to a question you have? No worries - get in touch and let's chat!
What is OpenObserve?
OpenObserve is an open-source observability platform, built in rust for high performance that unifies logs, metrics, traces, front end monitoring, pieplines, dashboards, alerts, reports and more into a single system. It provides real-time analytics through a custom built columnar storage engine optimized for observability data. The platform offers efficient storage using object storage solutions like S3 (or any s3 API compatible service), GCS, Azure Blob or MinIO, making it significantly more cost-effective than traditional solutions. OpenObserve supports both cloud and self-hosted deployments, with a focus on performance and resource efficiency.
How does OpenObserve handle log management?
OpenObserve processes logs through an efficient pipeline that includes real-time parsing and indexing. Logs are stored in columnar format using Apache Parquet, enabling fast queries and efficient storage. The platform supports various ingestion methods including HTTP endpoints, popular log forwarders (Vector, Fluentd, Fluent Bit, otel-collector), and cloud provider integrations. Log processing can be customized using pipelines and Vector Remap Language (VRL) functions for parsing, transformation, and enrichment. The system supports both structured and unstructured logs with automatic field detection and indexing.
How does OpenObserve handle metrics?
OpenObserve provides comprehensive metrics support with multiple collection methods. It accepts metrics through OpenTelemetry, Prometheus remote write, and direct ingestion. The platform supports all standard metric types including counters, gauges, and histograms. Metrics can be queried using both SQL and PromQL, allowing for complex analysis and aggregations. The storage engine is optimized for time-series data, enabling efficient storage and fast retrieval of metric data.
What are OpenObserve's distributed tracing capabilities?
OpenObserve implements distributed tracing through OpenTelemetry integration. The platform collects trace data using the OTLP protocol and maintains trace context using W3C trace context standards. Traces include detailed span information with timing, service relationships, and custom attributes. The system provides service maps for dependency visualization and supports both manual and automatic instrumentation through OpenTelemetry SDKs.
How does OpenObserve's frontend monitoring work?
OpenObserve's Real User Monitoring (RUM) capabilities are implemented through a JavaScript SDK that collects performance metrics, user interactions, and errors. The system captures Core Web Vitals, page load timing, and resource performance data. Error tracking includes automatic capture of JavaScript errors with full stack traces and context. The platform provides real-time analysis of frontend performance and user experience data.
What observability pipeline capabilities does OpenObserve offer?
OpenObserve implements observability pipelines using conditions for routing Vector Remap Language (VRL) for transformation and enrichment. The platform supports both real-time and scheduled pipelines with VRL for data processing. Pipelines can include multiple processing steps with conditions and enrichment tables. The system provides monitoring and debugging tools for pipeline execution, with support for testing transformations before deployment with an intuitive GUI.
How does OpenObserve's alerting system work?
OpenObserve provides a flexible alerting system that supports both scheduled and real-time alerts. Alerts can be configured using SQL queries for logs and traces, and PromQL for metrics. The system includes support for occurrence thresholds, evaluation windows, and silence periods. Notifications can be sent to various destinations including email, Slack, and webhook endpoints. Alert conditions can use aggregations and complex query logic for precise monitoring.
What visualization capabilities does OpenObserve provide?
OpenObserve offers comprehensive visualization through its dashboard feature. The platform supports over 19 different chart types including time-series graphs, tables, heatmaps, and gauges. Custom charts are supported too that allow you to build over 300 different chart types allowing you to unleash your creativity. Dashboards can be created using SQL or PromQL queries, with support for variables and templating. The system provides real-time updates, drill-down capabilities, and sharing options. Prebuilt community dashboards are available for common use cases and can be customized as needed.
How does OpenObserve handle multi-tenancy?
OpenObserve is built to be multi-tenant from ground up. It implements multi-tenancy through organizations. Each organization maintains isolated data storage and access controls. The system supports role-based access control (RBAC) for fine-grained permissions management. Users can be assigned to multiple organizations with different roles. The platform ensures data isolation at both storage and query levels.
What deployment options are available for OpenObserve?
OpenObserve can be deployed in multiple ways to suit different requirements. The platform offers a cloud service (OpenObserve Cloud) with a generous free tier. For self-hosted deployments, OpenObserve can be installed on Kubernetes using Helm charts, or on virtual machines using Docker containers. The system supports various object storage backends including AWS S3, Google Cloud Storage, MinIO, and Azure Blob Storage. Any other object store that offers s3 compatible APIs including ceph, digital ocean, tencent cloud, civo and more can be used too.
How does OpenObserve achieve cost efficiency?
OpenObserve's cost efficiency comes from its architectural design choices. The platform uses columnar storage (Apache Parquet) which provides excellent compression ratio. Data is stored in object storage, significantly reducing storage costs compared to traditional solutions. The system implements efficient indexing strategies and query optimization to minimize compute requirements. The stateless architecture allows for flexible scaling based on actual needs.
What security features does OpenObserve include?
OpenObserve implements comprehensive security features including authentication, authorization, and audit logging. The platform supports single sign-on (SSO) through below providers:
- LDAP
- GitHub
- SAML 2.0
- GitLab
- OpenID Connect
- OAuth 2.0
- Microsoft
- AuthProxy
- Bitbucket Cloud
- BuiltIn (local)
- OpenShift
- Atlassian Crowd
- Gitea
- OpenStack Keystone
Role-based access control (RBAC) enables fine-grained permission management.
Data encryption is supported both in transit and at rest. The system provides audit trails for user actions and data access.
How can I get started with OpenObserve?
Getting started with OpenObserve is straightforward. You can sign up for OpenObserve Cloud which offers a free tier with generous limits. For self-hosted deployments, comprehensive documentation guides you through the installation process. The platform provides quick-start guides for common use cases and integrations. Community support is available through Slack and GitHub for additional assistance.
For additional questions or detailed information, please refer to our documentation or join our community.
Openobserve Cloud Free Tier
Monthly Limits:
Ingestion - 50 GB logs, 50 GB metrics , 50 GB traces
Query volume - 200 GB
Pipelines - 50 GB of Data Processing
1K RUM & Session Replay
1K Action Script Runs
3 Users
7-Days Retention
Get started in minutes—no credit card required.
Solutions
Company
Resources
Pricing
OpenObserve Inc. © 2025
3000 Sand Hill Rd Building 1, Suite 260, Menlo Park, CA 94025