Netdata 장애 기록

1. 2026년 10월 23일 오후 12:34 UTCinvestigating

   Netdata Agent의 취약점은 공개적으로 공개되었습니다. 로컬 웹 포트 (19999) 또는 Netdata Cloud 공간에 액세스하는 공격자는 'netdata' 사용자로 임의 명령을 실행할 수 있습니다. 취약점의 전체 세부 사항은 여기 해시: https://codeberg.org/x509dot/vulns/src/branch/main/netdata-rce.md. 우리는 문제를 해결하고 에이전트의 새로운 야간 / 가장자리 빌드 (https://github.com/netdata/netdata-nightlies/releases/tag/v2.12.0-267-nightly) 및 새로운 패치 릴리스 v2.12.2 우리의 안정적인 채널에 대한 짧은 게시해야합니다. 우리는이 사건을 업데이트합니다. Mitigation: 에이전트의 웹 포트에 액세스 제한은이 취약점을 악용하기 위해 공격자의 가능성을 낮춘다. 에이전트에 대한 지침은 여기에 찾을 수 있습니다. https://learn.netdata.cloud/docs/netdata-agent/configuration/securing-agents, 로컬 호스트에 포트를 바인딩하고, 베어 토큰을 필요로하거나, 웹 포트를 완전히 비활성화하여 서버 접근 방식을 통해. 부모 에이전트, 그러나, 그들의 웹 포트는 스트리밍에 대한 어린이 에이전트에 사용할 수 있습니다. 액세스 목록은 제한 액세스에 사용될 수 있습니다. https://learn.netdata.cloud/docs/netdata-agent/configuration/securing-agents/web-server-reference#access-lists 타협의 증거는이 스크립트에서 찾을 수 있습니다: https://gist.github.com/ktsaou/b3fcf41c8ce0a01effb6df9d82a14858

2. 2026년 10월 23일 오후 12:35 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

3. 2026년 10월 23일 오후 1:34 UTCmonitoring

   버전 2.12.2 패치 릴리즈는 문제 해결을 가진 안정적인 릴리스 채널에 게시되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 5월 30일 오전 11:21 UTCresolved

   Following a scheduled TLS certificate renewal, a subset of Netdata agents failed to reconnect to Netdata Cloud. The issue stems from outdated CA (Certificate Authority) trust stores on certain legacy Linux distributions, like: • CentOS 7 / RHEL 7 • Amazon Linux 2 • Debian 9 (Jessie) • Ubuntu 16.04 LTS • Oracle Linux 7 A quick way to test for this: curl -v https://app.netdata.cloud If the output shows an error indicating the certificate has expired, the system needs an updated CA bundle.

1. 2026년 5월 8일 오전 1:13 UTCmonitoring

   We are currently tracking an issue with our upstream cloud provider that is affecting a subset of our Kubernetes nodes. As a result, some customers may receive false-positive alerts regarding node reachability. Please be assured that your underlying services and workloads remain operational, and these alerts can be safely ignored at this time. We are closely monitoring the situation with our provider.

2. 2026년 5월 8일 오전 6:00 UTCresolved

   This incident has been resolved.

1. 2026년 5월 8일 오전 12:11 UTCmonitoring

   We are currently tracking an issue with our upstream cloud provider that is affecting a subset of our Kubernetes nodes. As a result, some customers may receive false-positive alerts regarding node reachability. Please be assured that your underlying services and workloads remain operational, and these alerts can be safely ignored at this time. We are closely monitoring the situation with our provider.

2. 2026년 5월 8일 오전 12:12 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 2026년 5월 8일 오전 12:32 UTCresolved

   This incident has been resolved.

1. 2026년 4월 15일 오전 6:38 UTCresolved

   At ~02:20 UTC, a Kubernetes node running part of our ingress controller failed and was auto-replaced. Some clients experienced brief agent disconnections and false-positive node-unavailability alerts during the failover. Service has fully recovered after few minutes. We apologize for the inconvenience.

1. 2026년 3월 9일 오후 1:49 UTCresolved

   Yesterday, a brief infrastructure incident occurred due to certain processes on our load balancer failing (exactly at 16:34 UTC). This caused more than half of our globally connected nodes to reconnect, which in turn triggered false positive alerts notifying clients of node downtime. We apologize for the confusion and are taking steps to ensure this does not happen again.

