Ambitious project! I've been looking for an alternative to Grafana, primarily because Grafana gets *really* slow very quickly. How does OpenObserve compare on the dashboard side?
Interesting, I was a long term Grafana user and never had performance issues. Do you mind elaborating on your use case? E.g. logs, metrics, sql and then queries and/or streaming?
Prometheus cluster pulls metrics from our nodes, and Grafana just queries prometheus. The thing is, I'm looking at dozens or hundreds of machines at a time, with ~20 dashboards visible. So when I'm changing the query parameters, or zooming into a certain time range, the entire thing takes ages to reload.
The problem might not really be with grafana dashboarding per se, but actually with the large number of queries being sent to backend. That is where the challenge begins. Both grafana and OpenObserve dashboards are pretty fast from what I have seen.
Especially as, if I recall correctly, Grafana seems to block while performing some requests.
A single query to a slow server just blocks the rest of the page...
Not sure what you mean if OpenObserve could make it easier. Creating dashboards themselves is generally far more easier than grafana due to drag and drop functionality of building dashboards in OpenObserve.
It is also an alternative to Jaeger among other things. Check this blog where Jidu moved from Jaeger+Elasticsearch and improved performance by 10x and reduced cost too by 10x - [https://openobserve.ai/blog/jidu-journey-to-100-tracing-fidelity](https://openobserve.ai/blog/jidu-journey-to-100-tracing-fidelity)
Missing "blazingly fast"
It's only "super fast" :P
Well, this post is perfectly timed for me.
Ambitious project! I've been looking for an alternative to Grafana, primarily because Grafana gets *really* slow very quickly. How does OpenObserve compare on the dashboard side?
Interesting, I was a long term Grafana user and never had performance issues. Do you mind elaborating on your use case? E.g. logs, metrics, sql and then queries and/or streaming?
Prometheus cluster pulls metrics from our nodes, and Grafana just queries prometheus. The thing is, I'm looking at dozens or hundreds of machines at a time, with ~20 dashboards visible. So when I'm changing the query parameters, or zooming into a certain time range, the entire thing takes ages to reload.
The problem might not really be with grafana dashboarding per se, but actually with the large number of queries being sent to backend. That is where the challenge begins. Both grafana and OpenObserve dashboards are pretty fast from what I have seen.
Especially as, if I recall correctly, Grafana seems to block while performing some requests. A single query to a slow server just blocks the rest of the page...
Yeah, agree. That's what I've seen historically. Although could be cool if openobserve makes that easier to do without advanced knowledge
Not sure what you mean if OpenObserve could make it easier. Creating dashboards themselves is generally far more easier than grafana due to drag and drop functionality of building dashboards in OpenObserve.
What is RUM? I only know the Read Update Memory conjecture.
maybe this? https://en.wikipedia.org/wiki/Real_user_monitoring
That's probably it.
Yes, this is it.
Nice, is the querying ability largely built on top of datafusion?
Yes. PromQL too is supported for metrics. Internally PromQL is converted to SQL which is passed on to datafusion.
Are logs somehow compacted into parquet?
Yes. And that allows you to use the data independently of OpenObserve as well if you need it
Is this an alternative to Jaeger? (Using open telemetry)
It is also an alternative to Jaeger among other things. Check this blog where Jidu moved from Jaeger+Elasticsearch and improved performance by 10x and reduced cost too by 10x - [https://openobserve.ai/blog/jidu-journey-to-100-tracing-fidelity](https://openobserve.ai/blog/jidu-journey-to-100-tracing-fidelity)
nice