prabhatsharma

You could also try the cloud version of OpenObserve without setting it up yourself.

Not yet. Will have it in some time.

Elasticsearch compatibility is provided through a separate component. We believe that this should be a commercial solution. As a commercial entity we need to figure out ways of making money. This is one of them along with SaaS.

What is your use case?

Logs, metrics and traces are all queryable using SQL. Metrics can additionally use PromQL for querying.

We haven't compared resource usage against grafana stack. Rust is a lot more efficient than Go in general though.

Yes, you could use it. If you face any issues, let us know through github issues or on slack.

Thanks for pointing out. fixed.

We have done minimal performance testing for now. A lot of work is remaining in this area.

Thanks for pointing out. Fixed it.

Here you go - https://github.com/openobserve/openobserve/blob/main/CONTRIB...

Helm chart is available for HA mode installation that allows you to use minio/s3/gcs etc - https://openobserve.ai/docs/ha_deployment/ .

For single node installations, you can use base k8s manifests that is available using instructions at - https://openobserve.ai/docs/quickstart/#self-hosted-installa... .

Mike created a helm chart for s ingle node installation too - https://github.com/mshade/openobserve-chart/

You are right.

Yes, you understand it correctly that you can integrate existing prometheus with OpenObserve for long term storage of metrics with s3.

And yes you can get your logs there too.

You don't need grafana as OpenObserve has good dashboarding for metrics and logs built in. Still early days for OpenObserve - some features are missing and has some rough edges.

I am not sure what you mean by:

> does it mean that long term metrics mirrored from prometheus are no longer available there?

> is there any way to get just graphana plugin for self hosted deployment?

ping us on slack channel, If you are able to make friends with the team you can get anything :-) . Fair warning - We have found OpenObserve logs UI to be much smoother and advanced than grafana UI.

Glad you liked it. Yeah, resource usage is so low that some folks are running it in their homelab even on a raspberry-pi.

>Is Kibana support totally out of the question?

Actually no.

We already have a good amount of pieces in place to support kibana. 2-3 weeks of dev work and it will be ready. Just not the top priority right now though.

Yeah, Reddit is filled with horror stories from Datadog. One thread here - https://www.reddit.com/r/devops/comments/zz4naq/datadog_i_do...

Check the docs - https://openobserve.ai/docs/ingestion/traces/opentelemetry/

Logs, Metrics and traces are all queryable.

You can join Slack if you are outside of China, or wechat, if you are in China. We had some good early users whoBoth the options are available.

> headquartered in Bangalore, India This is embarrassing, just fixed it. We are a delaware based company, headquartered in San Francisco. Pure copy paste error.

Zinc Labs (Legal name) is the company behind the product OpenObserve.

Here is a quick demo - https://www.youtube.com/watch?v=fZ-ErfMdF-o . Covers basics, logs, function, dashboards. Does not cover traces and metrics.

An ask, we are getting from a lot of users. We are trying to figure out the most sophisticated and easiest way. Goal is to be able to do it in next 2-3 months. We have looked at Dex, but have not finalized on anything yet.

I think Signoz is a good product. The team really understands that it you need all 3 - logs, metrics and traces - to effectively observe and troubleshoot applications and has done a good implementation.

Certain difference on how OpenObserve is different than Signoz:

1. Built in rust for high performance and memory safety. 2. Has its own data storage engine based on open specification of Apache Parquet. This allows the data to be used by other applications outside of OpenObserve if desired. 3. Use stateless nodes in architecture (You are going to love it from maintenance point of view). 4. Use of object storage for extreme scalability and low cost. 5. Requires far lower resources than Signoz. Can practically be run using a single binary/container. There are users ingesting terabytes of data on a single node. There are people running OpenObserve on raspberry-pi. 6. A lot easier to setup and maintain. 7. Ingest and query functions are awesome. Give them a shot.

ZincSearch was an old product that we built. We don't use that in OpenObserve in any way. OpenObserve is built on top of awesome Apache arrow datafusion.

This is a good feedback. That would be true DaC (Dashboards as code). We already have plans to implement versioning of dashboards via git. Will see how to get DaC in place.

We have run internal tests to ingest 1.2 petabayte of data in 24 hours period. We are making further improvements in performance and we will publish details that will allow you to replicate it yourself.

Parquet and data fusion are awesome. Parseable is a good project. Just has logs though. No HA either. They will get there though - I don't know anyone there, but they certainly need to if not there already.

Yes, OpenObserve has a lot more use cases than parseable and our focus on ease of use has allowed us to build far more features and join them in an elegant way making it easier to use it, than any other platform out there.

Give it a shot and let us know what you think.

We wish parseable team our best wishes.

I should fix it. Metrics and traces are supported today. Logs and traces are advanced.

Metrics is still in its infancy though.

Grafana stack is cool. It solved the problem around observability for the first time in a neat and light way. Think about it however, for someone setting up their observability stack they will need to setup 4 components: Grafana (dashboarding), Loki (logs), Mimir (Metrics) and Tempo (Traces). This is a lot of work and a lot of moving parts. It is also a lot of work to maintain and upgrade. Loki, Mimir and Tempo have their own querying languages and their own quirks. Good amount of stuff to learn. It is really hard for a small team to learn and maintain all of this. Junior engineers really struggle with this and seniors resent the time they have to spend on this. Loki also has issues around high cardinality, which is a problem for many teams.

We need something new and better.

We made sure to build a solution that is easy to setup and maintain. One single binary/container for single node setup and one stack to setup/upgrade/maintain for HA setup.

We also made sure that it is easy to use and learn. We allow standard SQL to be used for querying logs, metrics and traces - nothing extra to learn here. Metrics querying is supported using PromQL too. Drag and drop for creating panels and dashboards is there too :-).

Dashboarding is supported within the same stack. No need to setup Grafana or something else separately.

OpenObserve also offer functions that grafana stack does not offer. Give it a shot, you are going to love it.

Data is stored in open parquet format, allowing its usage even outside of OpenObserve if so desired.

Hope this helps.

Yes, OTLP is supported. You can use standard Opentelemetry SDKs with no changes required.