1. 2026년 1월 22일 오후 12:47 UTCidentified

   We have identified an issue with the latest version of the repository configuration packages for our RHEL 8.x repositories that causes systems which update to that version of the repository configuration package to become unable to access our repositories. This affects all systems that use our repository configuration packages to access our RHEL 8.x repositories, including but not limited to RHEL 8.x, Alma Linux 8.x, Rocky Linux 8.x, and Oracle Linux 8.x. Affected systems will report a failure to download repository metadata for Netdata repositories. A fix is currently being tested and is expected to be deployed soon.

2. 2026년 1월 22일 오후 12:48 UTCidentified

   We are continuing to work on a fix for this issue.

3. 2026년 1월 22일 오후 2:06 UTCmonitoring

   The primary fix has been deployed and appears to be working correctly. We are currently working on a followup fix to allow affected systems to update properly without requiring user intervention. Until that additional fix is deployed, affected systems can be manually updated to fully resolve the issue locally by fetching the latest version of the repository configuration package manually and installing it on the system: - For most RHEL 8 equivalent systems using our stable repositories: https://repository.netdata.cloud/repos/repoconfig/el/8/x86_64/netdata-repo-5-4.noarch.rpm - For most RHEL 8 equivalent systems using our nightly repositories: https://repository.netdata.cloud/repos/repoconfig/el/8/x86_64/netdata-repo-edge-5-4.noarch.rpm - For Oracle Linux 8 systems using our stable repositories: https://repository.netdata.cloud/repos/repoconfig/ol/8/x86_64/netdata-repo-5-4.noarch.rpm - For Oracle Linux 8 systems using our nightly repositories: https://repository.netdata.cloud/repos/repoconfig/ol/8/x86_64/netdata-repo-edge-5-4.noarch.rpm

4. 2026년 1월 22일 오후 3:20 UTCresolved

   In addition to the fix for the repository configuration packages, a fix has been deployed to the repositories themselves that will enable affected systems to update successfully to the latest version of the repository configuration packages, and as such no further issues are expected.

1. 2025년 11월 18일 오후 12:11 UTCinvestigating

   As Cloudflare is experiencing network issues, Netdata Cloud, as well as our package repositories are currently unavailable.

2. 2025년 11월 18일 오후 12:23 UTCmonitoring

   Connectivity is recovering, we'll keep this open until we see traffic at previous levels. See https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 for details on the Cloudflare outage itself.

3. 2025년 11월 18일 오후 7:22 UTCresolved

   This incident has been resolved.

1. 2025년 9월 29일 오전 11:36 UTCidentified

   We've identified an issue with the latest Agent release on Windows that causes the go.d plugin to not be started. The impact is that for Windows nodes, none of the metrics from the go.d plugin are being collected and corresponding alerts don't fire. We will be releasing a patch release to address this as soon as possible today. As a workaround the plugin binary in Program Files can be renamed to add the missing .exe extension.

2. 2025년 9월 30일 오전 5:04 UTCmonitoring

   We have released Netdata Agent v2.7.1 and recommend all Windows users to upgrade. Release notes: https://github.com/netdata/netdata/releases/tag/v2.7.1

3. 2025년 9월 30일 오후 6:29 UTCresolved

   This incident has been resolved.

1. 2025년 8월 21일 오후 7:35 UTCinvestigating

   We are currently investigating issues with availability of our nightly DEB and RPM packages which are preventing updates and installs from working correctly.

2. 2025년 8월 21일 오후 7:39 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2025년 8월 21일 오후 7:42 UTCmonitoring

   A fix has been implemented and we expect the repositories to be functioning normally within the next 30 minutes.

4. 2025년 8월 21일 오후 7:58 UTCresolved

   All repositories are functioning normally again.

1. 2025년 8월 14일 오후 3:03 UTCmonitoring

   Due to issues in our package upload process, the v2.6.2 stable release and the nightly builds for 2025-08-13 and 2025-08-14 were not fully uploaded to our official DEB/RPM repositories. We have already identified the root cause and implemented a fix, and are currently monitoring the processing of the package upload backlog to ensure that all of the packages are properly available.

2. 2025년 8월 14일 오후 3:12 UTCresolved

   We have confirmed that the issue that caused the incomplete package uploads has been fully fixed, and all packages that should have been uploaded since the issue first occurred have been fully uploaded and are available in the repositories.

1. 2025년 8월 11일 오후 12:27 UTCinvestigating

   We are investigating an issue with increased data request latencies that can result in slow or completely empty charts for some customers. The affected Netdata Agent versions are v2.6.0 and later, for all stable and nightly builds.

