<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Co-Sre on Netdata</title><link>https://www.netdata.cloud/tags/co-sre/</link><description>Recent content in Co-Sre on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 02 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/co-sre/index.xml" rel="self" type="application/rss+xml"/><item><title>Conversations: Ask Netdata About Anything You're Looking At</title><link>https://www.netdata.cloud/blog/converse-with-everything-in-netdata/</link><pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/converse-with-everything-in-netdata/</guid><description>&lt;p>Netdata AI can already troubleshoot your alerts and generate Insights reports. What it couldn&amp;rsquo;t do, until now, was have a back-and-forth conversation. You could get a one-shot analysis, but you couldn&amp;rsquo;t ask follow-up questions, pull in additional context, or go from a quick question to a full investigation without starting over.&lt;/p>
&lt;p>We&amp;rsquo;ve added a conversational layer to Netdata AI. You&amp;rsquo;ll notice a new blue chat icon throughout Netdata Cloud, on charts, in the alerts table, on Insights reports, and in the reports list. Click it, and you&amp;rsquo;re in a conversation where the thing you clicked on is already the context. No copy-pasting metric names, no explaining what you&amp;rsquo;re looking at.&lt;/p></description></item><item><title>Introducing Real-Time Conversations with Netdata AI</title><link>https://www.netdata.cloud/blog/ai-conversations/</link><pubDate>Tue, 23 Dec 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/ai-conversations/</guid><description>&lt;p>Over the past few months, we&amp;rsquo;ve seen incredible adoption of our AI Investigations and Insights reports. Teams are using them to automate the deep, thoughtful analysis required for complex post-mortems, capacity planning, and performance optimization. These comprehensive reports are fantastic when you need a well-researched, shareable document.&lt;/p>
&lt;p>But what about the moments &lt;em>during&lt;/em> an investigation? What about the rapid-fire &amp;ldquo;what if&amp;rdquo; questions and the quick exploration of hypotheses that happen in the heat of the moment? For that, you need speed and interactivity. You need a partner you can have a real-time dialogue with.&lt;/p></description></item><item><title>Text-To-Alert: Create Alerts From Natural Language</title><link>https://www.netdata.cloud/blog/ai-alerts/</link><pubDate>Thu, 18 Dec 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/ai-alerts/</guid><description>&lt;p>Netdata has an incredibly powerful alerting engine. But this can sometimes be a double-edged sword: the flexibility to build incredibly specific, intelligent alerts is immense, but mastering its syntax can feel like learning a new language. We’ve heard this from so many of you. You tell us that configuring alerts is often the steepest part of the learning curve, a task that falls to the one &amp;ldquo;Netdata expert&amp;rdquo; on the team who has spent the time digging through the documentation.&lt;/p></description></item><item><title>Automate Infrastructure Analysis With AI Reports</title><link>https://www.netdata.cloud/blog/scheduled-reports-insights-investigations/</link><pubDate>Tue, 23 Sep 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/scheduled-reports-insights-investigations/</guid><description>&lt;p>The least exciting part of an operations or SRE role is often the manual, repetitive task of generating reports. It’s the Monday morning scramble to summarize weekly infrastructure health for the team, or the end-of-quarter push to build a capacity planning document. This is boilerplate work that pulls you away from critical engineering tasks.&lt;/p>
&lt;p>We believe that if a process is repeatable, it should be automated.&lt;/p>
&lt;!--truncate-->
&lt;p>That&amp;rsquo;s why we’re introducing &lt;strong>Scheduled AI Investigations and Insights&lt;/strong>. This new capability builds directly on our existing AI tools, allowing you to set your most important analyses on a recurring schedule. It’s like setting up a cron job for your infrastructure reporting, letting your Co-SRE do the heavy lifting for you.&lt;/p></description></item><item><title>Save Hours on Troubleshooting with Automated Investigations</title><link>https://www.netdata.cloud/blog/automated-investigations/</link><pubDate>Mon, 04 Aug 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/automated-investigations/</guid><description>&lt;p>How many times has your team stared at a dashboard, pointed to a spike, and asked a question that charts alone can&amp;rsquo;t answer? &amp;ldquo;What was the real impact of that deployment?&amp;rdquo; &amp;ldquo;Why are our Kubernetes pods in the us-east-1 cluster suddenly crashing?&amp;rdquo; &amp;ldquo;Are we wasting money on overprovisioned servers?&amp;rdquo;&lt;/p>
&lt;!--truncate-->
&lt;p>Answering these questions is the real work of operations and SRE. It often kicks off a time-consuming scramble, sending engineers down rabbit holes for hours, days, or even weeks. You dig through logs, correlate metrics across services, and piece together clues from Slack conversations and Jira tickets.&lt;/p></description></item><item><title>Netdata Now Troubleshoots Your Alerts for You</title><link>https://www.netdata.cloud/blog/automated-alert-troubleshooting/</link><pubDate>Sun, 03 Aug 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/automated-alert-troubleshooting/</guid><description>&lt;p>The 2 AM pager alert. For anyone in Ops, SRE, or IT administration, those words trigger a familiar sense of dread. An alert has fired. Is it a real fire, or another false alarm waking you from a dead sleep? The pressure is on. Every minute of downtime costs money and reputation, but troubleshooting a complex system when you&amp;rsquo;re sleep-deprived is a Herculean task.&lt;/p>
&lt;!--truncate-->
&lt;p>This cycle is a massive drain on engineering resources. The daily grind of sifting through alerts, trying to distinguish signal from noise, and manually correlating metrics to find a root cause consumes countless hours. This constant firefighting leads to alert fatigue, where even critical notifications start to get ignored. The core questions are always the same: Is this a real problem? What is the potential impact? Why did this trigger? What do I do next? Answering them is a slow, manual, and often stressful process.&lt;/p></description></item></channel></rss>