[HN Gopher] Show HN: Coroot - eBPF-based, open source observabil...
       ___________________________________________________________________
        
       Show HN: Coroot - eBPF-based, open source observability with
       actionable insights
        
       A common open source approach to observability will begin with
       databases and visualizations for telemetry - Grafana, Prometheus,
       Jaeger. But observability doesn't begin and end here: these tools
       require configuration, dashboard customization, and may not
       actually pinpoint the data you need to mitigate system risks.
       Coroot was designed to solve the problem of manual, time-consuming
       observability analysis: it handles the full observability journey
       -- from collecting telemetry to turning it into actionable
       insights. We also strongly believe that simple observability should
       be an innovation everyone can benefit from: which is why our
       software is open source.  Features:  - Cost monitoring to track and
       minimise your cloud expenses (AWS, GCP, Azure.)  - SLO tracking
       with alerts to detect anomalies and compare them to your system's
       baseline behaviour.  - 1-click application profiling: see the exact
       line of code that caused an anomaly.  - Mapped timeframes (stop
       digging through Grafana to find when the incident occurred.)  -
       eBPF automatically gathers logs, metrics, traces, and profiles for
       you.  - Service map to grasp a complete at-a-glance picture of your
       system.  - Automatic discovery and monitoring of every application
       deployment in your kubernetes cluster.  We welcome any feedback and
       hope the tool can improve your workflow!
        
       Author : openWrangler
       Score  : 68 points
       Date   : 2025-04-08 16:49 UTC (6 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | Conasg wrote:
       | I took a cursory look and I like what I see - the service maps
       | are really good, I love the level of detail. I will say, one
       | thing I'm looking for with this kind of software, to maximise
       | value, is structured logging support, and from what I could see,
       | each log line just has the raw payload currently. Is that
       | something you have on your roadmap?
        
         | nikolay_sivko wrote:
         | 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
        
       | toobulkeh wrote:
       | We're on sentry today, but have been waiting for a fully OSS
       | solution like this.
        
         | nikolay_sivko wrote:
         | (I'm a co-founder). At Coroot, we're strong believers in open
         | source, especially when it comes to observability. Agents often
         | require significant privileges, and the cost of switching
         | solutions is high, so being open source is the only way to
         | provide real guarantees for businesses.
        
       | IOT_Apprentice wrote:
       | Can this also be used in a non-cloud environment? Or even say in
       | promox based setup locally?
        
         | nikolay_sivko wrote:
         | It only requires a modern Linux kernel. Note: The agent does
         | not support Docker-in-Docker environments, such as KinD or
         | Minikube (D-in-D plugin).
        
       | esafak wrote:
       | What's the data transformation story; for ML on metrics?
        
         | nikolay_sivko wrote:
         | Coroot builds a model of each system, allowing it to traverse
         | the dependency graph and identify correlations between metrics.
         | On top of that, we're experimenting with LLMs for summarization
         | -- here are a few examples:
         | https://oopsdb.coroot.com/failures/cpu-noisy-neighbor/
        
           | esafak wrote:
           | That looks like a built-in feature. I'm asking about
           | extensibility. How do we use custom metrics transformations
           | (libraries), for example?
        
             | nikolay_sivko wrote:
             | Currently, you can define custom SLIs (Service Level
             | Indicators, such as service latency or error rate) for each
             | service using PromQL queries. In the future, you'll be able
             | to define custom metrics for each application, including
             | explanations of their meaning, so they can be leveraged in
             | Root Cause Analysis
        
       | akdor1154 wrote:
       | I already have Opentelemetry traces and logs going to Clickhouse
       | with the Clickhouse otel exporter.
       | 
       | Can i use Coroot to show my existing data, without it taking
       | control of my DDL?
        
         | nikolay_sivko wrote:
         | Initially, we relied on the ClickHouse OTEL exporter and its
         | schema, but for performance optimization, we decided to modify
         | our ClickHouse schema, and they are no longer compatible :(
        
           | akdor1154 wrote:
           | Bummer, it'd be awesome if i could point it at data i already
           | have, even if that meant a reduced feature set.
        
       ___________________________________________________________________
       (page generated 2025-04-08 23:00 UTC)