In addition to raw logs, Coroot can extract recurring patterns to generate log-based metrics [1].

We also plan to convert structured logs into OpenTelemetry attributes [2].

[1] https://demo.coroot.com/p/tbuzvelk/applications/default:Depl... [2] https://github.com/coroot/coroot/issues/490

Take a look at Coroot: https://github.com/coroot/coroot. It supports OpenTelemetry and stores traces in ClickHouse.

Here you can find a demo of the Distributed Tracing UI: https://demo.coroot.com/p/tbuzvelk/traces

Disclaimer: I'm a co-founder

Thanks. Will check it out

Sure, but the scope is quite broad. For example, we might need to explain logs from a relatively rare app or framework. In such cases, a large model could unintentionally have knowledge of it.

Disclaimer: I'm the author of the post

Give https://github.com/coroot/coroot a try for full visibility in minutes with eBPF

disclaimer: I'm a co-founder

Take a look at Coroot [0], which stores logs in ClickHouse with configurable TTL. Its agent can discover container logs and extract repeated patterns from logs [1].

[0] https://github.com/coroot/coroot

[1] demo: https://community-demo.coroot.com/p/qcih204s/app/default:Dep...

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

Disclaimer: I'm a co-founder of Coroot. We're currently benchmarking our eBPF-based agent to measure its performance impact.

Could you please elaborate on a few more details about your benchmark?

- Did you measure the CPU usage of the eBPF agent?

- How does Odigos handle eBPF's perfmap overflow, and did you measure any lost events between the kernel and the agent?

Coroot leverages eBPF to collect metrics and traces, and its agent parses container logs to extract recurring patterns from them.

Here is the list of collected metrics with detailed descriptions: https://coroot.com/docs/metric-exporters/node-agent/metrics

Nik and Anton here - we're building an open-source observability tool that transforms telemetry data into actionable insights. While there are many excellent observability tools on the market, pinpointing the root cause of an incident often requires manual searching through a sea of metrics, logs, and traces.

Coroot acts as a virtual assistant, conducting system audits just like an experienced engineer would:

- It utilizes telemetry data collected through eBPF to construct a model of the distributed system and understand its topology.

- It traverses the dependency graph and audits every relevant service to identify the root cause.

Our journey has been long, but we've made great strides in learning how to build better models of distributed systems, and improving our agents to gather the right metrics. Coroot is an open-source product (Apache 2.0), so you can self-host it for free. We charge for a cloud version with AI-based Root Cause Analysis, RBAC, and premium support.

Take a look at Coroot: it's open-source, ebpf-powered, and can be integrated in minutes: https://github.com/coroot/coroot