- Gartner Peer Insights (review platform)
- OpenObserve’s Gartner Peer Insights vendor page shows a small number of reviews with a very high average rating in the observability platforms category.
- Note: full-text review access may be partially gated; in this run we could access the vendor summary counts and a limited review snippet.
- Trustpilot (consumer-style review platform)
- Trustpilot shows a very small sample size with a mixed/middling aggregate score driven by a single entry.
- A single one-star review alleges:
- “Deceptive licensing” around a marketed “free” capacity but receiving a time-limited key instead
- “Buggy software” and “terrible support”
- Higher-than-expected RAM usage
- UI bugs (example: saving headers in alert destinations throws errors)
- Recommends alternatives like Grafana+Loki or VictoriaLogs
- Because this is a single review, it’s not statistically representative—but it is a strong signal to validate licensing terms, support responsiveness, and UI maturity before committing.
- Reddit (community/social)
- Licensing / open-core skepticism
- A thread titled “So OpenObserve is ‘open-source’… until you actually try using it” argues that the GitHub repo shows an open-source license, while screenshots/readme might imply features (e.g., SSO/RBAC) that some perceive as paid-only; commenters call this misleading and ask for “crystal clear” OSS vs Enterprise delineation.
- The thread includes a response from someone representing OpenObserve stating they have offered an Enterprise-free tier up to a stated daily cap for self-hosted downloads/pricing for years and that they’ve updated the README for clarity (indicating at minimum: messaging confusion existed in the market).
- Performance/cost anecdotes
- A community post claims a side-by-side ingestion test where Elasticsearch consumed substantially more RAM and CPU than OpenObserve on the same hardware and large log volume; a repository with test details was referenced.
- A self-hosted thread includes an anecdote of multi-day queries returning in a few seconds on a modest local VM (limited cores, modest RAM, spinning disk) for a home-network-scale event volume (hundreds of thousands to low millions of events/day).
- “Is it good?” evaluation threads
- A self-hosted thread includes a user who tested multiple tools (Grafana Loki, Graylog, OpenObserve, Qryn, SigNoz, VictoriaLogs) at very large insert volumes, indicating OpenObserve is commonly evaluated in “ELK/Loki replacement” bake-offs.
- Why customers chose this product over alternatives
- Reviews and community comments suggest typical drivers:
- Desire for a simpler “single platform” versus multi-tool stacks.
- Expectations of more predictable costs and lower storage/infra footprint versus Elasticsearch/Datadog.
- Preference for open-source availability and self-host control.
- Why some customers left for competitors (churn reasons)
- Based on negative feedback and recurring themes in threads:
- Confusion or dissatisfaction about licensing/feature gating (open-source vs enterprise boundaries).
- UI/UX maturity complaints (clunky admin UI, bugs).
- Enterprise procurement requirements (e.g., guaranteed support, artifacts, data residency) may push teams to larger vendors.
- Specific outcomes customers achieved (with metrics when available)
- Community claims include substantial reductions in CPU/RAM at ingest compared with Elasticsearch; these are anecdotal, not independently verified, and should be reproduced in your environment.
- Deal-breakers and reasons customers didn't purchase
- Potential deal-breakers implied by reviews:
- Perception of an “open-core trap” / unclear licensing.
- Concern about operational maturity and bug surface area.
- Requirement for advanced IAM/SSO/RBAC in the free tier.
Case Studies
- Vendor-published case study: “How Avatar Achieved SOC 2 Compliance, Improved Uptime, and Saved Costs with OpenObserve”
- Claims include SOC 2 compliance support and improved uptime/cost savings.
- Critical evaluation:
- This is vendor-published marketing content; methodology and counterfactuals are not independently audited in the captured sources.
- Treat reported outcomes as directional; request detailed baseline metrics, time window, and architecture diagrams from the vendor to validate applicability to your environment.
- Additional vendor content suggesting benchmarking
- OpenObserve blog series comparing Datadog vs OpenObserve (e.g., pipelines, log management) describes hands-on comparison setups.
- Critical evaluation:
- These pieces are produced by the vendor; while informative, they may reflect favorable configurations and assumptions. Buyers should attempt independent reproduction or request third-party benchmarks.