coroot VS community

I'm Peter Zaitsev, co-founder at Coroot. I come from the database world where observability, or monitoring, was crucial for keeping databases running smoothly. But as technology evolves, so do the challenges we face.

Today, many applications are built using microservices architecture, making it harder to pinpoint issues. Developers now have more ownership over the entire environment, but they lack the expertise to navigate intricate infrastructure details. And with the complexity of modern observability systems, crucial components often go unmonitored, leaving blind spots.

That's where Coroot comes in!

We're excited to announce the release of Coroot 1.0 – a simplified observability platform designed to provide actionable insights for modern environments. With Coroot you get:

- Comprehensive Visibility: Coroot covers your entire environment, ensuring no information gaps. Whether you're on Kubernetes, traditional VMs, or cloud services, Coroot has you covered.

- Simple Deployment: We've made deploying Coroot a breeze. Leveraging modern Linux features like eBPF and Netlink, setup requires zero configuration. Coroot also identifies and configures additional components for you.

- Actionable Insights: Coroot prioritizes the most important information, helping you resolve issues up to 80% faster than with legacy solutions.

And the best part? Coroot has open-source version. If you prefer a hosted solution, there is Coroot Cloud, which comes with a free trial and transparent affordable pricing.

While Coroot is already an awesome open-source observability platform, we're not stopping there. We have ambitious plans to automate issue resolution and minimize human intervention.

Got ideas? Let us know on GitHub - https://github.com/coroot/coroot

See detailed overview of Coroot Features - https://coroot.com/overview

Take a look at https://github.com/coroot/coroot (Apache 2.0). It offers plenty of ready-to-use dashboards and inspections

I think ClickHouse is becoming a default storage for observability nowdays: https://clickhouse.com/use-cases/logging-and-metrics

And there are quite a few solutions on top of it.

A couple of examples that seem to be interesting (however I didn't use them in real life):

https://coroot.com/

Landing page: https://coroot.com

otel is working on their events spec https://github.com/open-telemetry/community/issues/1688

1. Agreed. It's the sink and the house attached to it, and the docs are thin and confusing as a result.

2. I had a similar experience to you. I wanted to implement a simple heartbeat in our app to get an idea of usage numbers. This is surprisingly not possible, which greatly confuses me given the name of the project. The low engagement on my question put me off and I abandoned my OpenTelemetry planning completely. [1][2]

[1] https://github.com/open-telemetry/community/discussions/1598

One of the OpenTelemetry Project's many Special Interest Groups (SIG) is the OpenTelemetry Community Demo SIG which gives support to a set of instrumented backend microservices and a web frontend app that are primarily used to showcase how to instrument a distributed system using OpenTelemetry. The application's main focus is to demonstrate the implementation process to instrument an application no matter what programming language, platform, or operating system your team is using, as well as providing different approaching techniques (automatic and manual instrumentation, metrics, baggage). All of this while following the standards and conventions defined by the official OpenTelemetry Documentation. More about the specific requirements can be found here. At Tracetest, we have always focused on becoming part of and embracing the OpenTelemetry community. One of our goals this summer was to get more involved with a core OpenTelemetry project where we could provide a meaningful contribution. The OTel demo became the best match for achieving that goal as it would not only help the community, but we at Tracetest needed a good example to test and showcase what can be done with our tool. During the version 0.7 project cycle, we created two specific tickets to get us closer to the community and start looking for things to pick up: