<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: openWrangler</title><link>https://news.ycombinator.com/user?id=openWrangler</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 23 Apr 2026 12:54:22 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=openWrangler" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[Memory stall: agony before OOM]]></title><description><![CDATA[
<p>Article URL: <a href="https://coroot.com/blog/memory-stall-the-agony-before-oom/">https://coroot.com/blog/memory-stall-the-agony-before-oom/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=45351149">https://news.ycombinator.com/item?id=45351149</a></p>
<p>Points: 4</p>
<p># Comments: 1</p>
]]></description><pubDate>Tue, 23 Sep 2025 18:45:32 +0000</pubDate><link>https://coroot.com/blog/memory-stall-the-agony-before-oom/</link><dc:creator>openWrangler</dc:creator><comments>https://news.ycombinator.com/item?id=45351149</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45351149</guid></item><item><title><![CDATA[Instrumenting the Node.js event loop with eBPF]]></title><description><![CDATA[
<p>Article URL: <a href="https://coroot.com/blog/instrumenting-the-node-js-event-loop-with-ebpf/">https://coroot.com/blog/instrumenting-the-node-js-event-loop-with-ebpf/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=45302945">https://news.ycombinator.com/item?id=45302945</a></p>
<p>Points: 4</p>
<p># Comments: 0</p>
]]></description><pubDate>Fri, 19 Sep 2025 15:47:43 +0000</pubDate><link>https://coroot.com/blog/instrumenting-the-node-js-event-loop-with-ebpf/</link><dc:creator>openWrangler</dc:creator><comments>https://news.ycombinator.com/item?id=45302945</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45302945</guid></item><item><title><![CDATA[AI-Powered Root Cause Analysis – Limited Free Use]]></title><description><![CDATA[
<p>Article URL: <a href="https://github.com/coroot/coroot/releases/tag/v1.14.0">https://github.com/coroot/coroot/releases/tag/v1.14.0</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=45041070">https://news.ycombinator.com/item?id=45041070</a></p>
<p>Points: 5</p>
<p># Comments: 0</p>
]]></description><pubDate>Wed, 27 Aug 2025 15:31:03 +0000</pubDate><link>https://github.com/coroot/coroot/releases/tag/v1.14.0</link><dc:creator>openWrangler</dc:creator><comments>https://news.ycombinator.com/item?id=45041070</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=45041070</guid></item><item><title><![CDATA[Show HN: Coroot – AI powered Root Cause Analysis using eBPF-based telemetry]]></title><description><![CDATA[
<p>Hey HN,<p>We launched Coroot a while ago as an open source observability tool that collects complete telemetry using eBPF. Today we are adding a major new capability:<p>Coroot enterprise now includes AI-powered Root Cause Analysis.<p>When an incident happens (like an SLO violation), Coroot:<p>- Automatically kicks off an RCA<p>- Summarizes what went wrong in plain English<p>- Suggests immediate fixes<p>- Shows the full investigation using metrics, logs, traces, and profiles<p>With most tools, the quality of root cause analysis depends on how well the system is instrumented. Coroot takes a different approach: it uses eBPF to collect all the critical signals automatically, even from uninstrumented or third party services. That gives the AI a much more complete picture to work with.<p>We are keeping it simple and accessible at $1 per monitored CPU core per month. Our core tool is also completely open source at: <a href="https://github.com/coroot/coroot">https://github.com/coroot/coroot</a><p>You can try it for free or view a demo with the link connected to this thread. We'd love to hear your thoughts!</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44745813">https://news.ycombinator.com/item?id=44745813</a></p>
<p>Points: 8</p>
<p># Comments: 0</p>
]]></description><pubDate>Thu, 31 Jul 2025 14:08:01 +0000</pubDate><link>https://coroot.ai/</link><dc:creator>openWrangler</dc:creator><comments>https://news.ycombinator.com/item?id=44745813</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44745813</guid></item><item><title><![CDATA[Evaluating the different types of AI-powered Root Cause Analysis]]></title><description><![CDATA[
<p>Article URL: <a href="https://coroot.com/blog/anatomy-of-ai-powered-root-cause-analysis/">https://coroot.com/blog/anatomy-of-ai-powered-root-cause-analysis/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44670803">https://news.ycombinator.com/item?id=44670803</a></p>
<p>Points: 3</p>
<p># Comments: 0</p>
]]></description><pubDate>Thu, 24 Jul 2025 14:01:31 +0000</pubDate><link>https://coroot.com/blog/anatomy-of-ai-powered-root-cause-analysis/</link><dc:creator>openWrangler</dc:creator><comments>https://news.ycombinator.com/item?id=44670803</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44670803</guid></item><item><title><![CDATA[Instrumenting Python GIL with eBPF]]></title><description><![CDATA[
<p>Article URL: <a href="https://coroot.com/blog/engineering/instrumenting-python-gil-with-ebpf/">https://coroot.com/blog/engineering/instrumenting-python-gil-with-ebpf/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44571890">https://news.ycombinator.com/item?id=44571890</a></p>
<p>Points: 5</p>
<p># Comments: 0</p>
]]></description><pubDate>Tue, 15 Jul 2025 15:04:39 +0000</pubDate><link>https://coroot.com/blog/engineering/instrumenting-python-gil-with-ebpf/</link><dc:creator>openWrangler</dc:creator><comments>https://news.ycombinator.com/item?id=44571890</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44571890</guid></item><item><title><![CDATA[OpenTelemetry for Go: Measuring overhead costs]]></title><description><![CDATA[
<p>Article URL: <a href="https://coroot.com/blog/opentelemetry-for-go-measuring-the-overhead/">https://coroot.com/blog/opentelemetry-for-go-measuring-the-overhead/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44290331">https://news.ycombinator.com/item?id=44290331</a></p>
<p>Points: 129</p>
<p># Comments: 48</p>
]]></description><pubDate>Mon, 16 Jun 2025 15:09:17 +0000</pubDate><link>https://coroot.com/blog/opentelemetry-for-go-measuring-the-overhead/</link><dc:creator>openWrangler</dc:creator><comments>https://news.ycombinator.com/item?id=44290331</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44290331</guid></item><item><title><![CDATA[New comment by openWrangler in "Graceful Shutdown in Go: Practical Patterns"]]></title><description><![CDATA[
<p>It's not just you - OSS toolstacks can be sprawling and involve long manual processes while costs from most enterprise vendors are too steep for fully mapped observability.<p>Coroot is an open source project I'm working with to try and to tackle this. eBPF automatically gathers your data into a centralized service map, and then the tool provides RCA insights (with things like mapped incident timeframes) to help implement fixes quicker and improve uptime.<p>GitHub here and we'd love any feedback if you think it can help: <a href="https://github.com/coroot/coroot">https://github.com/coroot/coroot</a></p>
]]></description><pubDate>Tue, 06 May 2025 19:12:14 +0000</pubDate><link>https://news.ycombinator.com/item?id=43908605</link><dc:creator>openWrangler</dc:creator><comments>https://news.ycombinator.com/item?id=43908605</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43908605</guid></item><item><title><![CDATA[New comment by openWrangler in "Observability 2.0 and the Database for It"]]></title><description><![CDATA[
<p>I'm currently working with Coroot, which is an open source project trying to create a solution for this issue of logs and other telemetry sources being too much for any team to reasonably have time to parse manually. Data is automatically imported using eBPF and Coroot will provide insights into RCA (with things like mapped incident timeframes) to help with anything overlooked in dumps.<p>GitHub here - hope the tool can help some folks in this thread: <a href="https://github.com/coroot/coroot">https://github.com/coroot/coroot</a></p>
]]></description><pubDate>Tue, 29 Apr 2025 04:18:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=43828648</link><dc:creator>openWrangler</dc:creator><comments>https://news.ycombinator.com/item?id=43828648</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43828648</guid></item><item><title><![CDATA[New comment by openWrangler in "Vector Search Conference 2025"]]></title><description><![CDATA[
<p>The Vector Search Conference is an online event on June 6 I thought could be helpful for developers, data engineers, and AI enthusiasts on HN to connect with other members of the vector search community. It’s a free opportunity to connect and learn from other professionals in your field if you’re interested in building RAG apps or scaling recommendation systems.<p>Event features:<p>- Experts from Google, Microsoft, Oracle, Qdrant, Manticore Search, Weaviate sharing real-world applications, best practices, and future directions in high-performance search and retrieval systems<p>- Presentations for all skill levels<p>- Live Q&A to engage with industry leaders and virtual networking<p>A few of the presenting speakers:<p>- Gunjan Joyal (Google): “Indexing and Searching at Scale with PostgreSQL and pgvector – from Prototype to Production”<p>- Maxim Sainikov (Microsoft): “Advanced Techniques in Retrieval-Augmented Generation with Azure AI Search”<p>- Ridha Chabad (Oracle): “LLMs and Vector Search unified in one Database: MySQL HeatWave's Approach to Intelligent Data Discovery”<p>If you can’t make it but want to learn from experience shared in one of these talks, sessions will also be recorded. Free registration can be checked out at (<a href="https://vsearchcon.com/register/" rel="nofollow">https://vsearchcon.com/register/</a>) - hope you learn something from the event!</p>
]]></description><pubDate>Mon, 28 Apr 2025 14:37:50 +0000</pubDate><link>https://news.ycombinator.com/item?id=43821991</link><dc:creator>openWrangler</dc:creator><comments>https://news.ycombinator.com/item?id=43821991</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43821991</guid></item><item><title><![CDATA[Vector Search Conference 2025]]></title><description><![CDATA[
<p>Article URL: <a href="https://vsearchcon.com/">https://vsearchcon.com/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=43821990">https://news.ycombinator.com/item?id=43821990</a></p>
<p>Points: 1</p>
<p># Comments: 1</p>
]]></description><pubDate>Mon, 28 Apr 2025 14:37:50 +0000</pubDate><link>https://vsearchcon.com/</link><dc:creator>openWrangler</dc:creator><comments>https://news.ycombinator.com/item?id=43821990</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43821990</guid></item><item><title><![CDATA[New comment by openWrangler in "Show HN: Nerdlog – Fast, multi-host TUI log viewer with timeline histogram"]]></title><description><![CDATA[
<p>Seconded - it sounds like compatibility isn't there yet with AWS, but it would be great if there was a way to use nerdlog with other OSS dashboard tools like Signoz or Coroot like you mentioned. Still a really interesting graylog altnerative.</p>
]]></description><pubDate>Mon, 21 Apr 2025 16:18:14 +0000</pubDate><link>https://news.ycombinator.com/item?id=43753661</link><dc:creator>openWrangler</dc:creator><comments>https://news.ycombinator.com/item?id=43753661</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43753661</guid></item><item><title><![CDATA[Show HN: Coroot – eBPF-based, open source observability with actionable insights]]></title><description><![CDATA[
<p>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.<p>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.<p>Features:<p>- Cost monitoring to track and minimise your cloud expenses (AWS, GCP, Azure.)<p>- SLO tracking with alerts to detect anomalies and compare them to your system’s baseline behaviour.<p>- 1-click application profiling: see the exact line of code that caused an anomaly.<p>- Mapped timeframes (stop digging through Grafana to find when the incident occurred.)<p>- eBPF automatically gathers logs, metrics, traces, and profiles for you.<p>- Service map to grasp a complete at-a-glance picture of your system.<p>- Automatic discovery and monitoring of every application deployment in your kubernetes cluster.<p>We welcome any feedback and hope the tool can improve your workflow!</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=43623820">https://news.ycombinator.com/item?id=43623820</a></p>
<p>Points: 162</p>
<p># Comments: 31</p>
]]></description><pubDate>Tue, 08 Apr 2025 16:49:40 +0000</pubDate><link>https://github.com/coroot/coroot</link><dc:creator>openWrangler</dc:creator><comments>https://news.ycombinator.com/item?id=43623820</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43623820</guid></item></channel></rss>