2. 2025년 8월 11일 오후 2:24 UTCinvestigating

   We will be adding additional debugging code in both the Agent (next nightly) and Cloud Backend to track what is causing these spurious latencies.

3. 2025년 8월 12일 오전 9:28 UTCidentified

   We have identified the cause of this issue and have been creating a fix which will appear in the upcoming nightly build. When we are confident that there are no negative effects on that build, we will do a new patch release on the stable channel the next day. What happened is that we were not correctly clearing MQTT messages that had been acknowledged by the broker, causing newer messages to not be correctly recognized as acknowledged in certain conditions.

4. 2025년 8월 13일 오후 3:30 UTCmonitoring

   We've implement a change for this issue which appeared in our latest nightly, and resolved the problem. We are now issuing a new stable release v2.6.2 to include that fix, and will resolve this issue when all packages are available.

5. 2025년 8월 20일 오후 1:09 UTCresolved

   This incident has been resolved. We recommend that Agents are upgraded to v2.6.2 on the stable channel, or the latest nightly build at the earliest convenience.

1. 2025년 7월 25일 오후 12:27 UTCmonitoring

   We identified monitoring issues affecting customers using Netdata Agent version 2.6.0 on Windows servers. These issues were caused by upstream changes in Windows libraries that impacted agent functionality. Resolution Fixed Version Available: Netdata Agent v2.6.1 Release Date: July 25, 2025 (16:00 UTC) Preview Available: Nightly release v2.6.0-2 Required Action Immediate upgrade recommended - All users running Netdata Agent v2.6.0 on Windows servers should upgrade to v2.6.1 as soon as possible to restore full monitoring capabilities. We appreciate your patience as we continue working on additional improvements related to the upstream Windows library changes.

2. 2025년 7월 28일 오전 10:44 UTCresolved

   This incident has been resolved.

1. 2025년 6월 4일 오후 12:59 UTCidentified

   We had a major problem with our MQTT broker. It is currently up and running and agents are reconnecting to the cloud.

2. 2025년 6월 4일 오후 1:42 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2025년 6월 4일 오후 1:49 UTCresolved

   This incident has been resolved.

1. 2025년 4월 1일 오전 9:00 UTCinvestigating

   We have found that a recent change in the nightly static builds of Netdata Agent causes meta data on the Agent to be overwritten. Specifically the sqlite3 database that keeps meta data on which timeseries stored in dbengine correspond with which metrics, and the information on the Agent's "machine GUID" are overwritten with the same copy in the build package. Not affected are: - All stable releases - Native packages (.deb and .rpm) Affected are all nightly static builds with the following version numbers: - 2.3.0-50-nightly - 2.3.0-60-nightly - 2.3.0-72-nightly - 2.3.0-78-nightly - 2.3.0-87-nightly The initial impact is that all affected Agent installs, even though they still have the timeseries data stored on disk, have lost all meta data associated with it, so these timeseries become inaccessable. This is unrecoverable. Additionally, the main form of identification is overwritten, too. We are assessing what the impact is for users of Netdata Cloud, and will update this incident with more information when the investigation is completed. The bug itself has been fixed and merged. We will issue a new nightly build shortly.

2. 2025년 4월 2일 오전 9:25 UTCresolved

   Affected Agents can cause the creation of multiple duplicate nodes in Netdata Cloud. All but the last one will appear as offline, and the last one will be as if it was created from scratch with no data. Unfortunately, the previously stored metrics for the affected nodes can not be recovered. The duplicate offline nodes can be safely deleted from Space Settings -> Nodes. Note that you may have to add the newest copy of these nodes to the appropriate rooms. The fixed nightly static build is v2.3.0-102.

1. 2025년 2월 25일 오전 9:41 UTCinvestigating

   We are investigating an issue with today's nightly (v2.2.0-245), causing alerting to not work ("health") and external plugins, including go.d, to not connect properly. This may be resolved by restarting the Agent. Stable versions of the Agent are not affected.

2. 2025년 2월 25일 오전 11:04 UTCidentified

   We have identified the issue, committed a fix, and initiated new nightly builds for all platforms. This will take several hours. In the mean time, please restart Netdata to work around the issue.

3. 2025년 2월 25일 오후 1:14 UTCmonitoring

   The builds are completed, so we are watching out for any remaining related issues.

4. 2025년 2월 25일 오후 1:29 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2025년 2월 25일 오후 3:25 UTCresolved

   This incident has been resolved.

