<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Crashes on Netdata</title><link>https://www.netdata.cloud/tags/crashes/</link><description>Recent content in Crashes on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 17 Jul 2026 17:33:53 +0300</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/crashes/index.xml" rel="self" type="application/rss+xml"/><item><title>Monitoring Netdata Restarts: A Reliable Solution</title><link>https://www.netdata.cloud/blog/2025-03-06-monitoring-netdata-restarts/</link><pubDate>Thu, 06 Mar 2025 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/2025-03-06-monitoring-netdata-restarts/</guid><description>&lt;p>For a tool like Netdata, monitoring crashes and abnormal events extends far beyond bug fixing—it&amp;rsquo;s essential for identifying edge cases, preventing regressions, and delivering the most dependable observability experience possible. With millions of daily downloads, each event provides a vital signal for maintaining the integrity of our systems.&lt;/p>
&lt;h2 id="the-challenge-with-traditional-solutions">The Challenge with Traditional Solutions&lt;/h2>
&lt;p>Over the years, we&amp;rsquo;ve evaluated many monitoring tools, each with significant limitations:&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Tool&lt;/th>
 &lt;th>Strengths&lt;/th>
 &lt;th>Limitations&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>&lt;strong>Sentry&lt;/strong>&lt;/td>
 &lt;td>• Comprehensive error tracking features&lt;br/>• Detailed stack traces&lt;/td>
 &lt;td>• Per-event pricing model becomes prohibitive at scale&lt;br/>• Forces sampling which reduces visibility into critical issues&lt;br/>• Compromises complete error capture for cost control&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>&lt;a href="https://www.netdata.cloud/solutions/technologies/gcp-monitoring/">GCP&lt;/a> BigQuery &amp;amp; Similar&lt;/strong>&lt;/td>
 &lt;td>• Powerful query capabilities&lt;br/>• Flexible data processing&lt;br/>• High scalability potential&lt;/td>
 &lt;td>• Complex reporting setup and maintenance&lt;br/>• Significant costs at high event volumes&lt;br/>• Requires specialized technical expertise&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Other Solutions&lt;/strong>&lt;/td>
 &lt;td>• Various specialized features&lt;br/>• Some open-source flexibility&lt;/td>
 &lt;td>• Either too inflexible for custom requirements&lt;br/>• Or prohibitively expensive at full-capture scale&lt;br/>• Often require compromising between detail and cost&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>We consistently encountered these core challenges:&lt;/p></description></item><item><title>How to monitor node reboots?</title><link>https://www.netdata.cloud/blog/monitoring-node-reboots/</link><pubDate>Thu, 17 Nov 2022 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/monitoring-node-reboots/</guid><description>&lt;p>Monitoring the health and status of nodes and servers is a critical part of effective infrastructure monitoring.&lt;/p>
&lt;p>&lt;img src="https://user-images.githubusercontent.com/96257330/202475049-22838a0b-73b1-485b-8416-5fd49d6ccb53.png" alt="logo">&lt;/p>
&lt;!--truncate-->
&lt;h2 id="how-to-monitor-node-reboots">How to monitor node reboots?&lt;/h2>
&lt;p>One of the most critical tasks of monitoring an infrastructure is to check the health of its servers/nodes. In most cases, this results in setting up a &amp;ldquo;Hardware manager&amp;rdquo; from the hardware vendor delivering these servers or setting up an SNMP (or similar) agent to continuously monitor the availability of the server and report when there is a reboot / failure.&lt;/p></description></item></channel></rss>