Framer — Launch websites with enterprise needs at startup speeds.
Launch websites with enterprise needs at startup speeds.
Promoted
Maker
📌
Hey everyone!
I’m Prabhat Sharma, and we’re incredibly excited to share OpenObserve with the Product Hunt community today.
Observability has become a massive operational burden for engineering teams. Between managing complex, resource-heavy stacks and the technical debt of fragmented data, the status quo is broken. We built OpenObserve because we believe you shouldn't have to choose between deep visibility and system simplicity.
OpenObserve is a cloud-native observability platform built in Rust that handles logs, metrics, and traces in a single, high-performance engine. By using a stateless architecture and leveraging your preferred object storage, we’ve made it possible to manage petabytes of data with a significantly smaller infrastructure footprint than traditional tools.
Why OpenObserve?
Built for Performance – Written in Rust with a stateless architecture. It’s incredibly fast and remarkably light on system resources.
Storage Efficiency – Store your data on S3/MinIO/GCS instead of relying on complex block storage. Capture all your data without the need for aggressive "sampling."
Unified Experience – Query logs, metrics, and traces using familiar SQL. No more context-switching between three different tools to find one root cause.
Drop-in Compatibility – Use your existing collectors. We are API-compatible with Prometheus, FluentBit, OpenTelemetry, and Vector.
AI-Powered Insights – Use our native AI Assistant to query your data using natural language or let the SRE Agent correlate incidents automatically.
Whether you’re a startup looking for visibility from day one or an enterprise seeking a streamlined "log-and-analyze" workflow, OpenObserve is built for you.
We’re in active development and would love to hear your feedback, feature requests, and critiques!
I've been using OpenObserve for the last two years, and must say quite impressed with the features and functionality they were able to add over this time. In the beginning I longed for permissions, patterns, and parity. Lo and behold, they've implemented all that and more. Things have definitely gotten quite nice, and continue to improve daily.
OpenObserve comes through in the clutch, its alerts, notifications, and dashboards are powerful and very flexible. Ingestion is also very easy, you can either pass yourself via endpoints/kinsesis/curl, etc, or leverage standard system agents.
They are also very quick to take feedback and provide support as needed. I look forward to the new features and updates they're adding. Hopefully they remain focused on what is most needed in the platform to ensure continue growth, stability, and use.
At this point I would definitely consider it an almost drop-in replacement for most of the core DataDog logging and observability features, and in some cases they exceed them, such as the current alerts and dashboards.
There are some things I wish they supported sooner, and some things I push for them to support, but all in all a very positive experience and happy I was able to start fresh in several projects with O2 and leave DataDog (its obscene billing) and the others firmly behind.
Report
Maker
Thanks a lot @asherraph . You have been an early supporter and have helped us improve many features. Your support means a lot to us.
Report
Maker
@asherraph - Your feedback has been so important to us. Just wondering, is there any feature or release over the past year where you've seen your direct feedback applied?
Hey everyone. We built OpenObserve to fix the headaches of complex observability, but the community is what actually shaped it. The GitHub stars, the feedback, the bug reports, the honest conversations.. we owe our continued success to you.
I'll be hanging out here - happy to answer any questions!
Report
Maker
Hi everyone! 🙋 It's been a wild journey moving from our first lines of Rust code to this launch. OpenObserve was really shaped by our early open-source contributors who pushed us to make it API-compatible with things like Prometheus and OpenTelemetry.
We’re just getting started with our AI-native features, and I’d love to hear from this community: how can we make your on-call rotations or debugging sessions less painful? Drop your questions below!
Report
Maker
Expanding on our AI-Powered Insights: We’re big believers that AI should be a co-pilot, not a black box. While our automated SRE agent handles the heavy lifting of the analysis, we make sure to present every correlated signal. It’s all about keeping the human in the loop—giving SREs the full context they need to make fast, informed decisions with total confidence.
Report
For teams adopting OpenObserve today, what are some practical entry points into AIOps, are you focusing more on anomaly detection, intelligent alerting, or incident summarization first?”
Hey everyone!
I’m Prabhat Sharma, and we’re incredibly excited to share OpenObserve with the Product Hunt community today.
Observability has become a massive operational burden for engineering teams. Between managing complex, resource-heavy stacks and the technical debt of fragmented data, the status quo is broken. We built OpenObserve because we believe you shouldn't have to choose between deep visibility and system simplicity.
OpenObserve is a cloud-native observability platform built in Rust that handles logs, metrics, and traces in a single, high-performance engine. By using a stateless architecture and leveraging your preferred object storage, we’ve made it possible to manage petabytes of data with a significantly smaller infrastructure footprint than traditional tools.
Why OpenObserve?
Built for Performance – Written in Rust with a stateless architecture. It’s incredibly fast and remarkably light on system resources.
Storage Efficiency – Store your data on S3/MinIO/GCS instead of relying on complex block storage. Capture all your data without the need for aggressive "sampling."
Unified Experience – Query logs, metrics, and traces using familiar SQL. No more context-switching between three different tools to find one root cause.
Drop-in Compatibility – Use your existing collectors. We are API-compatible with Prometheus, FluentBit, OpenTelemetry, and Vector.
AI-Powered Insights – Use our native AI Assistant to query your data using natural language or let the SRE Agent correlate incidents automatically.
Whether you’re a startup looking for visibility from day one or an enterprise seeking a streamlined "log-and-analyze" workflow, OpenObserve is built for you.
We’re in active development and would love to hear your feedback, feature requests, and critiques!
Get started:
Try OpenObserve Cloud: https://openobserve.ai/
Explore the Docs: https://openobserve.ai/docs/
Check us out on GitHub:https://github.com/openobserve/openobserve
Mesh
I've been using OpenObserve for the last two years, and must say quite impressed with the features and functionality they were able to add over this time. In the beginning I longed for permissions, patterns, and parity. Lo and behold, they've implemented all that and more. Things have definitely gotten quite nice, and continue to improve daily.
OpenObserve comes through in the clutch, its alerts, notifications, and dashboards are powerful and very flexible. Ingestion is also very easy, you can either pass yourself via endpoints/kinsesis/curl, etc, or leverage standard system agents.
They are also very quick to take feedback and provide support as needed. I look forward to the new features and updates they're adding. Hopefully they remain focused on what is most needed in the platform to ensure continue growth, stability, and use.
At this point I would definitely consider it an almost drop-in replacement for most of the core DataDog logging and observability features, and in some cases they exceed them, such as the current alerts and dashboards.
There are some things I wish they supported sooner, and some things I push for them to support, but all in all a very positive experience and happy I was able to start fresh in several projects with O2 and leave DataDog (its obscene billing) and the others firmly behind.
Thanks a lot @asherraph . You have been an early supporter and have helped us improve many features. Your support means a lot to us.
@asherraph - Your feedback has been so important to us. Just wondering, is there any feature or release over the past year where you've seen your direct feedback applied?
@asherraph thank you for your support!
Hey everyone. We built OpenObserve to fix the headaches of complex observability, but the community is what actually shaped it. The GitHub stars, the feedback, the bug reports, the honest conversations.. we owe our continued success to you.
I'll be hanging out here - happy to answer any questions!
Hi everyone! 🙋 It's been a wild journey moving from our first lines of Rust code to this launch. OpenObserve was really shaped by our early open-source contributors who pushed us to make it API-compatible with things like Prometheus and OpenTelemetry.
We’re just getting started with our AI-native features, and I’d love to hear from this community: how can we make your on-call rotations or debugging sessions less painful? Drop your questions below!
Expanding on our AI-Powered Insights: We’re big believers that AI should be a co-pilot, not a black box. While our automated SRE agent handles the heavy lifting of the analysis, we make sure to present every correlated signal. It’s all about keeping the human in the loop—giving SREs the full context they need to make fast, informed decisions with total confidence.
For teams adopting OpenObserve today, what are some practical entry points into AIOps, are you focusing more on anomaly detection, intelligent alerting, or incident summarization first?”
Curious to know.
Congratulations
Thank you so much@madalina_barbu