1. 2024년 11월 15일 오전 8:23 UTCresolved

   Our alarm processing infrastructure was running behind which is causing inaccuracies alarms for some nodes. No data has been lost and the systems should be already up to date.

1. 2024년 11월 8일 오전 8:07 UTCinvestigating

   Due to the release of Netdata Agent 2.0 we have quite a big backlog for alarms. We are investigating this issue.

2. 2024년 11월 8일 오전 9:49 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2024년 11월 8일 오전 11:01 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2024년 11월 8일 오후 1:36 UTCresolved

   This incident has been resolved.

1. 2024년 7월 18일 오전 4:45 UTCinvestigating

   We were alerted to a delay in alarms for some users and are investigating the matter.

2. 2024년 7월 18일 오전 5:37 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2024년 7월 18일 오전 8:17 UTCidentified

   Currently, we are waiting for the fix to take effect, and some users might experience delays in all cloud operations.

4. 2024년 7월 18일 오전 11:41 UTCresolved

   This incident has been resolved.

1. 2024년 5월 1일 오후 3:44 UTCidentified

   We've identified an issue with static and local builds of the Netdata Agent, that causes its main configuration in `/etc/netdata/netdata.conf` or `/opt/netdata/etc/netdata/netdata.conf` to be overwritten with the default. The `netdata-updater.conf` file is similarly affected. Depending on your configuration settings that have been changed with respect to the defaults, this may result in data loss. We will update this incident with more detailed information on the impact as soon as possible. Docker image or native package builds, as well as stable builds, are not affected. We have created a fix (https://github.com/netdata/netdata/pull/17572) and have triggered a new nightly build. As soon as those are available, we will also update this incident.

2. 2024년 5월 1일 오후 3:59 UTCidentified

   The affected build number is v1.45.0-315-nightly, and local builds starting with commit https://github.com/netdata/netdata/commit/5973417027606bacf044b3ead40a882931ce773f (April 30, 11:45 UTC) up until commit https://github.com/netdata/netdata/commit/0f2a261839d5ffc42f17383b4292673aa93d6a1f (May 1, 15:13 UTC).

3. 2024년 5월 1일 오후 4:28 UTCidentified

   Update regarding potential data loss. This will happen if the configuration had been changed to increase metric retention (with respect to the defaults). Unfortunately, any stored data beyond the default metric retention will be lost on running installs of the affected builds. The only way to prevent this is by not using (of having used) version v1.45.0-315-nightly. We have made sure that the corresponding artifacts are no longer accessible by the installer.

4. 2024년 5월 1일 오후 5:22 UTCresolved

   The build artifacts for the new nightly release (1.45.0-326) are now available, and consider the incident resolved. Should you experience any issues, please let us know!

5. 2024년 5월 2일 오전 10:02 UTCpostmortem

   Prior to [netdata/netdata#17475](https://github.com/netdata/netdata/pull/17475), the `netdata.conf` and `netdata-updater.conf` files where handled by the installer code outside of the build system. With the shift to using the build system to produce packages, handling for them needed to be moved into the build system. However, insufficient testing was performed to confirm that this would not break other installation types, and the change was not properly made conditional on packages being built. As a result, the static and local builds with version `v1.45.0-315-nightly` will overwrite these configuration files with the default templates for those files. This causes all local changes to those files to be lost. In particular, if the Agent configuration had been changed for longer retention, the overwritten configuration will have undone those settings, causing any metrics data **beyond the _default_ retention to be lost** on the first run of this version. We have pulled the affected build artifacts to prevent our installer from using them. While [the fix](https://github.com/netdata/netdata/pull/17572) ensures the issue won't occur in future versions, starting with version `v1.45.0-326-nightly`, it is important to note that affected installations **will not automatically recover** their previous configurations. If you were using a non-default `netdata.conf` and/or `netdata-updater.conf` and experienced this bug, you will need to **manually reconfigure** your Netdata install. As we aim to carefully develop Netdata for many platforms and hardware architectures, we release nightly builds of the Netdata Agent to catch any issues our changes may have caused, beyond our own internal testing. Unfortunately, we make mistakes that we did not catch in our testing, with data loss as an extreme possible outcome. Therefore we strongly recommend using our **stable releases for production systems**. You can review the [difference between nightly and stable builds](https://learn.netdata.cloud/docs/netdata-agent/installation#nightly-vs-stable-releases), and our recommended [best practices](https://www.netdata.cloud/blog/netdata-best-practices/). If you have been affected by this issue and/or have any questions, please let us know.