Sign up to save your podcasts
Or
Share Interview with Nikolay Sivko, Founder & CEO at Coroot
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Interview with Nikolay Sivko, Founder & CEO at Coroot
This time I sat down with Nikolay Sivko, the Founder and CEO at Coroot, and here are some of the topics we discussed:
* The sparkEvery product begins with a pain point—what was the “aha moment” that made Coroot necessary?
* The landscapeWhen looking at the broad observability market, what’s the biggest advantage Coroot brings compared to existing solutions?
* The profiling edgeMetrics, logs, traces, and continuous profiling all ship out of the box. Where has profiling made the biggest difference in practice?
* Zero-code instrumentationCoroot promises instrumentation without code changes for every language on Kubernetes. Which runtime—Java, Go, Rust, etc.—caused the trickiest edge cases, and how were they solved?
* Taming the firehoseCollecting “everything” is easy—handling it without blowing up the system is the real challenge. How do you decide which telemetry data is important and which not?
* The eBPF observer effectWhat about CPU and memory overhead—how do you guard against the tooling itself impacting the workload?
* 80/20 troubleshootingHow did you arrive at the idea that 80% of issues follow common patterns, and the remaining 20% can be uncovered by linking logs with other system data?
* AI insightsCoroot uses AI to surface actionable insights. How do you avoid false positives and measure the success rate of those explanations?
* From telemetry to root causeHow do you actually map raw telemetry to a possible root cause—is this a huge state machine, pattern matching, or something else under the hood?
* The future of observabilityWill we see a shift from passive runtime visibility to autonomous systems that not only detect but also act on issues, powered by eBPF-fed AI models? The fear, of course, is false positives—how do you see that playing out?
* Community energyYour GitHub repo has passed 6,000 stars in a short time. What have you learned about building—and sustaining—an engaged open-source community?
🐝 I’ll leave it there—hope you enjoy the conversation.
Get full access to eBPFChirp at ebpfchirp.substack.com/subscribe
View all episodes
By Teodor J. PodobnikThis time I sat down with Nikolay Sivko, the Founder and CEO at Coroot, and here are some of the topics we discussed:
* The sparkEvery product begins with a pain point—what was the “aha moment” that made Coroot necessary?
* The landscapeWhen looking at the broad observability market, what’s the biggest advantage Coroot brings compared to existing solutions?
* The profiling edgeMetrics, logs, traces, and continuous profiling all ship out of the box. Where has profiling made the biggest difference in practice?
* Zero-code instrumentationCoroot promises instrumentation without code changes for every language on Kubernetes. Which runtime—Java, Go, Rust, etc.—caused the trickiest edge cases, and how were they solved?
* Taming the firehoseCollecting “everything” is easy—handling it without blowing up the system is the real challenge. How do you decide which telemetry data is important and which not?
* The eBPF observer effectWhat about CPU and memory overhead—how do you guard against the tooling itself impacting the workload?
* 80/20 troubleshootingHow did you arrive at the idea that 80% of issues follow common patterns, and the remaining 20% can be uncovered by linking logs with other system data?
* AI insightsCoroot uses AI to surface actionable insights. How do you avoid false positives and measure the success rate of those explanations?
* From telemetry to root causeHow do you actually map raw telemetry to a possible root cause—is this a huge state machine, pattern matching, or something else under the hood?
* The future of observabilityWill we see a shift from passive runtime visibility to autonomous systems that not only detect but also act on issues, powered by eBPF-fed AI models? The fear, of course, is false positives—how do you see that playing out?
* Community energyYour GitHub repo has passed 6,000 stars in a short time. What have you learned about building—and sustaining—an engaged open-source community?
🐝 I’ll leave it there—hope you enjoy the conversation.
Get full access to eBPFChirp at ebpfchirp.substack.com/subscribe