prabhatsharma

Which websites does it search for jobs? LinkedIn or also specific websites of companies?

Do you support subqueries and joins?

Agree

Author of the pr gave stuff for free. He showed no signs of entitlement. But he is not there only one who gave stuff for free. The open source project gave code for free that is 100 times bigger than the pr. Not acknowledging that is a problem.

98 to 99 percent of the contributions in all open core projects come from core contributors. You take the core team out and you will see the project die.

They need to be able to differentiate core from Enterprise. If they can't make money in a sustainable way the open core company will die and so will the open source project. Those who fail to see this reality are only hurting themselves.

This is perfectly fine.

eCharts is awesome. We moved from plotly after using it for several months to echarts at https://github.com/openobserve/openobserve and are super happy.

Short answer - no. You don't have to if you are sending logs data.

Long descriptive answer. It depends on, if your software is a covered work.

You are building a software that uses an AGPL software by calling its APIs : Your software is a covered work and you need to license it under AGPL and make the source code available to your users. A concrete example would be a monitoring software that calls OpenObserve APIs to provide its core functionality.

You are building a software and use a software licensed under AGPL to monitor your application: Your software is not a covered work and you can license it under any license you want. A concrete example would be - you using OpenObserve to monitor your closed source e-commerce application.

Github actions works great Even AWS codebuild is good.

I got a captcha from azure. Took me 15 minutes to solve it

So it requires redis. Would have loved if it was just a simple script or binary.

Google Jamboard is winding down

Google Jamboard will no longer be available after December 31, 2024 across Web, iOS, Android, and Google Meet devices. Your Jam data will be available for you to export or migrate to one of our whiteboard partners, like FigJam, Lucidspark, and Miro, until that date.

Another one killed by google.

Why build in this age when too many open source solutions backed by opentelemetry standard are available. Use fluentbit/vector/otel-collector to capture data and send to some open source solution.

It's like Splunk got saved by Cisco. While they were still growing but too many new age players coming up.

A good one. A lot is being built on top of clickhouse. I can count at least 3 if not more (hyperdx, signoz and highlight) built on top of clickhouse now.

We at OpenObserve are solving the same problem but a bit differently. A much simpler solution that anyone can run using a single binary on their own laptop or in a cluster of hundreds of nodes backed by s3. Covers logs, metrics, traces, Session replay, RUM and error tracking are being released by end of the month) - https://github.com/openobserve/openobserve

I am really curious, why build another project that has similar features as another open source software pixie - https://px.dev/.

How is it different than pixie?

Does it collect traces from compiled as well as scripted languages?

Getting rid of electron was the best thing.

this looks awesome. when is LLaMA 2 70B coming?

Outside of YC you have OpenObserve - https://news.ycombinator.com/item?id=36280028

Check https://openobserve.ai . It already has logs, metrics and traces and there is more on the horizon.

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.

No metrics and logs with OTLP yet. Only traces for now. Will have it soon for logs and metrics too.

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 is extra effort. Direct access to object storage is vital for cost reduction which is somewhat difficult in clickhouse. Small resource footprint is extremely valuable to many too. Simplicity of deployment is key to get started and many will use a product simply because they can. I know, I have used products that simply ran, and for no other reason.

Our best wishes to all the 3 teams.

Easiest way to interact with the team is to follow the github project (add to your watch) and join the slack community.

used material for mkdocs - https://github.com/squidfunk/mkdocs-material . Its pretty neat.

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 kubernetes, then use this guide - https://openobserve.ai/blog/how-to-send-kubernetes-logs-usin... .

If something else let us know, and we can have a guide. fluentbit and vector are fairly well documented and have been there for years now. I would recommend you to check them out. OTEL-collector is a good option too.

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. If there is something that needs to be handled that these cannot handle then its easy enough to build plugins for fluentbit and otel-collector.

We did not want to reinvent the wheel and recommend that you use one of these.

quickstart tutorial does not reflect what you will do in real life scenario.

You will want to learn how to use log forwarders like fluentbit and vector. These are the ones that you will generally use in real life. These log forwarders read the log files and send them to OpenObserve. Here is a blog on how to use fluentbit to capture kubernetes logs using fluentbit and send them to OpenObserve - https://openobserve.ai/blog/how-to-send-kubernetes-logs-usin...

We will add more tutorials and examples soon.

Hope this helps.

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 partitions that allow it to handle this very well.