prabhatsharma

9 ms·

1. 61.▲
   by prabhatsharma 3y ago

   Check https://openobserve.ai . It already has logs, metrics and traces and there is more on the horizon.
2. 62.▲
   by prabhatsharma 3y ago

   I think this is a great tool. Not discounting the value of work (which you started long ago) that you have done already, but I am thinking that an LLM could do it much more easily today.
3. 63.▲
   by prabhatsharma 3y ago

   No metrics and logs with OTLP yet. Only traces for now. Will have it soon for logs and metrics too.
4. 64.▲
   by prabhatsharma 3y ago

   qryn, signoz and highlight are all built on top of clickhouse. I think they all have done a good job of leveraging clickhouse instead of building something from the ground up. That is a super smart thing. We think that managing clickhouse i
5. 65.▲
   by prabhatsharma 3y ago

   Easiest way to interact with the team is to follow the github project (add to your watch) and join the slack community.
6. 66.▲
   by prabhatsharma 3y ago

   used material for mkdocs - https://github.com/squidfunk/mkdocs-material . Its pretty neat.
7. 67.▲
   by prabhatsharma 3y ago

   What is your environment? local laptop, linux VM, kubernetes cluster, ... ? You don't use curl for logging except in demonstrations. In production you would want to use a log forwarder like vector or fluentbit. If your environment is k
8. 68.▲
   by prabhatsharma 3y ago

   Got your point. We think that there are 3 really good agents out there that can be leveraged by anyone to capture and send telemetry data. These are Vector, fluentbit and Otel-collector. Between these 3 they can handle pretty much anything.
9. 69.▲
   by prabhatsharma 3y ago

   Loki solves the problem of high cardinality by saying - "don't have high cardinality". OpenObserve use parquet as the storage format which is much more resilient to high cardinality. OpenObserve has page indexes and partition
10. 70.▲
    by prabhatsharma 3y ago

    You could also try the cloud version of OpenObserve without setting it up yourself.
11. 71.▲
    by prabhatsharma 3y ago

    Not yet. Will have it in some time.
12. 72.▲
    by prabhatsharma 3y ago

    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
13. 73.▲
    by prabhatsharma 3y ago

    Logs, metrics and traces are all queryable using SQL. Metrics can additionally use PromQL for querying.
14. 74.▲
    by prabhatsharma 3y ago

    We haven't compared resource usage against grafana stack. Rust is a lot more efficient than Go in general though.
15. 75.▲
    by prabhatsharma 3y ago

    Yes, you could use it. If you face any issues, let us know through github issues or on slack.
16. 76.▲
    by prabhatsharma 3y ago

    Thanks for pointing out. fixed.
17. 77.▲
    by prabhatsharma 3y ago

    We have done minimal performance testing for now. A lot of work is remaining in this area.
18. 78.▲
    by prabhatsharma 3y ago

    Thanks for pointing out. Fixed it.
19. 79.▲
    by prabhatsharma 3y ago

    Here you go - https://github.com/openobserve/openobserve/blob/main/CONTRIB...
20. 80.▲
    by prabhatsharma 3y ago

    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
21. 81.▲
    by prabhatsharma 3y ago

    You are right.
22. 82.▲
    by prabhatsharma 3y ago

    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
23. 83.▲
    by prabhatsharma 3y ago

    Glad you liked it. Yeah, resource usage is so low that some folks are running it in their homelab even on a raspberry-pi.
24. 84.▲
    by prabhatsharma 3y ago

    >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.
25. 85.▲
    by prabhatsharma 3y ago

    Yeah, Reddit is filled with horror stories from Datadog. One thread here - https://www.reddit.com/r/devops/comments/zz4naq/datadog_i_do...
26. 86.▲
    by prabhatsharma 3y ago

    Check the docs - https://openobserve.ai/docs/ingestion/traces/opentelemetry/
27. 87.▲
    by prabhatsharma 3y ago

    Logs, Metrics and traces are all queryable.
28. 88.▲
    by prabhatsharma 3y ago

    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 ba
29. 89.▲
    by prabhatsharma 3y ago

    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.
30. 90.▲
    by prabhatsharma 3y ago

    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.