Viewing profile — prabhatsharma

You should take a look at https://github.com/openobserve/openobserve - Extremely performant and simple full-stack observability solution.

OpenObserve would be the simplest and most performant

>The real scaling question is how many active timeseries the system can handle handle? What does it mean? Be able to ingest data? Be able to query? ingest data - Using kafka helps …

>There are no other open-source solutions offering the same scalability, period. I love it when people take a hard stand like this, using the words "period" BTW, Cortex is used as …

Check OpenObserve https://github.com/openobserve/openobserve . It precisely was built to solve the challenges around grafana nd elastic. This is not a stack that you will need to w…

OpenObserve has logs, metrics, traces, dashboards, RUM and alerts

Kide is fast and lightweight Kubernetes IDE built in Rust/Tauri + VueJS. We built it as there were not really good IDEs for Kubernetes that were light. Lens was too heavy with it's…

We moved from plotly to eCharts at OpenObserve, having faced too many small things that we had to fight with plotly. Haven't looked back since the migration.

OpenObserve offers free SSO on our cloud service to anyone and Free SSO for anyone using enterprise version if they ingest under 200 GB/Day (6 TB/Month). This should cover all comp…

For one thing - From their website - Our powerful ingestion engine has a proven track record of handling 10TB+ data ingestion per day. OpenObserve clusters can ingest PBs of data e…

In all likelihood you are not going to get convinced by that. You did not switch to using LGTM stack because grafana gave you a benchmark of LGTM against what you were using previo…

Thanks @yourapostasy . Agree with you for the most part. Not all managers are averse to paying, but many are. I have had discussions with Director/Sr. Director and VP level folks i…

You are in the same danger with Grafana (Front end, Elasic/Redis fate and lock in) as you are with OpenObserve. No difference there.

Too much to give all details in an HN thread. To simplify the conversation, Data will be persisted and usable for individual searches and aggregations. I would welcome you to our s…

By all means, if LGTM works for you stay with it. For those looking at much more simplicity, and much higher performance OpenObserve is the way to go. Many folks have moved from Lo…

We will publish many names on our website soon.

Compute power is required to process and store the incoming data. It's not "only 28 MB/Sec/Core". Try doing same with Splunk/Elasticsearch - You won't go past 5 MB/Sec/Core (Typica…

Machines I would use for benchmarking would go down after some time and won't be active.

God bless you my friend. Thanks for the comment.

I do understand it's super important for security, and I want large companies who have ample money and spend a lot on security to pay me as well for it. If you are running OpenObse…

By using object storage (Think s3 and similar) and not replicating data for HA (Not needed if using s3) which is done by legacy systems like Elasticsearch and Splunk.

You should read - https://openobserve.ai/blog/sso-tax and https://openobserve.ai/blog/openobserve-vs-grafana

Most people who talk about SSO Tax don't really care for it's values but rather want free stuff. I have had conversations with multi-billion dollar companies who would avoid paying…