Netdata: Monitoring and troubleshooting transformed on Netdatahttps://www.netdata.cloud/Recent content in Netdata: Monitoring and troubleshooting transformed on NetdataHugoen-usIntroducing Infrastructure Knowledge: Teach Netdata AI What Your Metrics Can't Showhttps://www.netdata.cloud/blog/infrastructure-knowledge/Tue, 08 Sep 2026 00:00:00 +0000https://www.netdata.cloud/blog/infrastructure-knowledge/<p>Netdata AI sees everything your infrastructure does: every metric, every anomaly, every alert. It does not see what your infrastructure is: which services matter, which host is supposed to run hot, who owns what, what your team considers normal. Without that context, &ldquo;CPU at 91%&rdquo; is just a finding. With it, it might be a machine doing exactly its job.</p> <!--truncate--> <h2 id="two-places-to-put-it">Two places to put it</h2> <p><strong>Infrastructure Knowledge</strong> holds that context. The more you tell Netdata AI about your environment, the more accurate its answers get.</p>Malmö stad: A Full Day of Troubleshooting Cut to 30 Minuteshttps://www.netdata.cloud/case-studies/government/malmo-stad/Tue, 08 Sep 2026 00:00:00 +0000https://www.netdata.cloud/case-studies/government/malmo-stad/<p>Malmö stad runs the digital services behind a city of roughly 366,000 people. Waste collection schedules, school administration, social services intake, the public-facing sites residents use to reach any of it. The IT team responsible for keeping that infrastructure healthy is between two and five people, and it covers every environment the city operates: development, test, staging and production.</p> <div class="cs-stats"> <div class="cs-stat"><span class="cs-stat__n">&lt; 30 min</span><span class="cs-stat__l">To resolve a mission-critical slowdown that would previously have taken a full working day</span></div> <div class="cs-stat"><span class="cs-stat__n">~10 hrs</span><span class="cs-stat__l">Engineer time returned to the team each week, mostly from reporting and troubleshooting</span></div> <div class="cs-stat"><span class="cs-stat__n">51–200</span><span class="cs-stat__l">Nodes covered across every environment by a team of two to five people</span></div> </div> <p>That ratio is the whole story. A team that size cannot afford to spend a day chasing one slow system, and for years the tooling gave them no way to avoid it.</p>Hours to Minutes: AI-Led Root Cause at a Not-for-Profit Care Providerhttps://www.netdata.cloud/case-studies/healthcare/health-social-care-provider/Mon, 07 Sep 2026 00:00:00 +0000https://www.netdata.cloud/case-studies/healthcare/health-social-care-provider/<p>This organization shared its results with us but asked not to be named. The industry, the scale of the estate and the specifics of what changed are all as reported; the identifying details are withheld.</p> <p>A UK not-for-profit delivering health and social care services runs more than a thousand monitored nodes across every environment it operates. Infrastructure architecture is owned by a team of between two and five people, which means the ratio of estate to engineers leaves very little room for a long investigation.</p>Four Hours Back Per Root Cause at a Global Food Ingredients Manufacturerhttps://www.netdata.cloud/case-studies/manufacturing/food-ingredients-manufacturer/Sun, 06 Sep 2026 00:00:00 +0000https://www.netdata.cloud/case-studies/manufacturing/food-ingredients-manufacturer/<p>This organization shared its results with us but asked not to be named. The industry, the scale of the estate and the specifics of what changed are all as reported; the identifying details are withheld.</p> <p>A global food and bio-based ingredients manufacturer runs between 201 and 1,000 monitored nodes across every environment, managed by a cloud infrastructure team of six to twenty people. The previous monitoring stack had four problems at once, and they compounded each other.</p>Less Noise, Better Answers: Monitoring at a Global Game Publisherhttps://www.netdata.cloud/case-studies/gaming/game-publisher/Sat, 05 Sep 2026 00:00:00 +0000https://www.netdata.cloud/case-studies/gaming/game-publisher/<p>This organization shared its results with us but asked not to be named. The industry, the scale of the estate and the specifics of what changed are all as reported; the identifying details are withheld.</p> <p>A global video game publisher runs between 201 and 1,000 monitored production nodes. The technical architecture team&rsquo;s problem was not a lack of monitoring. It was that monitoring had become two jobs: watching the estate, and looking after the thing that watched the estate.</p>Retiring Nagios at a Consumer Auto Finance Lenderhttps://www.netdata.cloud/case-studies/fintech/consumer-auto-finance-lender/Fri, 04 Sep 2026 00:00:00 +0000https://www.netdata.cloud/case-studies/fintech/consumer-auto-finance-lender/<p>This organization shared its results with us but asked not to be named. The industry, the scale of the estate and the specifics of what changed are all as reported; the identifying details are withheld.</p> <p>A consumer auto finance lender runs more than a thousand monitored nodes across development, test, staging and production. Infrastructure monitoring ran on Nagios. Netdata replaced it completely.</p> <div class="cs-stats"> <div class="cs-stat"><span class="cs-stat__n">Nagios retired</span><span class="cs-stat__l">Removed entirely, rather than run alongside a replacement indefinitely</span></div> <div class="cs-stat"><span class="cs-stat__n">1,000+</span><span class="cs-stat__l">Nodes covered across development, test, staging and production</span></div> <div class="cs-stat"><span class="cs-stat__n">Regulated</span><span class="cs-stat__l">Lending estate, where predictable cost and data control carry compliance weight</span></div> </div> <h2 id="what-nagios-could-not-give-them">What Nagios could not give them</h2> <p>Nagios is a capable check scheduler and it has kept a great many estates running for a very long time. What it does not do is give you depth. It tells you that a check passed or failed, which is a different thing from telling you what the machine was actually doing at the time.</p>One Standard for Every Product Team at a Digital Marketplace Operatorhttps://www.netdata.cloud/case-studies/technology/digital-marketplace-operator/Thu, 03 Sep 2026 00:00:00 +0000https://www.netdata.cloud/case-studies/technology/digital-marketplace-operator/<p>This organization shared its results with us but asked not to be named. The industry, the scale of the estate and the specifics of what changed are all as reported; the identifying details are withheld.</p> <p>This company operates several consumer digital marketplaces on shared infrastructure, with between 51 and 200 monitored nodes across production and staging. Engineering is organized by product, and before Netdata, so was monitoring.</p> <h2 id="every-team-solving-the-same-problem-separately">Every team solving the same problem separately</h2> <p>There were dashboards. That was not the issue. The issue was that each product team had built its own, to its own conventions, covering its own slice.</p>OfficeCore: The Crash They Could See, and the Two They Could Nothttps://www.netdata.cloud/case-studies/technology/officecore/Wed, 02 Sep 2026 00:00:00 +0000https://www.netdata.cloud/case-studies/technology/officecore/<p>OfficeCore builds OfficeTrack, a platform for managing mobile workforces and vehicle fleets, used by more than a thousand business customers. Between 51 and 200 nodes carry it across every environment, and the team looking after them is between two and five people.</p> <div class="cs-stats"> <div class="cs-stat"><span class="cs-stat__n">3 services</span><span class="cs-stat__l">Crashed in one incident. The team could see only the one that reached customers</span></div> <div class="cs-stat"><span class="cs-stat__n">Minutes</span><span class="cs-stat__l">To reach root cause, fast enough that the logs were still there to read</span></div> <div class="cs-stat"><span class="cs-stat__n">51–200</span><span class="cs-stat__l">Nodes across every environment, run by a team of two to five</span></div> </div> <h2 id="visibility-that-had-thinned-and-a-bill-that-had-not">Visibility that had thinned, and a bill that had not</h2> <p>Two problems arrived together, which is often how monitoring decisions get made.</p>Kavenegarhttps://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/kavenegar/Tue, 25 Aug 2026 13:37:36 +0000https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/kavenegar/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Palo Alto Networks PAN-OShttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/palo-alto-networks-pan-os/Tue, 25 Aug 2026 13:37:36 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/palo-alto-networks-pan-os/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->HAProxy Prometheushttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/haproxy-prometheus/Mon, 24 Aug 2026 14:16:04 +0000https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/haproxy-prometheus/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ceph Prometheushttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ceph-prometheus/Mon, 24 Aug 2026 08:40:59 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ceph-prometheus/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->LiteLLMhttps://www.netdata.cloud/integrations/data-collection/applications/litellm/Mon, 24 Aug 2026 08:40:59 +0000https://www.netdata.cloud/integrations/data-collection/applications/litellm/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Prometheus endpointhttps://www.netdata.cloud/integrations/data-collection/applications/prometheus-endpoint/Mon, 24 Aug 2026 08:40:59 +0000https://www.netdata.cloud/integrations/data-collection/applications/prometheus-endpoint/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->vLLMhttps://www.netdata.cloud/integrations/data-collection/applications/vllm/Mon, 24 Aug 2026 08:40:59 +0000https://www.netdata.cloud/integrations/data-collection/applications/vllm/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->4D Serverhttps://www.netdata.cloud/integrations/data-collection/databases/4d-server/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/4d-server/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->8430FT modemhttps://www.netdata.cloud/integrations/data-collection/networking/8430ft-modem/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/networking/8430ft-modem/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Alamos FE2 serverhttps://www.netdata.cloud/integrations/data-collection/applications/alamos-fe2-server/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/alamos-fe2-server/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->AMD CPU & GPUhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/amd-cpu--gpu/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/amd-cpu--gpu/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->APIcasthttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/apicast/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/apicast/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->AuthLoghttps://www.netdata.cloud/integrations/data-collection/applications/authlog/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/authlog/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->AWS EC2 Compute instanceshttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/aws-ec2-compute-instances/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/aws-ec2-compute-instances/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->AWS Quotahttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/aws-quota/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/aws-quota/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->AWS RDShttps://www.netdata.cloud/integrations/data-collection/databases/aws-rds/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/aws-rds/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bird Routing Daemonhttps://www.netdata.cloud/integrations/data-collection/networking/bird-routing-daemon/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/networking/bird-routing-daemon/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Blackboxhttps://www.netdata.cloud/integrations/data-collection/synthetic-testing/blackbox/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/synthetic-testing/blackbox/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->BOSHhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/bosh/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/bosh/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->BungeeCordhttps://www.netdata.cloud/integrations/data-collection/applications/bungeecord/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/bungeecord/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Celeryhttps://www.netdata.cloud/integrations/data-collection/applications/celery/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/celery/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cephhttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ceph/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ceph/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Chiahttps://www.netdata.cloud/integrations/data-collection/applications/chia/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/chia/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Christ Elektronik CLM5IP power panelhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/christ-elektronik-clm5ip-power-panel/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/christ-elektronik-clm5ip-power-panel/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cilium Agenthttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/cilium-agent/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/cilium-agent/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cilium Operatorhttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/cilium-operator/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/cilium-operator/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cilium Proxyhttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/cilium-proxy/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/cilium-proxy/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ClamAV daemonhttps://www.netdata.cloud/integrations/data-collection/applications/clamav-daemon/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/clamav-daemon/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Clamscan resultshttps://www.netdata.cloud/integrations/data-collection/applications/clamscan-results/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/clamscan-results/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Clashhttps://www.netdata.cloud/integrations/data-collection/networking/clash/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/networking/clash/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cloud Foundryhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/cloud-foundry/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/cloud-foundry/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cloud Foundry Firehosehttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/cloud-foundry-firehose/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/cloud-foundry-firehose/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ClusterControl CMONhttps://www.netdata.cloud/integrations/data-collection/databases/clustercontrol-cmon/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/clustercontrol-cmon/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Collectdhttps://www.netdata.cloud/integrations/data-collection/applications/collectd/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/collectd/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Concoursehttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/concourse/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/concourse/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->CraftBeerPihttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/craftbeerpi/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/craftbeerpi/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Crowdsechttps://www.netdata.cloud/integrations/data-collection/applications/crowdsec/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/crowdsec/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cryptowatchhttps://www.netdata.cloud/integrations/data-collection/applications/cryptowatch/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/cryptowatch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Discoursehttps://www.netdata.cloud/integrations/data-collection/applications/discourse/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/discourse/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->DMARChttps://www.netdata.cloud/integrations/data-collection/applications/dmarc/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/dmarc/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->DNSBLhttps://www.netdata.cloud/integrations/data-collection/networking/dnsbl/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/networking/dnsbl/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dutch Electricity Smart Meterhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/dutch-electricity-smart-meter/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/dutch-electricity-smart-meter/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dynatrace (go.d.plugin prometheus)https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/dynatrace/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/dynatrace/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Elgato Key Light devices.https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/elgato-key-light-devices./Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/elgato-key-light-devices./<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->EOShttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/eos/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/eos/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->etcdhttps://www.netdata.cloud/integrations/data-collection/applications/etcd/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/etcd/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fastdhttps://www.netdata.cloud/integrations/data-collection/networking/fastd/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/networking/fastd/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->FreeBSD NFShttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/freebsd-nfs/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/freebsd-nfs/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->FreeBSD RCTL-RACCThttps://www.netdata.cloud/integrations/data-collection/operating-systems/freebsd-rctl-racct/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/freebsd-rctl-racct/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Freifunk networkhttps://www.netdata.cloud/integrations/data-collection/networking/freifunk-network/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/networking/freifunk-network/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->FRRoutinghttps://www.netdata.cloud/integrations/data-collection/networking/frrouting/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/networking/frrouting/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->GCP GCEhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/gcp-gce/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/gcp-gce/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Generic storage enclosure toolhttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/generic-storage-enclosure-tool/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/generic-storage-enclosure-tool/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->GitHub API rate limithttps://www.netdata.cloud/integrations/data-collection/applications/github-api-rate-limit/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/github-api-rate-limit/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->GitHub repositoryhttps://www.netdata.cloud/integrations/data-collection/applications/github-repository/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/github-repository/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->GitLab Runnerhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/gitlab-runner/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/gitlab-runner/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Gobetweenhttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/gobetween/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/gobetween/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Google Cloud Platformhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/google-cloud-platform/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/google-cloud-platform/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Google Pagespeedhttps://www.netdata.cloud/integrations/data-collection/applications/google-pagespeed/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/google-pagespeed/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Google Stackdriverhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/google-stackdriver/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/google-stackdriver/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->gpsdhttps://www.netdata.cloud/integrations/data-collection/applications/gpsd/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/gpsd/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Grafanahttps://www.netdata.cloud/integrations/data-collection/applications/grafana/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/grafana/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Graylog Serverhttps://www.netdata.cloud/integrations/data-collection/applications/graylog-server/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/graylog-server/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Halonhttps://www.netdata.cloud/integrations/data-collection/applications/halon/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/halon/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->HANAhttps://www.netdata.cloud/integrations/data-collection/databases/hana/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/hana/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Hitron CODA Cable Modemhttps://www.netdata.cloud/integrations/data-collection/networking/hitron-coda-cable-modem/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/networking/hitron-coda-cable-modem/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Homebridgehttps://www.netdata.cloud/integrations/data-collection/applications/homebridge/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/homebridge/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Homeyhttps://www.netdata.cloud/integrations/data-collection/applications/homey/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/homey/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Honeypothttps://www.netdata.cloud/integrations/data-collection/applications/honeypot/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/honeypot/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->HTTP Endpointshttps://www.netdata.cloud/integrations/data-collection/synthetic-testing/http-endpoints/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/synthetic-testing/http-endpoints/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Hubblehttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/hubble/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/hubble/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IBM AIX systems Njmonhttps://www.netdata.cloud/integrations/data-collection/applications/ibm-aix-systems-njmon/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/ibm-aix-systems-njmon/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IBM CryptoExpress (CEX) cardshttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/ibm-cryptoexpress-cex-cards/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/ibm-cryptoexpress-cex-cards/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IBM MQ (go.d.plugin prometheus)https://www.netdata.cloud/integrations/data-collection/databases/ibm-mq/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/ibm-mq/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IBM Spectrumhttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ibm-spectrum/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ibm-spectrum/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IBM Spectrum Virtualizehttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ibm-spectrum-virtualize/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ibm-spectrum-virtualize/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IBM Z Hardware Management Consolehttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/ibm-z-hardware-management-console/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/ibm-z-hardware-management-console/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->InfluxDBhttps://www.netdata.cloud/integrations/data-collection/databases/influxdb/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/influxdb/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Jarvis Standing Deskhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/jarvis-standing-desk/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/jarvis-standing-desk/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Jenkinshttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/jenkins/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/jenkins/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->JMXhttps://www.netdata.cloud/integrations/data-collection/applications/jmx/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/jmx/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->journaldhttps://www.netdata.cloud/integrations/data-collection/applications/journald/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/journald/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kafka (go.d.plugin prometheus)https://www.netdata.cloud/integrations/data-collection/databases/kafka/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/kafka/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kafka Consumer Laghttps://www.netdata.cloud/integrations/data-collection/databases/kafka-consumer-lag/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/kafka-consumer-lag/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kafka ZooKeeperhttps://www.netdata.cloud/integrations/data-collection/databases/kafka-zookeeper/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/kafka-zookeeper/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kannelhttps://www.netdata.cloud/integrations/data-collection/applications/kannel/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/kannel/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Keepalivedhttps://www.netdata.cloud/integrations/data-collection/networking/keepalived/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/networking/keepalived/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Linodehttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/linode/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/linode/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->lokihttps://www.netdata.cloud/integrations/data-collection/applications/loki/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/loki/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Lustre metadatahttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/lustre-metadata/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/lustre-metadata/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Lynis audit reportshttps://www.netdata.cloud/integrations/data-collection/applications/lynis-audit-reports/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/lynis-audit-reports/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Meilisearchhttps://www.netdata.cloud/integrations/data-collection/databases/meilisearch/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/meilisearch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mesoshttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/mesos/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/mesos/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Minecrafthttps://www.netdata.cloud/integrations/data-collection/applications/minecraft/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/minecraft/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Modbus protocolhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/modbus-protocol/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/modbus-protocol/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->MogileFShttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/mogilefs/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/mogilefs/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->mosquittohttps://www.netdata.cloud/integrations/data-collection/databases/mosquitto/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/mosquitto/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->MQTT Blackboxhttps://www.netdata.cloud/integrations/data-collection/synthetic-testing/mqtt-blackbox/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/synthetic-testing/mqtt-blackbox/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->mtailhttps://www.netdata.cloud/integrations/data-collection/applications/mtail/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/mtail/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nature Remo E lite deviceshttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/nature-remo-e-lite-devices/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/nature-remo-e-lite-devices/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netapp ONTAP APIhttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/netapp-ontap-api/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/netapp-ontap-api/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NetApp Solidfirehttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/netapp-solidfire/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/netapp-solidfire/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netatmo sensorshttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/netatmo-sensors/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/netatmo-sensors/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nextcloud servershttps://www.netdata.cloud/integrations/data-collection/applications/nextcloud-servers/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/nextcloud-servers/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NextDNShttps://www.netdata.cloud/integrations/data-collection/networking/nextdns/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/networking/nextdns/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NRPE daemonhttps://www.netdata.cloud/integrations/data-collection/applications/nrpe-daemon/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/nrpe-daemon/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->OBS Studiohttps://www.netdata.cloud/integrations/data-collection/applications/obs-studio/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/obs-studio/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Open vSwitchhttps://www.netdata.cloud/integrations/data-collection/networking/open-vswitch/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/networking/open-vswitch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->OpenRChttps://www.netdata.cloud/integrations/data-collection/operating-systems/openrc/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/openrc/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->OpenROADM deviceshttps://www.netdata.cloud/integrations/data-collection/networking/openroadm-devices/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/networking/openroadm-devices/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->OpenWeatherMaphttps://www.netdata.cloud/integrations/data-collection/applications/openweathermap/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/openweathermap/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Patronihttps://www.netdata.cloud/integrations/data-collection/databases/patroni/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/patroni/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Personal Weather Stationhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/personal-weather-station/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/personal-weather-station/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->pgBackResthttps://www.netdata.cloud/integrations/data-collection/databases/pgbackrest/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/pgbackrest/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pgpool-IIhttps://www.netdata.cloud/integrations/data-collection/databases/pgpool-ii/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/pgpool-ii/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Philips Huehttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/philips-hue/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/philips-hue/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pimoroni Enviro+https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/pimoroni-enviro+/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/pimoroni-enviro+/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Podmanhttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/podman/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/podman/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Powerpal deviceshttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/powerpal-devices/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/powerpal-devices/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ProFTPDhttps://www.netdata.cloud/integrations/data-collection/applications/proftpd/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/proftpd/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Proxmox VEhttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/proxmox-ve/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/proxmox-ve/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Radio Thermostathttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/radio-thermostat/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/radio-thermostat/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->RADIUShttps://www.netdata.cloud/integrations/data-collection/applications/radius/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/radius/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Raritan PDUhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/raritan-pdu/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/raritan-pdu/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Redis Queuehttps://www.netdata.cloud/integrations/data-collection/databases/redis-queue/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/redis-queue/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->RIPE Atlashttps://www.netdata.cloud/integrations/data-collection/networking/ripe-atlas/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/networking/ripe-atlas/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SABnzbdhttps://www.netdata.cloud/integrations/data-collection/applications/sabnzbd/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/sabnzbd/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Salicru EQX inverterhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/salicru-eqx-inverter/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/salicru-eqx-inverter/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ScyllaDBhttps://www.netdata.cloud/integrations/data-collection/databases/scylladb/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/scylladb/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sense Energyhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/sense-energy/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/sense-energy/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Shelly humidity sensorhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/shelly-humidity-sensor/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/shelly-humidity-sensor/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Siemens S7 PLChttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/siemens-s7-plc/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/siemens-s7-plc/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Site 24x7https://www.netdata.cloud/integrations/data-collection/synthetic-testing/site-24x7/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/synthetic-testing/site-24x7/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Slurmhttps://www.netdata.cloud/integrations/data-collection/applications/slurm/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/slurm/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SMA Invertershttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/sma-inverters/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/sma-inverters/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Smart meters SMLhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/smart-meters-sml/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/smart-meters-sml/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SoftEther VPN Serverhttps://www.netdata.cloud/integrations/data-collection/networking/softether-vpn-server/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/networking/softether-vpn-server/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Solar logging stickhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/solar-logging-stick/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/solar-logging-stick/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Solis Ginlong 5G invertershttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/solis-ginlong-5g-inverters/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/solis-ginlong-5g-inverters/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SONiC NOShttps://www.netdata.cloud/integrations/data-collection/networking/sonic-nos/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/networking/sonic-nos/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Spacelifthttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/spacelift/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/spacelift/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sphinxhttps://www.netdata.cloud/integrations/data-collection/databases/sphinx/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/sphinx/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Starlink (SpaceX)https://www.netdata.cloud/integrations/data-collection/networking/starlink-spacex/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/networking/starlink-spacex/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->StatusPagehttps://www.netdata.cloud/integrations/data-collection/applications/statuspage/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/statuspage/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Steamhttps://www.netdata.cloud/integrations/data-collection/applications/steam/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/steam/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Storidgehttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/storidge/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/storidge/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->strongSwanhttps://www.netdata.cloud/integrations/data-collection/networking/strongswan/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/networking/strongswan/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sunspec Solar Energyhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/sunspec-solar-energy/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/sunspec-solar-energy/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Suricatahttps://www.netdata.cloud/integrations/data-collection/applications/suricata/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/suricata/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Synology ActiveBackuphttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/synology-activebackup/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/synology-activebackup/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sysloadhttps://www.netdata.cloud/integrations/data-collection/applications/sysload/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/sysload/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->TACACShttps://www.netdata.cloud/integrations/data-collection/applications/tacacs/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/tacacs/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tado smart heating solutionhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/tado-smart-heating-solution/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/tado-smart-heating-solution/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tankerkoenig APIhttps://www.netdata.cloud/integrations/data-collection/applications/tankerkoenig-api/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/tankerkoenig-api/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tesla vehiclehttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/tesla-vehicle/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/tesla-vehicle/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tesla Wall Connectorhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/tesla-wall-connector/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/tesla-wall-connector/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Twitchhttps://www.netdata.cloud/integrations/data-collection/applications/twitch/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/twitch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ubiquiti UFiber OLThttps://www.netdata.cloud/integrations/data-collection/networking/ubiquiti-ufiber-olt/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/networking/ubiquiti-ufiber-olt/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Uptimerobothttps://www.netdata.cloud/integrations/data-collection/synthetic-testing/uptimerobot/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/synthetic-testing/uptimerobot/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Vault PKIhttps://www.netdata.cloud/integrations/data-collection/applications/vault-pki/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/vault-pki/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Verticahttps://www.netdata.cloud/integrations/data-collection/databases/vertica/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/vertica/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->VSCodehttps://www.netdata.cloud/integrations/data-collection/applications/vscode/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/vscode/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Warp10https://www.netdata.cloud/integrations/data-collection/databases/warp10/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/databases/warp10/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Web server log fileshttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/web-server-log-files/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/web-server-log-files/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->X.509 certificatehttps://www.netdata.cloud/integrations/data-collection/synthetic-testing/x.509-certificate/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/synthetic-testing/x.509-certificate/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Xiaomi Mi Florahttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/xiaomi-mi-flora/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/xiaomi-mi-flora/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->YOURLS URL Shortenerhttps://www.netdata.cloud/integrations/data-collection/applications/yourls-url-shortener/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/applications/yourls-url-shortener/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Zertohttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/zerto/Sun, 23 Aug 2026 18:54:14 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/zerto/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->BOINChttps://www.netdata.cloud/integrations/data-collection/applications/boinc/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/data-collection/applications/boinc/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Consulhttps://www.netdata.cloud/integrations/data-collection/applications/consul/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/data-collection/applications/consul/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->DB-IP IP Intelligencehttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/db-ip-ip-intelligence/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/db-ip-ip-intelligence/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Decapsulationhttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/decapsulation/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/decapsulation/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Docker Enginehttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/docker-engine/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/docker-engine/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dovecothttps://www.netdata.cloud/integrations/data-collection/applications/dovecot/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/data-collection/applications/dovecot/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dynatrace (Agent notifications)https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/dynatrace/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/dynatrace/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->eBPF DCstathttps://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-dcstat/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-dcstat/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Elasticsearch (go.d.plugin elasticsearch)https://www.netdata.cloud/integrations/data-collection/databases/elasticsearch/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/data-collection/databases/elasticsearch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Flockhttps://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/flock/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/flock/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->MongoDB (Exporter)https://www.netdata.cloud/integrations/exporters/mongodb/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/exporters/mongodb/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NATShttps://www.netdata.cloud/integrations/data-collection/databases/nats/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/data-collection/databases/nats/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ntfyhttps://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/ntfy/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/ntfy/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NVMe deviceshttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/nvme-devices/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/nvme-devices/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->OpenSearchhttps://www.netdata.cloud/integrations/data-collection/databases/opensearch/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/data-collection/databases/opensearch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->PagerDuty (Agent notifications)https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/pagerduty/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/pagerduty/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pushbullethttps://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/pushbullet/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/pushbullet/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->RocketChat (Cloud notifications)https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/rocketchat/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/rocketchat/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Splunk VictorOpshttps://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/splunk-victorops/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/splunk-victorops/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Squid log fileshttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/squid-log-files/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/squid-log-files/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ubiquiti Net-SNMP Deviceshttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ubiquiti-net-snmp-devices/Sun, 23 Aug 2026 15:00:46 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ubiquiti-net-snmp-devices/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ActiveMQhttps://www.netdata.cloud/integrations/data-collection/databases/activemq/Sat, 22 Aug 2026 13:21:18 +0000https://www.netdata.cloud/integrations/data-collection/databases/activemq/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Docker (Service discovery)https://www.netdata.cloud/integrations/all/docker/Sat, 22 Aug 2026 13:21:18 +0000https://www.netdata.cloud/integrations/all/docker/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->HTTP endpointhttps://www.netdata.cloud/integrations/all/http-endpoint/Sat, 22 Aug 2026 13:21:18 +0000https://www.netdata.cloud/integrations/all/http-endpoint/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kuberneteshttps://www.netdata.cloud/integrations/all/kubernetes/Sat, 22 Aug 2026 13:21:18 +0000https://www.netdata.cloud/integrations/all/kubernetes/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Local listening processeshttps://www.netdata.cloud/integrations/all/local-listening-processes/Sat, 22 Aug 2026 13:21:18 +0000https://www.netdata.cloud/integrations/all/local-listening-processes/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->OpenTelemetryhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/opentelemetry/Sat, 22 Aug 2026 13:21:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/opentelemetry/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ProxySQLhttps://www.netdata.cloud/integrations/data-collection/databases/proxysql/Sat, 22 Aug 2026 13:21:18 +0000https://www.netdata.cloud/integrations/data-collection/databases/proxysql/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SNMPhttps://www.netdata.cloud/integrations/all/snmp/Sat, 22 Aug 2026 13:21:18 +0000https://www.netdata.cloud/integrations/all/snmp/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SQL databases (generic)https://www.netdata.cloud/integrations/data-collection/databases/sql-databases-generic/Sat, 22 Aug 2026 13:21:18 +0000https://www.netdata.cloud/integrations/data-collection/databases/sql-databases-generic/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->VMware vCenter Serverhttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/vmware-vcenter-server/Sat, 22 Aug 2026 13:21:18 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/vmware-vcenter-server/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Applicationshttps://www.netdata.cloud/integrations/data-collection/operating-systems/applications/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/applications/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->AWS ECS Containershttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/aws-ecs-containers/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/aws-ecs-containers/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->containerd Containershttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/containerd-containers/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/containerd-containers/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Containershttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/containers/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/containers/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Docker Containershttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/docker-containers/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/docker-containers/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->eBPF Cachestathttps://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-cachestat/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-cachestat/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Libvirt VMs and Containershttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/libvirt-vms-and-containers/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/libvirt-vms-and-containers/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Live Network Connectionshttps://www.netdata.cloud/integrations/network-performance-monitoring/topologies/live-network-connections/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/topologies/live-network-connections/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->LXC Containershttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/lxc-containers/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/lxc-containers/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Network Connectionshttps://www.netdata.cloud/integrations/data-collection/networking/network-connections/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/data-collection/networking/network-connections/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nomad Containershttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/nomad-containers/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/nomad-containers/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->OpenStack VMshttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/openstack-vms/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/openstack-vms/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->oVirt VMshttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/ovirt-vms/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/ovirt-vms/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Podman Containershttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/podman-containers/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/podman-containers/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Proxmox VMs and Containershttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/proxmox-vms-and-containers/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/proxmox-vms-and-containers/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Synology Disk Stationhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/synology-disk-station/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/synology-disk-station/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Systemd Serviceshttps://www.netdata.cloud/integrations/data-collection/operating-systems/systemd-services/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/systemd-services/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->systemd-nspawn Containershttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/systemd-nspawn-containers/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/systemd-nspawn-containers/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Virtual Machineshttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/virtual-machines/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/virtual-machines/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Windows Network Protocolshttps://www.netdata.cloud/integrations/data-collection/networking/windows-network-protocols/Sat, 22 Aug 2026 00:07:12 +0000https://www.netdata.cloud/integrations/data-collection/networking/windows-network-protocols/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Amazon Linuxhttps://www.netdata.cloud/integrations/deploy/operating-systems/amazon-linux/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/deploy/operating-systems/amazon-linux/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->CentOShttps://www.netdata.cloud/integrations/deploy/operating-systems/centos/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/deploy/operating-systems/centos/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ciscohttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco 3850https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-3850/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-3850/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco Access Pointhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-access-point/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-access-point/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco ASAhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-asa/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-asa/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco ASRhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-asr/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-asr/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco Catalysthttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-catalyst/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-catalyst/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco Catalyst WLChttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-catalyst-wlc/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-catalyst-wlc/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco Csr1000Vhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-csr1000v/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-csr1000v/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco ICMhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-icm/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-icm/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco ISRhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-isr/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-isr/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco ISR 4431https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-isr-4431/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-isr-4431/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco Load Balancerhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-load-balancer/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-load-balancer/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco NCShttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-ncs/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-ncs/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco Nexushttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-nexus/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-nexus/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco SBhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-sb/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-sb/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco UC Virtual Machinehttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-uc-virtual-machine/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-uc-virtual-machine/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco WAN Optimizerhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-wan-optimizer/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-wan-optimizer/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ClickHousehttps://www.netdata.cloud/integrations/data-collection/databases/clickhouse/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/data-collection/databases/clickhouse/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Microsoft SQL Serverhttps://www.netdata.cloud/integrations/data-collection/databases/microsoft-sql-server/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/data-collection/databases/microsoft-sql-server/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Red Hat Enterprise Linuxhttps://www.netdata.cloud/integrations/deploy/operating-systems/red-hat-enterprise-linux/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/deploy/operating-systems/red-hat-enterprise-linux/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SNMP deviceshttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/snmp-devices/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/snmp-devices/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ubuntuhttps://www.netdata.cloud/integrations/deploy/operating-systems/ubuntu/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/deploy/operating-systems/ubuntu/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Windowshttps://www.netdata.cloud/integrations/deploy/operating-systems/windows/Fri, 21 Aug 2026 00:07:50 +0000https://www.netdata.cloud/integrations/deploy/operating-systems/windows/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Chart Annotations: Pin the Deploy, the Incident, or the Config Change Right on the Charthttps://www.netdata.cloud/blog/chart-annotations/Mon, 17 Aug 2026 00:00:00 +0000https://www.netdata.cloud/blog/chart-annotations/<p>A chart shows you that CPU jumped at 15:57. It doesn&rsquo;t show you that a deploy went out at 15:56. Chart annotations let you pin a note to the exact moment on a chart, and it stays there for everyone in your Space, permanently, the next time anyone looks at that chart.</p> <!--truncate--> <h2 id="pin-a-note-to-a-moment">Pin a note to a moment</h2> <p>Deployments, incidents, config changes, maintenance windows: these events explain the shape of your metrics, but they usually live somewhere your dashboard can&rsquo;t see, like a deploy log, a ticket, or a Slack thread someone will eventually delete. Chart annotations put that context on the chart itself, so you don&rsquo;t have to cross-reference a separate system by hand.</p>2Wcom GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/2wcom-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/2wcom-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->2Wire Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/2wire-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/2wire-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->3Com SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/3com-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/3com-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->3Par Data SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/3par-data-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/3par-data-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->4Rf Communications Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/4rf-communications-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/4rf-communications-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->A10 Networks Previously Raksha Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/a10-networks-previously-raksha-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/a10-networks-previously-raksha-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->A10 Thunderhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/a10-thunder/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/a10-thunder/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Abb Power Protection S.A. SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/abb-power-protection-s.a.-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/abb-power-protection-s.a.-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ablerex Electronic Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ablerex-electronic-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ablerex-electronic-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Acc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/acc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/acc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Accedian Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/accedian-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/accedian-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Accelerated Concepts Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/accelerated-concepts-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/accelerated-concepts-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Access Pointshttps://www.netdata.cloud/integrations/data-collection/networking/access-points/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/access-points/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Accton Technology SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/accton-technology-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/accton-technology-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Accuenergy Canada Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/accuenergy-canada-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/accuenergy-canada-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Acer SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/acer-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/acer-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Acksys SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/acksys-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/acksys-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Acme Packet SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/acme-packet-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/acme-packet-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Actidata Company SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/actidata-company-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/actidata-company-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Active Directoryhttps://www.netdata.cloud/integrations/data-collection/applications/active-directory/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/applications/active-directory/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Actona Technologies Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/actona-technologies-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/actona-technologies-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Adaptec Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/adaptec-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/adaptec-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Adtran SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/adtran-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/adtran-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Adva AG Optical Networking SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/adva-ag-optical-networking-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/adva-ag-optical-networking-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Advanced Fibre Communications Afc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/advanced-fibre-communications-afc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/advanced-fibre-communications-afc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Advantech Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/advantech-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/advantech-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aerohive Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aerohive-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aerohive-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aethra SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aethra-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aethra-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Affirmed Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/affirmed-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/affirmed-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Agent SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/agent-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/agent-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Agere Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/agere-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/agere-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Agfeo GmbH Co KG SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/agfeo-gmbh-co-kg-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/agfeo-gmbh-co-kg-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aginode Germany GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aginode-germany-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aginode-germany-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Airespace Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/airespace-inc-formerly-black-storm-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/airespace-inc-formerly-black-storm-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Alaxala Networks Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/alaxala-networks-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/alaxala-networks-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Albal Ingenieros S A SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/albal-ingenieros-s-a-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/albal-ingenieros-s-a-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Albentia Systems S A SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/albentia-systems-s-a-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/albentia-systems-s-a-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Albis Technologies Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/albis-technologies-ltd-formerly-siemens-switzerland-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/albis-technologies-ltd-formerly-siemens-switzerland-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Alcatel Lucent Enterprise SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/alcatel-lucent-enterprise-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/alcatel-lucent-enterprise-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ale USA Inc Omniswitch SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ale-usa-inc-omniswitch-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ale-usa-inc-omniswitch-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Alebra Technologies Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/alebra-technologies-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/alebra-technologies-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Allaire Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/allaire-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/allaire-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Allied Telesis Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/allied-telesis-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/allied-telesis-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Allot Communications SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/allot-communications-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/allot-communications-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Alpine Optoelectronics Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/alpine-optoelectronics-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/alpine-optoelectronics-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Alteon Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/alteon-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/alteon-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Altergy Systems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/altergy-systems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/altergy-systems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Alvarion Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/alvarion-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/alvarion-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Amazon SNShttps://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/amazon-sns/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/amazon-sns/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->American Power Conversion Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/american-power-conversion-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/american-power-conversion-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Amperion Incorporated SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/amperion-incorporated-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/amperion-incorporated-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->An D Cz SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/an-d-cz-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/an-d-cz-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ancor Communications SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ancor-communications-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ancor-communications-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Andover Controls Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/andover-controls-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/andover-controls-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Anuesystems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/anuesystems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/anuesystems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aol Netscape Communications Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aol-netscape-communications-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aol-netscape-communications-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ap Nederland B.V. SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ap-nederland-b.v.-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ap-nederland-b.v.-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Apachehttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/apache/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/apache/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Apache Pulsarhttps://www.netdata.cloud/integrations/data-collection/databases/apache-pulsar/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/databases/apache-pulsar/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->APC PDUhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/apc-pdu/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/apc-pdu/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->APC UPS (SNMP device)https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/apc-ups/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/apc-ups/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aperto Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aperto-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aperto-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Apple Computer Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/apple-computer-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/apple-computer-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Applied Innovation Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/applied-innovation-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/applied-innovation-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->AppOpticshttps://www.netdata.cloud/integrations/exporters/appoptics/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/appoptics/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aptis Communications Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aptis-communications-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aptis-communications-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Arbor Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/arbor-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/arbor-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Areca Technology Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/areca-technology-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/areca-technology-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Argus Technologies SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/argus-technologies-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/argus-technologies-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aricent Communication Holdings Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aricent-communication-holdings-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aricent-communication-holdings-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Arista Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/arista-networks-inc-formerly-arastra-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/arista-networks-inc-formerly-arastra-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Armillaire Technologies SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/armillaire-technologies-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/armillaire-technologies-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ARP / IP Neighbor Topologyhttps://www.netdata.cloud/integrations/network-performance-monitoring/topologies/arp---ip-neighbor-topology/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/topologies/arp---ip-neighbor-topology/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Arris Interactive LLC SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/arris-interactive-llc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/arris-interactive-llc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Arrowpoint Communications Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/arrowpoint-communications-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/arrowpoint-communications-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Artel Video Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/artel-video-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/artel-video-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Artem Gmbhmichael Marsanu Catrinel Catrinescu SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/artem-gmbhmichael-marsanu-catrinel-catrinescu-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/artem-gmbhmichael-marsanu-catrinel-catrinescu-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aruba A Hewlett Packard Enterprise Company SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aruba-a-hewlett-packard-enterprise-company-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aruba-a-hewlett-packard-enterprise-company-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aruba CX Switchhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/aruba-cx-switch/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/aruba-cx-switch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Asante Technology SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/asante-technology-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/asante-technology-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ascend Communications Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ascend-communications-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ascend-communications-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ascom Sweden AB SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ascom-sweden-ab-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ascom-sweden-ab-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Asentria Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/asentria-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/asentria-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Asetek SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/asetek-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/asetek-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Askey Computer Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/askey-computer-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/askey-computer-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ASP.NEThttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/asp.net/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/asp.net/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Astaro AG SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/astaro-ag-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/astaro-ag-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->At T SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/at-t-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/at-t-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ateme SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ateme-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ateme-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aten International Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aten-international-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aten-international-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Atlas Computer Equipment Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/atlas-computer-equipment-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/atlas-computer-equipment-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Atm Forum SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/atm-forum-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/atm-forum-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Atmel Hellas S A N SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/atmel-hellas-s-a-n-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/atmel-hellas-s-a-n-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Atto Technology Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/atto-technology-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/atto-technology-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Audiocodes Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/audiocodes-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/audiocodes-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Auditec S.A. SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/auditec-s.a.-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/auditec-s.a.-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Auspex Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/auspex-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/auspex-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Austin Hughes Electronics Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/austin-hughes-electronics-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/austin-hughes-electronics-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Availant SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/availant-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/availant-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Avamar SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/avamar-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/avamar-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Avaya Communication SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/avaya-communication-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/avaya-communication-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aventail Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aventail-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aventail-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aviat Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aviat-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aviat-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Avici Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/avici-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/avici-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Avista Labs Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/avista-labs-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/avista-labs-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Avocent Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/avocent-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/avocent-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Avtech Software Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/avtech-software-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/avtech-software-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aware Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aware-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/aware-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->AWS Kinesishttps://www.netdata.cloud/integrations/exporters/aws-kinesis/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/aws-kinesis/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Axis Communications AB SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/axis-communications-ab-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/axis-communications-ab-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure API Managementhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-api-management/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-api-management/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure App Servicehttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-app-service/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-app-service/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Application Gatewayhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-application-gateway/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-application-gateway/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Application Insightshttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-application-insights/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-application-insights/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Cache for Redishttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-cache-for-redis/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-cache-for-redis/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Cognitive Serviceshttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-cognitive-services/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-cognitive-services/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Container Appshttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-container-apps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-container-apps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Container Instanceshttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-container-instances/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-container-instances/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Container Registryhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-container-registry/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-container-registry/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Cosmos DB Accounthttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-cosmos-db-account/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-cosmos-db-account/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Data Explorerhttps://www.netdata.cloud/integrations/exporters/azure-data-explorer/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/azure-data-explorer/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Data Explorer Clusterhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-data-explorer-cluster/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-data-explorer-cluster/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Data Factoryhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-data-factory/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-data-factory/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Event Grid Topichttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-event-grid-topic/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-event-grid-topic/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Event Hubhttps://www.netdata.cloud/integrations/exporters/azure-event-hub/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/azure-event-hub/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Event Hubs Namespacehttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-event-hubs-namespace/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-event-hubs-namespace/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure ExpressRoute Circuithttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-expressroute-circuit/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-expressroute-circuit/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure ExpressRoute Gatewayhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-expressroute-gateway/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-expressroute-gateway/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Firewallhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-firewall/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-firewall/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Front Doorhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-front-door/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-front-door/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Functionshttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-functions/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-functions/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure IoT Hubhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-iot-hub/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-iot-hub/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Key Vault (go.d.plugin azure_monitor)https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-key-vault/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-key-vault/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Kubernetes Service Clusterhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-kubernetes-service-cluster/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-kubernetes-service-cluster/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Load Balancerhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-load-balancer/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-load-balancer/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Log Analytics Workspacehttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-log-analytics-workspace/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-log-analytics-workspace/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Logic Apps Workflowhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-logic-apps-workflow/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-logic-apps-workflow/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Machine Learning Workspacehttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-machine-learning-workspace/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-machine-learning-workspace/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Monitorhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-monitor/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-monitor/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure MySQL Flexible Serverhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-mysql-flexible-server/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-mysql-flexible-server/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure NAT Gatewayhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-nat-gateway/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-nat-gateway/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure PostgreSQL Flexible Serverhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-postgresql-flexible-server/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-postgresql-flexible-server/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Service Bus Namespacehttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-service-bus-namespace/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-service-bus-namespace/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure SQL Databasehttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-sql-database/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-sql-database/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure SQL Elastic Poolhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-sql-elastic-pool/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-sql-elastic-pool/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure SQL Managed Instancehttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-sql-managed-instance/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-sql-managed-instance/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Storage Accounthttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-storage-account/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-storage-account/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Stream Analytics Jobhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-stream-analytics-job/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-stream-analytics-job/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Synapse Analytics Workspacehttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-synapse-analytics-workspace/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-synapse-analytics-workspace/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Virtual Machinehttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-virtual-machine/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-virtual-machine/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Virtual Machine Scale Sethttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-virtual-machine-scale-set/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-virtual-machine-scale-set/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure VPN Gatewayhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-vpn-gateway/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/azure-vpn-gateway/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->B A T M Advance Technologies SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/b-a-t-m-advance-technologies-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/b-a-t-m-advance-technologies-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bachmann GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bachmann-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bachmann-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bancomm SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bancomm-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bancomm-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Barco Control Rooms SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/barco-control-rooms-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/barco-control-rooms-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Barix AG SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/barix-ag-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/barix-ag-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Barracuda Networks AG SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/barracuda-networks-ag-previous-was-phion-information-technologies-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/barracuda-networks-ag-previous-was-phion-information-technologies-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Barracuda Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/barracuda-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/barracuda-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bay Technical Associates SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bay-technical-associates-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bay-technical-associates-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bdt GmbH Co KG SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bdt-gmbh-co-kg-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bdt-gmbh-co-kg-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Beijing Raisecom Scientific Technology Development Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/beijing-raisecom-scientific-technology-development-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/beijing-raisecom-scientific-technology-development-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bekarts International SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bekarts-international-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bekarts-international-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bellcore SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bellcore-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bellcore-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Benu Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/benu-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/benu-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Beronet GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/beronet-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/beronet-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Best Power A Division Of General Signal Power Systems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/best-power-a-division-of-general-signal-power-systems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/best-power-a-division-of-general-signal-power-systems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Better Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/better-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/better-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->BGP Peering Topologyhttps://www.netdata.cloud/integrations/network-performance-monitoring/topologies/bgp-peering-topology/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/topologies/bgp-peering-topology/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bharti Telesoft International Pvt Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bharti-telesoft-international-pvt-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bharti-telesoft-international-pvt-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bintec Communications GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bintec-communications-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bintec-communications-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bird Technologies SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bird-technologies-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bird-technologies-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bke A S SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bke-a-s-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bke-a-s-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Blade Network Technologies Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/blade-network-technologies-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/blade-network-technologies-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Blue Coat Systems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/blue-coat-systems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/blue-coat-systems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bluecat Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bluecat-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bluecat-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bluefloodhttps://www.netdata.cloud/integrations/exporters/blueflood/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/blueflood/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bluesocket Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bluesocket-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bluesocket-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bmc Software SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bmc-software-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bmc-software-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Borderware Technologies Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/borderware-technologies-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/borderware-technologies-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Brand Communications Limited SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/brand-communications-limited-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/brand-communications-limited-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bridgewave Communications SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bridgewave-communications-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bridgewave-communications-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Broadband Access Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/broadband-access-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/broadband-access-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Broadcom Limited SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/broadcom-limited-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/broadcom-limited-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Broadsoft Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/broadsoft-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/broadsoft-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Brocade Communication Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/brocade-communication-systems-inc-formerly-foundry-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/brocade-communication-systems-inc-formerly-foundry-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Brocade Communications Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/brocade-communications-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/brocade-communications-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Brocade Communications Systems Inc SNMP Traps (variant 1)https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/brocade-communications-systems-inc-formerly-mcdata-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/brocade-communications-systems-inc-formerly-mcdata-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Brocade Communications Systems Inc SNMP Traps (variant 2)https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/brocade-communications-systems-inc-formerly-nuview-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/brocade-communications-systems-inc-formerly-nuview-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bti Photonic Systems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bti-photonic-systems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bti-photonic-systems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bytesphere LLC SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bytesphere-llc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/bytesphere-llc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->C C Power Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/c-c-power-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/c-c-power-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cable Television Laboratories Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cable-television-laboratories-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cable-television-laboratories-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cacheflow Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cacheflow-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cacheflow-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cacti SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cacti-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cacti-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cadant Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cadant-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cadant-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Calix Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/calix-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/calix-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cambium Networks Limited SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cambium-networks-limited-formerly-pipinghot-networks-limited-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cambium-networks-limited-formerly-pipinghot-networks-limited-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Carel SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/carel-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/carel-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cascade Communications Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cascade-communications-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cascade-communications-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Castle Rock Computing SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/castle-rock-computing-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/castle-rock-computing-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cato Networks Topologyhttps://www.netdata.cloud/integrations/network-performance-monitoring/topologies/cato-networks-topology/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/topologies/cato-networks-topology/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->CDP Topologyhttps://www.netdata.cloud/integrations/network-performance-monitoring/topologies/cdp-topology/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/topologies/cdp-topology/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ce T SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ce-t-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ce-t-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Centec Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/centec-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/centec-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Centillion Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/centillion-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/centillion-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Centrum Communications Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/centrum-communications-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/centrum-communications-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cerent Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cerent-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cerent-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Chateau Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/chateau-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/chateau-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Check Point Software Technologies Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/check-point-software-technologies-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/check-point-software-technologies-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cherokee International Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cherokee-international-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cherokee-international-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cheyenne Software SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cheyenne-software-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cheyenne-software-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Chippcom SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/chippcom-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/chippcom-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Chloride SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/chloride-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/chloride-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Chromatis Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/chromatis-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/chromatis-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Chronixhttps://www.netdata.cloud/integrations/exporters/chronix/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/chronix/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ciena Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ciena-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ciena-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cirpack SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cirpack-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cirpack-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco UCShttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-ucs/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-ucs/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ciscosystems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ciscosystems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ciscosystems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Citrix Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/citrix-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/citrix-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->City Com B.V. SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/city-com-b.v.-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/city-com-b.v.-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Clarent Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/clarent-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/clarent-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Clavister AB SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/clavister-ab-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/clavister-ab-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Clickarrray Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/clickarrray-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/clickarrray-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cloudgenix SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cloudgenix-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cloudgenix-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->CockroachDBhttps://www.netdata.cloud/integrations/data-collection/databases/cockroachdb/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/databases/cockroachdb/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Codan Limited SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/codan-limited-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/codan-limited-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Codex SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/codex-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/codex-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Codima Technologies Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/codima-technologies-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/codima-technologies-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cohesity Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cohesity-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cohesity-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Colubris Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/colubris-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/colubris-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Com21 SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/com21-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/com21-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Comap A S SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/comap-a-s-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/comap-a-s-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Comet System S R O SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/comet-system-s-r-o-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/comet-system-s-r-o-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Commend International GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/commend-international-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/commend-international-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Communication Company Nari Group Corporation Information Technology SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/communication-company-nari-group-corporation-information-technology-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/communication-company-nari-group-corporation-information-technology-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Compaq SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/compaq-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/compaq-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Compellent Technologies SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/compellent-technologies-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/compellent-technologies-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Compex Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/compex-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/compex-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Computer Associates International SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/computer-associates-international-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/computer-associates-international-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Computer Network Technology SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/computer-network-technology-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/computer-network-technology-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Comtech Efdata Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/comtech-efdata-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/comtech-efdata-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Concord Communications SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/concord-communications-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/concord-communications-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Confmon Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/confmon-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/confmon-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Connection Technology Systems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/connection-technology-systems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/connection-technology-systems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Conteg SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/conteg-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/conteg-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Convertronic GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/convertronic-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/convertronic-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cooler Master Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cooler-master-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cooler-master-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Copper Mountain Communications Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/copper-mountain-communications-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/copper-mountain-communications-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->CoreDNShttps://www.netdata.cloud/integrations/data-collection/networking/coredns/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/coredns/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Coriolis Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/coriolis-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/coriolis-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cortexhttps://www.netdata.cloud/integrations/exporters/cortex/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/cortex/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cosine Communications SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cosine-communications-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cosine-communications-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Couchbasehttps://www.netdata.cloud/integrations/data-collection/databases/couchbase/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/databases/couchbase/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->CouchDBhttps://www.netdata.cloud/integrations/data-collection/databases/couchdb/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/databases/couchdb/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->CrateDBhttps://www.netdata.cloud/integrations/exporters/cratedb/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/cratedb/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cray Communications A S SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cray-communications-a-s-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cray-communications-a-s-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cray SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cray-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cray-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Croix Rouge Francaise SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/croix-rouge-francaise-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/croix-rouge-francaise-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Crossbeam Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/crossbeam-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/crossbeam-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ctc Union Technologies Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ctc-union-technologies-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ctc-union-technologies-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cube Optics AG SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cube-optics-ag-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cube-optics-ag-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cumulus Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cumulus-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cumulus-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cxr SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cxr-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cxr-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cyan SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cyan-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cyan-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cyber Ark SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cyber-ark-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cyber-ark-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cyber Power System Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cyber-power-system-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cyber-power-system-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cyberguard Corporationdavid Rhein SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cyberguard-corporationdavid-rhein-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/cyberguard-corporationdavid-rhein-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->D Link Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/d-link-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/d-link-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dantel Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dantel-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dantel-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dantherm Cooling A S SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dantherm-cooling-a-s-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dantherm-cooling-a-s-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Danware Data A S SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/danware-data-a-s-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/danware-data-a-s-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dasan Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dasan-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dasan-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Data Domain Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/data-domain-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/data-domain-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Datadirect Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/datadirect-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/datadirect-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Datalogic S P A SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/datalogic-s-p-a-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/datalogic-s-p-a-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Datapower Technology Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/datapower-technology-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/datapower-technology-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dataprobe Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dataprobe-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dataprobe-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Debian SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/debian-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/debian-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dec SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dec-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dec-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Deep Sea Electronics PLC SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/deep-sea-electronics-plc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/deep-sea-electronics-plc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Del Mar Solutions Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/del-mar-solutions-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/del-mar-solutions-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Deliberant SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/deliberant-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/deliberant-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dell Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dell-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dell-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Delta Electronics Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/delta-electronics-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/delta-electronics-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Delta Electronics Switzerland AG SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/delta-electronics-switzerland-ag-formerly-delta-energy-systems-sweden-ab-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/delta-electronics-switzerland-ag-formerly-delta-energy-systems-sweden-ab-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Deltanet AG SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/deltanet-ag-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/deltanet-ag-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Designer Systems Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/designer-systems-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/designer-systems-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->dev.cpu.0.freqhttps://www.netdata.cloud/integrations/data-collection/operating-systems/dev.cpu.0.freq/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/dev.cpu.0.freq/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->dev.cpu.temperaturehttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/dev.cpu.temperature/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/dev.cpu.temperature/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Deva Broadcast Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/deva-broadcast-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/deva-broadcast-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dialogic Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dialogic-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dialogic-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Didactum Security GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/didactum-security-gmbh-formerly-didactum-ltd-deutschland-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/didactum-security-gmbh-formerly-didactum-ltd-deutschland-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Digipower Manufacturing Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/digipower-manufacturing-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/digipower-manufacturing-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Digital China Shanghai Networks Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/digital-china-shanghai-networks-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/digital-china-shanghai-networks-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Digital Link SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/digital-link-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/digital-link-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Digital Video Broadcasting Dvb SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/digital-video-broadcasting-dvb-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/digital-video-broadcasting-dvb-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Discord (Cloud notifications)https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/discord/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/discord/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dismuntel S A L SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dismuntel-s-a-l-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dismuntel-s-a-l-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Distributed Management Task Force Dmtf SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/distributed-management-task-force-dmtf-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/distributed-management-task-force-dmtf-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Distributed Processing Technology SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/distributed-processing-technology-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/distributed-processing-technology-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->DNSdisthttps://www.netdata.cloud/integrations/data-collection/networking/dnsdist/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/dnsdist/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dnsmasqhttps://www.netdata.cloud/integrations/data-collection/networking/dnsmasq/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/dnsmasq/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dnsmasq DHCPhttps://www.netdata.cloud/integrations/data-collection/networking/dnsmasq-dhcp/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/dnsmasq-dhcp/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dps Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dps-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dps-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dragonwave SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dragonwave-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dragonwave-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dynatech Communications SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dynatech-communications-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/dynatech-communications-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->E Dynamics Org SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/e-dynamics-org-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/e-dynamics-org-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->E T A Elektrotechnische Apparate GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/e-t-a-elektrotechnische-apparate-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/e-t-a-elektrotechnische-apparate-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Eastern Research Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/eastern-research-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/eastern-research-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Eaton Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/eaton-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/eaton-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Eaton Epduhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/eaton-epdu/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/eaton-epdu/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Eaton UPShttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/eaton-ups/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/eaton-ups/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->eBPF Diskhttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ebpf-disk/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ebpf-disk/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->eBPF DNShttps://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-dns/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-dns/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->eBPF Hardirqhttps://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-hardirq/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-hardirq/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->eBPF MDflushhttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ebpf-mdflush/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ebpf-mdflush/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->eBPF Mounthttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ebpf-mount/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ebpf-mount/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->eBPF OOMkillhttps://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-oomkill/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-oomkill/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->eBPF Processhttps://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-process/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-process/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->eBPF Processeshttps://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-processes/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-processes/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->eBPF Sockethttps://www.netdata.cloud/integrations/data-collection/networking/ebpf-socket/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/ebpf-socket/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->eBPF SoftIRQhttps://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-softirq/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-softirq/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->eBPF SWAPhttps://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-swap/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-swap/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->eBPF VFShttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ebpf-vfs/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ebpf-vfs/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ecreso SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ecreso-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ecreso-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Edial Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/edial-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/edial-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Egenera Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/egenera-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/egenera-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Egnite GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/egnite-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/egnite-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Eicon SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/eicon-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/eicon-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ekinops Sas SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ekinops-sas-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ekinops-sas-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ElasticSearch (Exporter)https://www.netdata.cloud/integrations/exporters/elasticsearch/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/elasticsearch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Electroline Equipment Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/electroline-equipment-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/electroline-equipment-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Elfiq Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/elfiq-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/elfiq-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Elitecore Technologies Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/elitecore-technologies-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/elitecore-technologies-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Eltek Energy AS SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/eltek-energy-as-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/eltek-energy-as-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Eltek Valere Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/eltek-valere-inc-formerly-valere-power-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/eltek-valere-inc-formerly-valere-power-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Eltex Enterprise Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/eltex-enterprise-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/eltex-enterprise-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Emc Clariion Advanced Storage Solutions SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/emc-clariion-advanced-storage-solutions-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/emc-clariion-advanced-storage-solutions-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Emc Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/emc-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/emc-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Emc Data General Division SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/emc-data-general-division-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/emc-data-general-division-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Empire Technologies Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/empire-technologies-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/empire-technologies-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Endace Technology SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/endace-technology-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/endace-technology-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Endrun Technologies LLC SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/endrun-technologies-llc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/endrun-technologies-llc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Engenio Information Technologies Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/engenio-information-technologies-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/engenio-information-technologies-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Enlogic Systems LLC SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/enlogic-systems-llc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/enlogic-systems-llc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Enterasys Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/enterasys-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/enterasys-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Enterasys Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/enterasys-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/enterasys-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Enterprise 1004849 SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/enterprise-1004849-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/enterprise-1004849-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Entropyhttps://www.netdata.cloud/integrations/data-collection/operating-systems/entropy/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/entropy/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Epicenter Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/epicenter-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/epicenter-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Equallogic SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/equallogic-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/equallogic-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Equinox Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/equinox-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/equinox-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Equipe Communications Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/equipe-communications-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/equipe-communications-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Era A S SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/era-a-s-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/era-a-s-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ericsson AB Packet Core Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ericsson-ab-packet-core-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ericsson-ab-packet-core-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ericsson AB SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ericsson-ab-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ericsson-ab-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ericsson Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ericsson-inc-formerly-redback-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ericsson-inc-formerly-redback-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Essential Communications SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/essential-communications-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/essential-communications-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Etherwan Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/etherwan-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/etherwan-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Eurologic Systems Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/eurologic-systems-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/eurologic-systems-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Exablaze SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/exablaze-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/exablaze-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Exabyte Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/exabyte-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/exabyte-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Exagridhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/exagrid/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/exagrid/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Exalt Communications SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/exalt-communications-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/exalt-communications-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Exanet SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/exanet-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/exanet-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Exceliance SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/exceliance-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/exceliance-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Exinda Networks Pty Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/exinda-networks-pty-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/exinda-networks-pty-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Expand Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/expand-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/expand-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Extended Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/extended-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/extended-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Extrahop Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/extrahop-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/extrahop-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Extreme Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/extreme-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/extreme-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Extricomltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/extricomltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/extricomltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->F5 Labs Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/f5-labs-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/f5-labs-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->F5 Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/f5-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/f5-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->FDB / MAC Forwarding Topologyhttps://www.netdata.cloud/integrations/network-performance-monitoring/topologies/fdb---mac-forwarding-topology/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/topologies/fdb---mac-forwarding-topology/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fial Computer Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fial-computer-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fial-computer-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fiberhome Telecommunication Technologies Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fiberhome-telecommunication-technologies-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fiberhome-telecommunication-technologies-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fibernet International SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fibernet-international-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fibernet-international-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fibrolan SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fibrolan-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fibrolan-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fibronics SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fibronics-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fibronics-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fireeye Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fireeye-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fireeye-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Flarion Technologies SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/flarion-technologies-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/flarion-technologies-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fluentdhttps://www.netdata.cloud/integrations/data-collection/applications/fluentd/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/applications/fluentd/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Force10 Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/force10-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/force10-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Forcepoint LLC SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/forcepoint-llc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/forcepoint-llc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fore Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fore-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fore-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fort Telecom SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fort-telecom-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fort-telecom-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Forte Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/forte-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/forte-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fortinet Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fortinet-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fortinet-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fraunhofer Fokus SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fraunhofer-fokus-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fraunhofer-fokus-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->FreeRADIUShttps://www.netdata.cloud/integrations/data-collection/applications/freeradius/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/applications/freeradius/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fs Com Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fs-com-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fs-com-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fujitsu Access Limited SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fujitsu-access-limited-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fujitsu-access-limited-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fujitsu Germany GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fujitsu-germany-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fujitsu-germany-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fujitsu Limited SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fujitsu-limited-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fujitsu-limited-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fujitsu Network Communications Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fujitsu-network-communications-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fujitsu-network-communications-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fusionio SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fusionio-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/fusionio-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Future Software SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/future-software-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/future-software-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Gadzoox Microsystems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/gadzoox-microsystems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/gadzoox-microsystems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Gamatronic Electronic Industries Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/gamatronic-electronic-industries-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/gamatronic-electronic-industries-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Gandalf SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/gandalf-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/gandalf-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Garderos GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/garderos-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/garderos-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Gcom Technologies Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/gcom-technologies-co-ltd-formerly-greennet-technology-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/gcom-technologies-co-ltd-formerly-greennet-technology-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Gemtek Systems Holding B.V. SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/gemtek-systems-holding-b.v.-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/gemtek-systems-holding-b.v.-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->General Datacomm Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/general-datacomm-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/general-datacomm-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->General Instrument SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/general-instrument-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/general-instrument-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Generex Systems GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/generex-systems-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/generex-systems-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Genie Network Resource Management SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/genie-network-resource-management-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/genie-network-resource-management-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->getifaddrshttps://www.netdata.cloud/integrations/data-collection/networking/getifaddrs/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/getifaddrs/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->getmntinfohttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/getmntinfo/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/getmntinfo/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Gigamon Systems LLC SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/gigamon-systems-llc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/gigamon-systems-llc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Giganet Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/giganet-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/giganet-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Gnocchihttps://www.netdata.cloud/integrations/exporters/gnocchi/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/gnocchi/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Go-ethereumhttps://www.netdata.cloud/integrations/data-collection/applications/go-ethereum/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/applications/go-ethereum/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Google BigQueryhttps://www.netdata.cloud/integrations/exporters/google-bigquery/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/google-bigquery/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Google Cloud Pub Subhttps://www.netdata.cloud/integrations/exporters/google-cloud-pub-sub/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/google-cloud-pub-sub/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Grand Junction Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/grand-junction-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/grand-junction-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Grandstream Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/grandstream-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/grandstream-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Graphitehttps://www.netdata.cloud/integrations/exporters/graphite/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/graphite/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->GreptimeDBhttps://www.netdata.cloud/integrations/exporters/greptimedb/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/greptimedb/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Group Emailhttps://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/group-email/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/group-email/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Gude Analog Und Digitalsysteme GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/gude-analog-und-digitalsysteme-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/gude-analog-und-digitalsysteme-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Gw Technologies Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/gw-technologies-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/gw-technologies-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->H3C SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/h3c-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/h3c-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Hadoop Distributed File System (HDFS)https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/hadoop-distributed-file-system-hdfs/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/hadoop-distributed-file-system-hdfs/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Halcyon Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/halcyon-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/halcyon-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Harmonic Lightwaves SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/harmonic-lightwaves-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/harmonic-lightwaves-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->HDD temperaturehttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/hdd-temperature/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/hdd-temperature/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Hewlett Packard Enterprise SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/hewlett-packard-enterprise-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/hewlett-packard-enterprise-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Hewlett Packard SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/hewlett-packard-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/hewlett-packard-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Hitachi Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/hitachi-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/hitachi-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->HP ILOhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/hp-ilo/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/hp-ilo/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->HP Ilo4https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/hp-ilo4/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/hp-ilo4/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->HPE MSAhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/hpe-msa/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/hpe-msa/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->HTTPDhttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/httpd/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/httpd/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Huawei Symantec Technologies Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/huawei-symantec-technologies-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/huawei-symantec-technologies-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Huawei Technology Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/huawei-technology-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/huawei-technology-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Huber Suhner Bktel GmbH Hfc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/huber-suhner-bktel-gmbh-hfc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/huber-suhner-bktel-gmbh-hfc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Hw Group S R O SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/hw-group-s-r-o-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/hw-group-s-r-o-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->hw.intrcnthttps://www.netdata.cloud/integrations/data-collection/operating-systems/hw.intrcnt/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/hw.intrcnt/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Hyper-Vhttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/hyper-v/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/hyper-v/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Hypercom Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/hypercom-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/hypercom-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IBM DB2https://www.netdata.cloud/integrations/data-collection/databases/ibm-db2/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/databases/ibm-db2/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ibm Eserver X SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ibm-eserver-x-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ibm-eserver-x-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ibm Https W3 Ibm Com Standards SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ibm-https-w3-ibm-com-standards-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ibm-https-w3-ibm-com-standards-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IBM WebSphere PMIhttps://www.netdata.cloud/integrations/data-collection/applications/ibm-websphere-pmi/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/applications/ibm-websphere-pmi/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ibrix Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ibrix-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ibrix-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Icecasthttps://www.netdata.cloud/integrations/data-collection/applications/icecast/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/applications/icecast/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Idirect SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/idirect-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/idirect-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Idle OS Jitterhttps://www.netdata.cloud/integrations/data-collection/synthetic-testing/idle-os-jitter/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/synthetic-testing/idle-os-jitter/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IDRAChttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/idrac/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/idrac/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ieee 802 SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ieee-802-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ieee-802-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ieee Lldp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ieee-lldp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ieee-lldp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ilert (Cloud notifications)https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/ilert/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/ilert/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Image Processing Techniques Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/image-processing-techniques-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/image-processing-techniques-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Image Project Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/image-project-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/image-project-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Imv Victron B.V. SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/imv-victron-b.v.-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/imv-victron-b.v.-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Inca Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/inca-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/inca-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Incognito Software Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/incognito-software-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/incognito-software-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Independence Technologies Inc Iti SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/independence-technologies-inc-iti-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/independence-technologies-inc-iti-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Infinet LLC SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/infinet-llc-formerly-aqua-project-group-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/infinet-llc-formerly-aqua-project-group-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->InfiniBandhttps://www.netdata.cloud/integrations/data-collection/networking/infiniband/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/infiniband/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Inflection Systems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/inflection-systems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/inflection-systems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Infoblox Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/infoblox-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/infoblox-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Infortrend Technology Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/infortrend-technology-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/infortrend-technology-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Infosim SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/infosim-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/infosim-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Infratec Plus GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/infratec-plus-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/infratec-plus-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ingrasys SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ingrasys-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ingrasys-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Inktomi Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/inktomi-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/inktomi-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Innominate Security Technologies AG SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/innominate-security-technologies-ag-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/innominate-security-technologies-ag-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Innovaphone GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/innovaphone-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/innovaphone-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Innovative Circuit Technology Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/innovative-circuit-technology-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/innovative-circuit-technology-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Inoc Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/inoc-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/inoc-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Inova Dc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/inova-dc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/inova-dc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Inovonics Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/inovonics-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/inovonics-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Intel Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/intel-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/intel-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Intersystems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/intersystems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/intersystems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Invidi Technologies SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/invidi-technologies-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/invidi-technologies-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ip Infusion Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ip-infusion-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ip-infusion-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ipf Technology Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ipf-technology-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ipf-technology-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ipfwhttps://www.netdata.cloud/integrations/data-collection/networking/ipfw/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/ipfw/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IPv6 Socket Statisticshttps://www.netdata.cloud/integrations/data-collection/networking/ipv6-socket-statistics/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/ipv6-socket-statistics/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IRONdbhttps://www.netdata.cloud/integrations/exporters/irondb/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/irondb/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ironport Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ironport-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ironport-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Isilonhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/isilon/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/isilon/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Isilon Ststems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/isilon-ststems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/isilon-ststems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->It Watchdogs Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/it-watchdogs-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/it-watchdogs-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ixsystems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ixsystems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ixsystems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Jacarta Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/jacarta-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/jacarta-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Jacobs University Bremen SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/jacobs-university-bremen-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/jacobs-university-bremen-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Jacques Technologies SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/jacques-technologies-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/jacques-technologies-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Janitza Electronics GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/janitza-electronics-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/janitza-electronics-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Jds Uniphase Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/jds-uniphase-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/jds-uniphase-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Johnson Controls Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/johnson-controls-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/johnson-controls-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->JSONhttps://www.netdata.cloud/integrations/exporters/json/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/json/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Juniper Networks Funk Software SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/juniper-networks-funk-software-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/juniper-networks-funk-software-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Juniper Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/juniper-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/juniper-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Juniper Networks Unisphere SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/juniper-networks-unisphere-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/juniper-networks-unisphere-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->K2Net SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/k2net-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/k2net-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kafka (Exporter)https://www.netdata.cloud/integrations/exporters/kafka/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/kafka/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->KairosDBhttps://www.netdata.cloud/integrations/exporters/kairosdb/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/kairosdb/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kashya SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/kashya-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/kashya-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kaspersky Lab Zao SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/kaspersky-lab-zao-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/kaspersky-lab-zao-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Katron Technologies Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/katron-technologies-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/katron-technologies-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kcp Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/kcp-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/kcp-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kentix GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/kentix-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/kentix-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kentrox SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/kentrox-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/kentrox-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->kern.cp_timehttps://www.netdata.cloud/integrations/data-collection/operating-systems/kern.cp_time/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/kern.cp_time/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->kern.ipc.msqhttps://www.netdata.cloud/integrations/data-collection/operating-systems/kern.ipc.msq/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/kern.ipc.msq/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->kern.ipc.semhttps://www.netdata.cloud/integrations/data-collection/operating-systems/kern.ipc.sem/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/kern.ipc.sem/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->kern.ipc.shmhttps://www.netdata.cloud/integrations/data-collection/operating-systems/kern.ipc.shm/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/kern.ipc.shm/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kernel Same-Page Merginghttps://www.netdata.cloud/integrations/data-collection/operating-systems/kernel-same-page-merging/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/kernel-same-page-merging/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kevin Ether Boulain SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/kevin-ether-boulain-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/kevin-ether-boulain-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Knuerr AG SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/knuerr-ag-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/knuerr-ag-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kubelethttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/kubelet/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/kubelet/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kubeproxyhttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/kubeproxy/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/kubeproxy/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kubernetes Containershttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/kubernetes-containers/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/containers-and-vms/kubernetes-containers/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kyocera Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/kyocera-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/kyocera-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Lanart Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lanart-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lanart-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Lancast Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lancast-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lancast-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Lancity Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lancity-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lancity-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Lancom Systems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lancom-systems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lancom-systems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Lanex Sp Z O O SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lanex-sp-z-o-o-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lanex-sp-z-o-o-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Lannair Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lannair-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lannair-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Lannet Company SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lannet-company-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lannet-company-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Lantronix SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lantronix-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lantronix-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Last Mile Gear SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/last-mile-gear-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/last-mile-gear-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Latitude Communications SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/latitude-communications-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/latitude-communications-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Laurel Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/laurel-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/laurel-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Lefthand Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lefthand-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lefthand-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Lenovo Enterprise Business Group SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lenovo-enterprise-business-group-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lenovo-enterprise-business-group-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Lenovoemc Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lenovoemc-ltd-formerly-iomega-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lenovoemc-ltd-formerly-iomega-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Lexmark International SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lexmark-international-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lexmark-international-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Librenms SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/librenms-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/librenms-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ligowave SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ligowave-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ligowave-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Linksys SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/linksys-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/linksys-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Linux Audit Subsystemhttps://www.netdata.cloud/integrations/data-collection/operating-systems/linux-audit-subsystem/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/linux-audit-subsystem/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Linux Hardware Sensors (libsensors)https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/linux-hardware-sensors-libsensors/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/linux-hardware-sensors-libsensors/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Livingston Enterprises Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/livingston-enterprises-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/livingston-enterprises-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->LLDP Topologyhttps://www.netdata.cloud/integrations/network-performance-monitoring/topologies/lldp-topology/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/topologies/lldp-topology/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Logstashhttps://www.netdata.cloud/integrations/data-collection/applications/logstash/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/applications/logstash/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Loop Telecommunication International Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/loop-telecommunication-international-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/loop-telecommunication-international-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Loral Wdl SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/loral-wdl-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/loral-wdl-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Lotus Development Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lotus-development-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lotus-development-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Lsi Logic SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lsi-logic-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lsi-logic-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Lucent Technologies SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lucent-technologies-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/lucent-technologies-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Luminous Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/luminous-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/luminous-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Luxn Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/luxn-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/luxn-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->M3DBhttps://www.netdata.cloud/integrations/exporters/m3db/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/m3db/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Madge Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/madge-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/madge-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Maipu Electric Industrial Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/maipu-electric-industrial-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/maipu-electric-industrial-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Marc Hirsch SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/marc-hirsch-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/marc-hirsch-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->MariaDBhttps://www.netdata.cloud/integrations/data-collection/databases/mariadb/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/databases/mariadb/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mattermosthttps://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/mattermost/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/mattermost/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mcafee Associates Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mcafee-associates-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mcafee-associates-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mcafee Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mcafee-inc-formerly-network-associates-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mcafee-inc-formerly-network-associates-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mcafee SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mcafee-formerly-secure-computing-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mcafee-formerly-secure-computing-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Media5 Corporation M5 Technologies SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/media5-corporation-m5-technologies-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/media5-corporation-m5-technologies-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mega System Technologies Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mega-system-technologies-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mega-system-technologies-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Megapac SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/megapac-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/megapac-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Meinberg SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/meinberg-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/meinberg-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Melco Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/melco-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/melco-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mellanox Technologies Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mellanox-technologies-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mellanox-technologies-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Memory modules (DIMMs)https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/memory-modules-dimms/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/memory-modules-dimms/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Memory Statisticshttps://www.netdata.cloud/integrations/data-collection/operating-systems/memory-statistics/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/memory-statistics/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Memotec Communications SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/memotec-communications-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/memotec-communications-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Memotec Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/memotec-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/memotec-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Meraki Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/meraki-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/meraki-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Merlin Gerin SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/merlin-gerin-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/merlin-gerin-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Meru Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/meru-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/meru-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Metaswitch Networks Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/metaswitch-networks-ltd-formerly-data-connection-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/metaswitch-networks-ltd-formerly-data-connection-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->MetricFirehttps://www.netdata.cloud/integrations/exporters/metricfire/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/metricfire/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Metro Ethernet Forum SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/metro-ethernet-forum-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/metro-ethernet-forum-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Micom Communication Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/micom-communication-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/micom-communication-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Microchip Technology Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/microchip-technology-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/microchip-technology-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Micromuse Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/micromuse-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/micromuse-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Microsens GmbH Co KG SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/microsens-gmbh-co-kg-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/microsens-gmbh-co-kg-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Microsoft SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/microsoft-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/microsoft-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Microsoft Teams (Cloud notifications)https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/microsoft-teams/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/microsoft-teams/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Microwave Data Systems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/microwave-data-systems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/microwave-data-systems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Microwave Networks Incorporated SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/microwave-networks-incorporated-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/microwave-networks-incorporated-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mikom GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mikom-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mikom-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mikrotik SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mikrotik-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mikrotik-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Milestone Systems A S SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/milestone-systems-a-s-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/milestone-systems-a-s-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mimosa Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mimosa-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mimosa-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mission Critical Software Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mission-critical-software-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mission-critical-software-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mitel Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mitel-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mitel-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mitsubishi Electric Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mitsubishi-electric-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mitsubishi-electric-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Moca Multimedia Over Coax Alliance SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/moca-multimedia-over-coax-alliance-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/moca-multimedia-over-coax-alliance-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Monet Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/monet-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/monet-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->MongoDB (go.d.plugin mongodb)https://www.netdata.cloud/integrations/data-collection/databases/mongodb/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/databases/mongodb/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Monnit Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/monnit-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/monnit-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Moser Baer AG SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/moser-baer-ag-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/moser-baer-ag-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Motorola SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/motorola-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/motorola-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Moxa Technologies Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/moxa-technologies-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/moxa-technologies-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mpb Communications Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mpb-communications-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mpb-communications-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mrv Communications In Reach Product Division SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mrv-communications-in-reach-product-division-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mrv-communications-in-reach-product-division-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->MS Exchangehttps://www.netdata.cloud/integrations/data-collection/applications/ms-exchange/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/applications/ms-exchange/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mts Allstream Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mts-allstream-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mts-allstream-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mylex Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mylex-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mylex-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->MySQLhttps://www.netdata.cloud/integrations/data-collection/databases/mysql/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/databases/mysql/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mystrotv SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mystrotv-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/mystrotv-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nag LLC SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nag-llc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nag-llc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nagios SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nagios-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nagios-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nasuni Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nasuni-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nasuni-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nateks Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nateks-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nateks-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->National Standardization Committee Of Radio Television SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/national-standardization-committee-of-radio-television-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/national-standardization-committee-of-radio-television-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nbase Switch Communication SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nbase-switch-communication-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nbase-switch-communication-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nec Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nec-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nec-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Neoteris Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/neoteris-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/neoteris-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NET Frameworkhttps://www.netdata.cloud/integrations/data-collection/applications/net-framework/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/applications/net-framework/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Net Insight AB SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/net-insight-ab-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/net-insight-ab-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Net Snmp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/net-snmp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/net-snmp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Net To Net Technologies SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/net-to-net-technologies-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/net-to-net-technologies-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Net Track GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/net-track-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/net-track-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->net.inet.icmp.statshttps://www.netdata.cloud/integrations/data-collection/networking/net.inet.icmp.stats/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/net.inet.icmp.stats/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->net.inet.ip.statshttps://www.netdata.cloud/integrations/data-collection/networking/net.inet.ip.stats/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/net.inet.ip.stats/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->net.inet.tcp.stateshttps://www.netdata.cloud/integrations/data-collection/networking/net.inet.tcp.states/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/net.inet.tcp.states/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->net.inet.udp.statshttps://www.netdata.cloud/integrations/data-collection/networking/net.inet.udp.stats/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/net.inet.udp.stats/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->net.inet6.icmp6.statshttps://www.netdata.cloud/integrations/data-collection/networking/net.inet6.icmp6.stats/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/net.inet6.icmp6.stats/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->net.inet6.ip6.statshttps://www.netdata.cloud/integrations/data-collection/networking/net.inet6.ip6.stats/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/net.inet6.ip6.stats/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->net.isrhttps://www.netdata.cloud/integrations/data-collection/networking/net.isr/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/net.isr/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netbotz SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netbotz-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netbotz-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netcomm Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netcomm-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netcomm-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netdata Mobile Apphttps://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/netdata-mobile-app/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/netdata-mobile-app/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netdata Streaming Topologyhttps://www.netdata.cloud/integrations/network-performance-monitoring/topologies/netdata-streaming-topology/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/topologies/netdata-streaming-topology/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netgear SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netgear-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netgear-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netline SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netline-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netline-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netpartner S R O SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netpartner-s-r-o-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netpartner-s-r-o-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netquest Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netquest-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netquest-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netrake Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netrake-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netrake-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netreality Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netreality-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netreality-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netscaler SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netscaler-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netscaler-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netscreen Technologies Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netscreen-technologies-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netscreen-technologies-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netstar Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netstar-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/netstar-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Network Alchemy Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/network-alchemy-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/network-alchemy-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Network Appliance Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/network-appliance-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/network-appliance-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Network interfaceshttps://www.netdata.cloud/integrations/data-collection/networking/network-interfaces/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/network-interfaces/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Network Subsystemhttps://www.netdata.cloud/integrations/data-collection/networking/network-subsystem/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/network-subsystem/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Network Technologies Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/network-technologies-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/network-technologies-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Networth Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/networth-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/networth-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->New Oak Communications Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/new-oak-communications-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/new-oak-communications-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->New Relichttps://www.netdata.cloud/integrations/exporters/new-relic/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/new-relic/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Newbridge Networks Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/newbridge-networks-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/newbridge-networks-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Newtec Cy SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/newtec-cy-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/newtec-cy-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nextnet SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nextnet-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nextnet-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NGINXhttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/nginx/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/nginx/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NGINX Plushttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/nginx-plus/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/nginx-plus/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NGINX Unithttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/nginx-unit/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/nginx-unit/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nice Systems Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nice-systems-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nice-systems-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nimble Storage SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nimble-storage-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nimble-storage-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nokia Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nokia-networks-formerly-nokia-siemens-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nokia-networks-formerly-nokia-siemens-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nokia SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nokia-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nokia-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nokia SNMP Traps (variant 1)https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nokia-formerly-alcatel-lucent-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nokia-formerly-alcatel-lucent-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nokia SNMP Traps (variant 2)https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nokia-formerly-coriant-r-d-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nokia-formerly-coriant-r-d-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nokia SNMP Traps (variant 3)https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nokia-formerly-infinera-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nokia-formerly-infinera-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nokia SNMP Traps (variant 4)https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nokia-formerly-lumentis-ab-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nokia-formerly-lumentis-ab-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nokia SNMP Traps (variant 5)https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nokia-formerly-transmode-systems-ab-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nokia-formerly-transmode-systems-ab-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nomadix SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nomadix-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nomadix-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Northern Telecom Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/northern-telecom-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/northern-telecom-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Novell SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/novell-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/novell-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Novelsat SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/novelsat-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/novelsat-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nsc Communications Siberia Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nsc-communications-siberia-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nsc-communications-siberia-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nsc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nsc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nsc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nsi Software SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nsi-software-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nsi-software-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NTPdhttps://www.netdata.cloud/integrations/data-collection/networking/ntpd/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/ntpd/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nutanix Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nutanix-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nutanix-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nxnetworks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nxnetworks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/nxnetworks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Occam Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/occam-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/occam-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Octel Communications Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/octel-communications-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/octel-communications-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Oid 0 SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/oid-0-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/oid-0-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Oid 1 SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/oid-1-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/oid-1-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Oki Data Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/oki-data-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/oki-data-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Olicom A S SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/olicom-a-s-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/olicom-a-s-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Omnitron Systems Technology SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/omnitron-systems-technology-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/omnitron-systems-technology-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->One4Net GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/one4net-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/one4net-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Oneaccess SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/oneaccess-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/oneaccess-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Onstream Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/onstream-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/onstream-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->OpeanSearchhttps://www.netdata.cloud/integrations/exporters/opeansearch/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/opeansearch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Opencode Systems Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/opencode-systems-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/opencode-systems-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Opengear Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/opengear-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/opengear-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->OpenTelemetry Logshttps://www.netdata.cloud/integrations/logs/opentelemetry-logs/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/logs/opentelemetry-logs/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->OpenTSDBhttps://www.netdata.cloud/integrations/exporters/opentsdb/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/opentsdb/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Openvision Technologies Limited SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/openvision-technologies-limited-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/openvision-technologies-limited-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->OpenVPNhttps://www.netdata.cloud/integrations/data-collection/networking/openvpn/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/openvpn/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->OpenVPN status loghttps://www.netdata.cloud/integrations/data-collection/networking/openvpn-status-log/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/openvpn-status-log/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Oplink Communications Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/oplink-communications-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/oplink-communications-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Opsgenie (Cloud notifications)https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/opsgenie/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/opsgenie/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Optical Access Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/optical-access-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/optical-access-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Optical Data Systems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/optical-data-systems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/optical-data-systems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Optical moduleshttps://www.netdata.cloud/integrations/data-collection/networking/optical-modules/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/optical-modules/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Optical Transmission Labs Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/optical-transmission-labs-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/optical-transmission-labs-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Oracle SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/oracle-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/oracle-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Os Nexus Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/os-nexus-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/os-nexus-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->OSPF Adjacency Topologyhttps://www.netdata.cloud/integrations/network-performance-monitoring/topologies/ospf-adjacency-topology/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/topologies/ospf-adjacency-topology/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Overland Data Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/overland-data-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/overland-data-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->P Cube Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/p-cube-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/p-cube-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pacific Broadband Communications SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pacific-broadband-communications-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pacific-broadband-communications-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pacific Broadbank Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pacific-broadbank-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pacific-broadbank-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pacific Softworks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pacific-softworks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pacific-softworks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Packeteer Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/packeteer-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/packeteer-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Packetlight Networks Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/packetlight-networks-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/packetlight-networks-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Padtec Optical Components And Systems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/padtec-optical-components-and-systems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/padtec-optical-components-and-systems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->PagerDuty (Cloud notifications)https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/pagerduty/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/pagerduty/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pairgain Technologies Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pairgain-technologies-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pairgain-technologies-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Palo Alto Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/palo-alto-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/palo-alto-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pan Dacom Direkt GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pan-dacom-direkt-gmbh-formerly-pan-dacom-networking-ag-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pan-dacom-direkt-gmbh-formerly-pan-dacom-networking-ag-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pan Dacom Telekommunikations SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pan-dacom-telekommunikations-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pan-dacom-telekommunikations-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Panasas Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/panasas-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/panasas-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Panduit Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/panduit-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/panduit-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Papouch Elektronika SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/papouch-elektronika-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/papouch-elektronika-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Paradyne SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/paradyne-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/paradyne-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Parameter LLC SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/parameter-llc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/parameter-llc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pdu5 SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pdu5-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pdu5-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pentair Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pentair-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pentair-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Peplinkhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/peplink/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/peplink/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Percona MySQLhttps://www.netdata.cloud/integrations/data-collection/databases/percona-mysql/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/databases/percona-mysql/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Peribit Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/peribit-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/peribit-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Periphonics Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/periphonics-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/periphonics-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Perle Systems Limited SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/perle-systems-limited-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/perle-systems-limited-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->PgBouncerhttps://www.netdata.cloud/integrations/data-collection/databases/pgbouncer/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/databases/pgbouncer/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Phihong USA SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/phihong-usa-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/phihong-usa-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Philips Communication D Entreprise Claude Lubin SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/philips-communication-d-entreprise-claude-lubin-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/philips-communication-d-entreprise-claude-lubin-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Phobos Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/phobos-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/phobos-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Phoenix Contact GmbH Co KG SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/phoenix-contact-gmbh-co-kg-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/phoenix-contact-gmbh-co-kg-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Phoenix Technologies Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/phoenix-technologies-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/phoenix-technologies-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Phoenixtec Power Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/phoenixtec-power-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/phoenixtec-power-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->PHP-FPMhttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/php-fpm/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/php-fpm/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->phpDaemonhttps://www.netdata.cloud/integrations/data-collection/applications/phpdaemon/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/applications/phpdaemon/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Picturetel Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/picturetel-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/picturetel-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pikahttps://www.netdata.cloud/integrations/data-collection/databases/pika/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/databases/pika/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Plaintree Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/plaintree-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/plaintree-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Planet Technology Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/planet-technology-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/planet-technology-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Platform Computing Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/platform-computing-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/platform-computing-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Plexcom Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/plexcom-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/plexcom-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Polycom Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/polycom-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/polycom-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->PostgreSQL (Exporter)https://www.netdata.cloud/integrations/exporters/postgresql/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/postgresql/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Power Distribution Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/power-distribution-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/power-distribution-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Powerdsine SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/powerdsine-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/powerdsine-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Powershield Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/powershield-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/powershield-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Powertek Limited SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/powertek-limited-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/powertek-limited-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Premier Network Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/premier-network-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/premier-network-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Printer Working Group SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/printer-working-group-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/printer-working-group-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Processorhttps://www.netdata.cloud/integrations/data-collection/operating-systems/processor/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/processor/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Prometheus Remote Writehttps://www.netdata.cloud/integrations/exporters/prometheus-remote-write/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/prometheus-remote-write/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Prominet Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/prominet-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/prominet-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Promise Technology Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/promise-technology-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/promise-technology-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Protection One Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/protection-one-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/protection-one-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Proxim Wireless Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/proxim-wireless-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/proxim-wireless-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pulizzi Engineering Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pulizzi-engineering-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pulizzi-engineering-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pulse Power And Measurement Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pulse-power-and-measurement-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pulse-power-and-measurement-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pure Storage SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pure-storage-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/pure-storage-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Qlogic SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/qlogic-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/qlogic-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Qnap Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/qnap-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/qnap-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Qsan Technology Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/qsan-technology-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/qsan-technology-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Qtech LLC SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/qtech-llc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/qtech-llc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Qualix Group Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/qualix-group-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/qualix-group-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Quanta Computer Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/quanta-computer-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/quanta-computer-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Quantum Bridge SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/quantum-bridge-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/quantum-bridge-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Quantum Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/quantum-corp-formerly-pathlight-technology-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/quantum-corp-formerly-pathlight-technology-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Quantum Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/quantum-corporation-formerly-advanced-digital-information-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/quantum-corporation-formerly-advanced-digital-information-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->QuasarDBhttps://www.netdata.cloud/integrations/exporters/quasardb/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/quasardb/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->RabbitMQhttps://www.netdata.cloud/integrations/data-collection/databases/rabbitmq/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/databases/rabbitmq/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Racktivity SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/racktivity-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/racktivity-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Racom S R O SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/racom-s-r-o-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/racom-s-r-o-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Rad Data Communications Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/rad-data-communications-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/rad-data-communications-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Radwin Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/radwin-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/radwin-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Rapid City Communication SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/rapid-city-communication-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/rapid-city-communication-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Rapidstream Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/rapidstream-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/rapidstream-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Raptor Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/raptor-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/raptor-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Raritan Computer Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/raritan-computer-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/raritan-computer-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Rbb Rundfunk Berlin Brandenburg SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/rbb-rundfunk-berlin-brandenburg-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/rbb-rundfunk-berlin-brandenburg-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Red Creek Communications Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/red-creek-communications-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/red-creek-communications-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Red Lion Controls N Tron SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/red-lion-controls-n-tron-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/red-lion-controls-n-tron-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Red Lion Controls Sixnet SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/red-lion-controls-sixnet-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/red-lion-controls-sixnet-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Redishttps://www.netdata.cloud/integrations/data-collection/databases/redis/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/databases/redis/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Redline Communications Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/redline-communications-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/redline-communications-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Redstone Communications Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/redstone-communications-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/redstone-communications-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Reltec Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/reltec-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/reltec-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Research In Motion Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/research-in-motion-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/research-in-motion-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Richard Hirschmann GmbH Co SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/richard-hirschmann-gmbh-co-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/richard-hirschmann-gmbh-co-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Rittal GmbH Co KG SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/rittal-gmbh-co-kg-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/rittal-gmbh-co-kg-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Riverbed Technology Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/riverbed-technology-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/riverbed-technology-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Riverdelta Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/riverdelta-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/riverdelta-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Riverstone Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/riverstone-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/riverstone-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Rnd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/rnd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/rnd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Rogue Engineering Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/rogue-engineering-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/rogue-engineering-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Rohde Schwarz GmbH Co KG SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/rohde-schwarz-gmbh-co-kg-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/rohde-schwarz-gmbh-co-kg-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ross Video Limited SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ross-video-limited-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ross-video-limited-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Rtbrick Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/rtbrick-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/rtbrick-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ruby Tech Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ruby-tech-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ruby-tech-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ruckus Wireless Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ruckus-wireless-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ruckus-wireless-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ruggedcom Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ruggedcom-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ruggedcom-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ruijie Networks Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ruijie-networks-co-ltd-formerly-start-network-technology-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ruijie-networks-co-ltd-formerly-start-network-technology-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Saf Tehnika SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/saf-tehnika-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/saf-tehnika-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Safran Trusted 4D Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/safran-trusted-4d-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/safran-trusted-4d-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sagemcom Sas SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sagemcom-sas-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sagemcom-sas-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Salix Technologies Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/salix-technologies-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/salix-technologies-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Samlex America Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/samlex-america-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/samlex-america-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Samsung Electronics Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/samsung-electronics-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/samsung-electronics-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sandvine Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sandvine-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sandvine-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sangoma Technologies SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sangoma-technologies-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sangoma-technologies-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sap AG SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sap-ag-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sap-ag-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Scannex Electronics Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/scannex-electronics-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/scannex-electronics-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Schechtertech LLC SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/schechtertech-llc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/schechtertech-llc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Schleifenbauer Products B.V. SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/schleifenbauer-products-b.v.-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/schleifenbauer-products-b.v.-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Schmid Telecom AG SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/schmid-telecom-ag-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/schmid-telecom-ag-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Schneider Electric Apc Netbotz SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/schneider-electric-apc-netbotz-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/schneider-electric-apc-netbotz-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Schneider Electric SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/schneider-electric-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/schneider-electric-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Schneider Koch Co Datensysteme GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/schneider-koch-co-datensysteme-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/schneider-koch-co-datensysteme-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SCIMhttps://www.netdata.cloud/integrations/authentication/scim/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/authentication/scim/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Scte SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/scte-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/scte-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Seagate Technology SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/seagate-technology-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/seagate-technology-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Securitymatrix Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/securitymatrix-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/securitymatrix-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Seh Computertechnik GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/seh-computertechnik-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/seh-computertechnik-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Senao International Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/senao-international-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/senao-international-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sensoria Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sensoria-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sensoria-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sensu Enterprise SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sensu-enterprise-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sensu-enterprise-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Server Technology Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/server-technology-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/server-technology-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ServiceNowhttps://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/servicenow/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/servicenow/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sgte Ies SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sgte-ies-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sgte-ies-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Shanghai Baud Data Communication Development Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/shanghai-baud-data-communication-development-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/shanghai-baud-data-communication-development-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Shanghai Meridian Technologies Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/shanghai-meridian-technologies-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/shanghai-meridian-technologies-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Shasta Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/shasta-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/shasta-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Shenzhen C Data Technology Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/shenzhen-c-data-technology-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/shenzhen-c-data-technology-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Shenzhen First Mile Communications Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/shenzhen-first-mile-communications-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/shenzhen-first-mile-communications-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Shenzhen Smartbyte Technology Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/shenzhen-smartbyte-technology-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/shenzhen-smartbyte-technology-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Shiva Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/shiva-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/shiva-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Siae Microelettronica S P A SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/siae-microelettronica-s-p-a-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/siae-microelettronica-s-p-a-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Siemens AG Automation Drives SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/siemens-ag-automation-drives-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/siemens-ag-automation-drives-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Siemens AG SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/siemens-ag-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/siemens-ag-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sigma Network Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sigma-network-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sigma-network-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sigur SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sigur-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sigur-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Siklu Communication Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/siklu-communication-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/siklu-communication-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Silver Peak Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/silver-peak-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/silver-peak-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sinclair Internetworking Services SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sinclair-internetworking-services-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sinclair-internetworking-services-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sinetica SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sinetica-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sinetica-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sita Ads SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sita-ads-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sita-ads-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Skyhigh Security LLC SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/skyhigh-security-llc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/skyhigh-security-llc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Slack (Cloud notifications)https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/slack/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/slack/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Smartoptics AS SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/smartoptics-as-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/smartoptics-as-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Smc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/smc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/smc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SMShttps://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/sms/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/sms/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Snarlsnmp Dynamic Web Application Monitor Developers Group SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/snarlsnmp-dynamic-web-application-monitor-developers-group-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/snarlsnmp-dynamic-web-application-monitor-developers-group-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SNMP Trap Node Attributionhttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/snmp-trap-node-attribution/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/snmp-trap-node-attribution/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SNMP Trap Relay Source Resolutionhttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/snmp-trap-relay-source-resolution/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/snmp-trap-relay-source-resolution/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SNMP Trap Reverse DNS Enrichmenthttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/snmp-trap-reverse-dns-enrichment/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/snmp-trap-reverse-dns-enrichment/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Socket statisticshttps://www.netdata.cloud/integrations/data-collection/networking/socket-statistics/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/socket-statistics/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Socomec Sicon Ups SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/socomec-sicon-ups-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/socomec-sicon-ups-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Softnet Statisticshttps://www.netdata.cloud/integrations/data-collection/networking/softnet-statistics/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/softnet-statistics/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sonicwall Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sonicwall-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sonicwall-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sonix Communications Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sonix-communications-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sonix-communications-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sonus Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sonus-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sonus-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sophos PLC SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sophos-plc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sophos-plc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Spectra Logic SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/spectra-logic-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/spectra-logic-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Spidcom Technologies S.A. SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/spidcom-technologies-s.a.-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/spidcom-technologies-s.a.-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Splunkhttps://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/splunk/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/splunk/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Splunk SignalFxhttps://www.netdata.cloud/integrations/exporters/splunk-signalfx/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/splunk-signalfx/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Spring Tide Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/spring-tide-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/spring-tide-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Standard SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/standard-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/standard-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Starent Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/starent-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/starent-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Starline Holdings SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/starline-holdings-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/starline-holdings-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Stonesoft Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/stonesoft-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/stonesoft-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Storage Computer Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/storage-computer-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/storage-computer-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Storage Networking Industry Association SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/storage-networking-industry-association-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/storage-networking-industry-association-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Storage Technology Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/storage-technology-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/storage-technology-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Stormshield SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/stormshield-formerly-netasq-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/stormshield-formerly-netasq-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->STP Topologyhttps://www.netdata.cloud/integrations/network-performance-monitoring/topologies/stp-topology/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/topologies/stp-topology/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Stratacom SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/stratacom-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/stratacom-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Stratus Computer SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/stratus-computer-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/stratus-computer-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Streamcore SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/streamcore-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/streamcore-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Stulz GmbH Klimatechnik SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/stulz-gmbh-klimatechnik-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/stulz-gmbh-klimatechnik-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sub10 Systems Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sub10-systems-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sub10-systems-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Super Micro Computer Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/super-micro-computer-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/super-micro-computer-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Supervisorhttps://www.netdata.cloud/integrations/data-collection/operating-systems/supervisor/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/supervisor/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Swapcom SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/swapcom-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/swapcom-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Swichtec Power Systems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/swichtec-power-systems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/swichtec-power-systems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Symantec Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/symantec-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/symantec-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Symbol Technologies Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/symbol-technologies-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/symbol-technologies-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Symmetricom SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/symmetricom-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/symmetricom-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Symplex Communications Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/symplex-communications-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/symplex-communications-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Synaccess Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/synaccess-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/synaccess-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Synamedia SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/synamedia-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/synamedia-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sync Research Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sync-research-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/sync-research-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Synernetics Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/synernetics-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/synernetics-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Synoptics SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/synoptics-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/synoptics-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Synso Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/synso-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/synso-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Syslog from Network Deviceshttps://www.netdata.cloud/integrations/network-performance-monitoring/syslog-from-network-devices/syslog-from-network-devices/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/syslog-from-network-devices/syslog-from-network-devices/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->System Engineering International SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/system-engineering-international-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/system-engineering-international-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->System Management Arts Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/system-management-arts-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/system-management-arts-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->system.ramhttps://www.netdata.cloud/integrations/data-collection/operating-systems/system.ram/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/system.ram/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tail F Systems AB SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tail-f-systems-ab-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tail-f-systems-ab-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tailyn Communication Company SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tailyn-communication-company-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tailyn-communication-company-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tait International Limited SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tait-international-limited-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tait-international-limited-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Talari Networks SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/talari-networks-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/talari-networks-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tandberg Television SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tandberg-television-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tandberg-television-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tandem Computers SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tandem-computers-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tandem-computers-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tasman Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tasman-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tasman-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tavve Software Co SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tavve-software-co-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tavve-software-co-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tecnair S P A SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tecnair-s-p-a-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tecnair-s-p-a-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tecnopro S.A. SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tecnopro-s.a.-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tecnopro-s.a.-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tegile Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tegile-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tegile-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Telco Systems Nac SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/telco-systems-nac-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/telco-systems-nac-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Teldat S A SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/teldat-s-a-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/teldat-s-a-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Telefonaktiebolaget Lm Ericsson SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/telefonaktiebolaget-lm-ericsson-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/telefonaktiebolaget-lm-ericsson-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Telegram (Cloud notifications)https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/telegram/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/telegram/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Telematics International Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/telematics-international-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/telematics-international-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Telesend Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/telesend-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/telesend-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Teleste Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/teleste-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/teleste-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Telesystems Slw Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/telesystems-slw-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/telesystems-slw-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Televes S A SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/televes-s-a-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/televes-s-a-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Television Systems Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/television-systems-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/television-systems-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Telstrat International Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/telstrat-international-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/telstrat-international-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Teltonika SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/teltonika-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/teltonika-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tenginehttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/tengine/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/tengine/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Teracom Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/teracom-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/teracom-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Teracom Telematica Ltda SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/teracom-telematica-ltda-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/teracom-telematica-ltda-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Terra SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/terra-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/terra-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Thales E Security SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/thales-e-security-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/thales-e-security-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Thanoshttps://www.netdata.cloud/integrations/exporters/thanos/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/thanos/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->The Advantage Group SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/the-advantage-group-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/the-advantage-group-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->The Freeradius Server Project SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/the-freeradius-server-project-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/the-freeradius-server-project-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->TiKVhttps://www.netdata.cloud/integrations/exporters/tikv/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/tikv/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Timeplex SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/timeplex-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/timeplex-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->TimescaleDBhttps://www.netdata.cloud/integrations/exporters/timescaledb/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/timescaledb/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Timesten Performance Software SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/timesten-performance-software-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/timesten-performance-software-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Timestep Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/timestep-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/timestep-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tintri Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tintri-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tintri-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Toshiba Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/toshiba-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/toshiba-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tp Link Systems Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tp-link-systems-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tp-link-systems-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Traefikhttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/traefik/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/traefik/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Trango Networks LLC SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/trango-networks-llc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/trango-networks-llc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Transition Engineering Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/transition-engineering-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/transition-engineering-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Trapeze Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/trapeze-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/trapeze-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Trend Micro Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/trend-micro-inc-formerly-tippingpoint-technologies-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/trend-micro-inc-formerly-tippingpoint-technologies-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Trend Micro Incorporated SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/trend-micro-incorporated-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/trend-micro-incorporated-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tridium SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tridium-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tridium-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tripp Lite SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tripp-lite-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tripp-lite-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tu Braunschweig SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tu-braunschweig-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tu-braunschweig-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tylink SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tylink-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/tylink-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->U C Davis Ece Dept Tom SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/u-c-davis-ece-dept-tom-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/u-c-davis-ece-dept-tom-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ucopia Communications SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ucopia-communications-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ucopia-communications-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->UK Mod De S SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/uk-mod-de-s-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/uk-mod-de-s-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Unboundhttps://www.netdata.cloud/integrations/data-collection/networking/unbound/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/networking/unbound/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Unisys Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/unisys-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/unisys-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Unitrends Software Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/unitrends-software-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/unitrends-software-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ups Manufacturing SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ups-manufacturing-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/ups-manufacturing-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->uptimehttps://www.netdata.cloud/integrations/data-collection/operating-systems/uptime/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/uptime/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Utstarcom Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/utstarcom-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/utstarcom-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Utstarcom Incorporated SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/utstarcom-incorporated-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/utstarcom-incorporated-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->V Solution SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/v-solution-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/v-solution-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Veeam Software SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/veeam-software-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/veeam-software-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Venturi Wireless SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/venturi-wireless-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/venturi-wireless-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Verax Systems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/verax-systems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/verax-systems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Verilink Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/verilink-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/verilink-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Veritas Software Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/veritas-software-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/veritas-software-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Veritas Technologies LLC SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/veritas-technologies-llc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/veritas-technologies-llc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->VerneMQhttps://www.netdata.cloud/integrations/data-collection/databases/vernemq/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/databases/vernemq/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Versa Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/versa-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/versa-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Vertical Networks Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vertical-networks-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vertical-networks-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Vertiv SNMP Traps (variant 1)https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vertiv-formerly-emerson-computer-power-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vertiv-formerly-emerson-computer-power-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Vertiv SNMP Traps (variant 2)https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vertiv-formerly-emerson-energy-systems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vertiv-formerly-emerson-energy-systems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Vertiv SNMP Traps (variant 3)https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vertiv-formerly-geist-manufacturing-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vertiv-formerly-geist-manufacturing-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Vertiv Tech Co Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vertiv-tech-co-ltd-formerly-emerson-network-power-co-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vertiv-tech-co-ltd-formerly-emerson-network-power-co-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Viavideo Communications Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/viavideo-communications-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/viavideo-communications-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->VictoriaMetricshttps://www.netdata.cloud/integrations/exporters/victoriametrics/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/victoriametrics/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Videoframe Systems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/videoframe-systems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/videoframe-systems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Videoserver Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/videoserver-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/videoserver-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Vigintos Elektronika SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vigintos-elektronika-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vigintos-elektronika-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Viptela Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/viptela-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/viptela-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->vm.loadavghttps://www.netdata.cloud/integrations/data-collection/operating-systems/vm.loadavg/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/vm.loadavg/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->vm.stats.sys.v_intrhttps://www.netdata.cloud/integrations/data-collection/operating-systems/vm.stats.sys.v_intr/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/vm.stats.sys.v_intr/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->vm.stats.sys.v_softhttps://www.netdata.cloud/integrations/data-collection/operating-systems/vm.stats.sys.v_soft/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/vm.stats.sys.v_soft/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->vm.stats.sys.v_swtchhttps://www.netdata.cloud/integrations/data-collection/operating-systems/vm.stats.sys.v_swtch/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/vm.stats.sys.v_swtch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->vm.stats.vm.v_pgfaultshttps://www.netdata.cloud/integrations/data-collection/operating-systems/vm.stats.vm.v_pgfaults/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/vm.stats.vm.v_pgfaults/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->vm.swap_infohttps://www.netdata.cloud/integrations/data-collection/operating-systems/vm.swap_info/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/vm.swap_info/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->vm.vmtotalhttps://www.netdata.cloud/integrations/data-collection/operating-systems/vm.vmtotal/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/vm.vmtotal/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->VMware Ariahttps://www.netdata.cloud/integrations/exporters/vmware-aria/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/vmware-aria/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Vmware Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vmware-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vmware-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Vocaltec Communications Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vocaltec-communications-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vocaltec-communications-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Voice Print International Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/voice-print-international-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/voice-print-international-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Volubill SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/volubill-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/volubill-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Vpnet SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vpnet-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vpnet-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->vSphere Topologyhttps://www.netdata.cloud/integrations/network-performance-monitoring/topologies/vsphere-topology/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/topologies/vsphere-topology/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Vutlan Sro SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vutlan-sro-formerly-sky-control-sro-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/vutlan-sro-formerly-sky-control-sro-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Wago Kontakttechnik GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/wago-kontakttechnik-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/wago-kontakttechnik-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Watchguard Technologies Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/watchguard-technologies-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/watchguard-technologies-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Wavefronthttps://www.netdata.cloud/integrations/exporters/wavefront/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/exporters/wavefront/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Waystream AB SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/waystream-ab-formerly-packetfront-network-products-ab-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/waystream-ab-formerly-packetfront-network-products-ab-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Webhookhttps://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/webhook/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/notifications/centralized-cloud-notifications/webhook/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Webscreen Technology Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/webscreen-technology-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/webscreen-technology-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Websense Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/websense-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/websense-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Wellfleet SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/wellfleet-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/wellfleet-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Westek Technology Ltd John Tucker SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/westek-technology-ltd-john-tucker-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/westek-technology-ltd-john-tucker-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Westell Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/westell-inc-formerly-kentrox-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/westell-inc-formerly-kentrox-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Westermo Teleindustri AB SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/westermo-teleindustri-ab-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/westermo-teleindustri-ab-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Western Digital Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/western-digital-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/western-digital-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Western Multiplex SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/western-multiplex-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/western-multiplex-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Western Telematic Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/western-telematic-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/western-telematic-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Wiesemann Theis GmbH SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/wiesemann-theis-gmbh-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/wiesemann-theis-gmbh-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Wind River Systems SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/wind-river-systems-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/wind-river-systems-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Wired For Management SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/wired-for-management-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/wired-for-management-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Wisi SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/wisi-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/wisi-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Wordperfect Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/wordperfect-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/wordperfect-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->World Wide Packets SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/world-wide-packets-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/world-wide-packets-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Wuhan Research Institute Of Posts And Telecommunications SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/wuhan-research-institute-of-posts-and-telecommunications-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/wuhan-research-institute-of-posts-and-telecommunications-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Wyse Technology SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/wyse-technology-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/wyse-technology-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Xedia Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/xedia-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/xedia-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Xerox SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/xerox-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/xerox-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Xiotech Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/xiotech-corporation-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/xiotech-corporation-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Xircom SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/xircom-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/xircom-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Xirrus Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/xirrus-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/xirrus-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Xylogics Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/xylogics-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/xylogics-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Xytronix Research Design Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/xytronix-research-design-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/xytronix-research-design-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Zao Light Communication SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/zao-light-communication-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/zao-light-communication-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Zenitel Norway AS SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/zenitel-norway-as-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/zenitel-norway-as-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Zeus Technology Ltd SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/zeus-technology-ltd-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/zeus-technology-ltd-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->zfshttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/zfs/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/zfs/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ZFS Adaptive Replacement Cachehttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/zfs-adaptive-replacement-cache/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/zfs-adaptive-replacement-cache/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Zhone Technologies Inc SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/zhone-technologies-inc-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/zhone-technologies-inc-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Zhongxing Telecom Co Ltd Abbr Zte SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/zhongxing-telecom-co-ltd-abbr-zte-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/zhongxing-telecom-co-ltd-abbr-zte-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Zoho Corporation SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/zoho-corporation-formerly-advent-network-management-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/zoho-corporation-formerly-advent-network-management-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ZooKeeperhttps://www.netdata.cloud/integrations/data-collection/applications/zookeeper/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/applications/zookeeper/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ZRAMhttps://www.netdata.cloud/integrations/data-collection/operating-systems/zram/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/data-collection/operating-systems/zram/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Zyxel Communications Corp SNMP Trapshttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/zyxel-communications-corp-snmp-traps/Sun, 16 Aug 2026 00:54:18 +0000https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/zyxel-communications-corp-snmp-traps/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->10 Best Apache Tomcat Monitoring Tools in 2026https://www.netdata.cloud/resources/best-tomcat-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-tomcat-monitoring-tools/10 Best Consul Monitoring Tools - Ranked & Reviewedhttps://www.netdata.cloud/resources/best-consul-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-consul-monitoring-tools/10 Best CoreDNS Monitoring Tools (2026)https://www.netdata.cloud/resources/best-coredns-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-coredns-monitoring-tools/10 Best Database Monitoring Tools (2027 Comparison)https://www.netdata.cloud/resources/best-database-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-database-monitoring-tools/10 Best Disk Health & S.M.A.R.T. Monitoring Toolshttps://www.netdata.cloud/resources/best-disk-health-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-disk-health-monitoring-tools/10 Best Docker Monitoring Tools In 2027 (Free & Paid)https://www.netdata.cloud/resources/best-docker-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-docker-monitoring-tools/10 Best GPU Monitoring Tools for AI Workloads (2026)https://www.netdata.cloud/resources/best-gpu-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-gpu-monitoring-tools/10 Best IoT Device Monitoring Tools 2027 (Free & Paid)https://www.netdata.cloud/resources/best-iot-device-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-iot-device-monitoring-tools/10 Best Kubernetes Monitoring Tools (2027 Comparison)https://www.netdata.cloud/resources/best-kubernetes-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-kubernetes-monitoring-tools/10 Best Linux Server Monitoring Tools (2027 Comparison)https://www.netdata.cloud/resources/best-linux-server-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-linux-server-monitoring-tools/10 Best Log Monitoring Tools In 2026 (Free & Paid)https://www.netdata.cloud/resources/best-log-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-log-monitoring-tools/10 Best Microsoft SQL Server Monitoring Tools (2026)https://www.netdata.cloud/resources/best-sql-server-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-sql-server-monitoring-tools/10 Best Network Monitoring Tools (2027 Software Comparison)https://www.netdata.cloud/resources/best-network-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-network-monitoring-tools/10 Best PostgreSQL Monitoring Tools for 2026https://www.netdata.cloud/resources/best-postgresql-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-postgresql-monitoring-tools/10 Best Varnish Cache Monitoring Toolshttps://www.netdata.cloud/resources/best-varnish-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-varnish-monitoring-tools/10 Best Windows Server Monitoring Tools (Free & Paid)https://www.netdata.cloud/resources/best-windows-server-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-windows-server-monitoring-tools/11 Best Elasticsearch Monitoring Tools Ranked (2026)https://www.netdata.cloud/resources/best-elasticsearch-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-elasticsearch-monitoring-tools/6 Best Logstash Monitoring Tools Ranked for 2026https://www.netdata.cloud/resources/best-logstash-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-logstash-monitoring-tools/7 Best Apache Pulsar Monitoring Tools Ranked (2026)https://www.netdata.cloud/resources/best-pulsar-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-pulsar-monitoring-tools/8 Best PgBouncer Monitoring Tools (2026)https://www.netdata.cloud/resources/best-pgbouncer-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-pgbouncer-monitoring-tools/Best ActiveMQ Monitoring Tools: 10 Ranked for 2026https://www.netdata.cloud/resources/best-activemq-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-activemq-monitoring-tools/Best Apache Monitoring Tools: 11 Picks Ranked for 2026https://www.netdata.cloud/resources/best-apache-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-apache-monitoring-tools/Best BIND DNS Monitoring Tools: 10 Ranked for 2026https://www.netdata.cloud/resources/best-bind-dns-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-bind-dns-monitoring-tools/Best Cassandra Monitoring Tools: 10 Ranked (2026)https://www.netdata.cloud/resources/best-cassandra-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-cassandra-monitoring-tools/Best Ceph Monitoring Tools: 7 Options Ranked (2026)https://www.netdata.cloud/resources/best-ceph-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-ceph-monitoring-tools/Best ClickHouse Monitoring Tools: 10 Ranked for 2026https://www.netdata.cloud/resources/best-clickhouse-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-clickhouse-monitoring-tools/Best Envoy Proxy Monitoring Tools (2026): 10 Rankedhttps://www.netdata.cloud/resources/best-envoy-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-envoy-monitoring-tools/Best Fluentd Monitoring Tools: 6 Top Picks for 2026https://www.netdata.cloud/resources/best-fluentd-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-fluentd-monitoring-tools/Best HAProxy Monitoring Tools: 10 Ranked Picks (2026)https://www.netdata.cloud/resources/best-haproxy-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-haproxy-monitoring-tools/Best Kafka Monitoring Tools: 10 Ranked for 2026https://www.netdata.cloud/resources/best-kafka-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-kafka-monitoring-tools/Best LVM & Linux Storage Monitoring Tools (9 Ranked)https://www.netdata.cloud/resources/best-lvm-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-lvm-monitoring-tools/Best Memcached Monitoring Tools in 2026: 10 Rankedhttps://www.netdata.cloud/resources/best-memcached-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-memcached-monitoring-tools/Best MongoDB Monitoring Tools (10 Ranked for 2026)https://www.netdata.cloud/resources/best-mongodb-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-mongodb-monitoring-tools/Best MySQL Monitoring Tools: 10 Options Ranked for 2026https://www.netdata.cloud/resources/best-mysql-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-mysql-monitoring-tools/Best NATS Monitoring Tools: 9 Ranked for 2026https://www.netdata.cloud/resources/best-nats-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-nats-monitoring-tools/Best NGINX Monitoring Tools: 10 Ranked & Reviewedhttps://www.netdata.cloud/resources/best-nginx-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-nginx-monitoring-tools/Best NVMe & SSD Health Monitoring Tools: 9 Options Rankedhttps://www.netdata.cloud/resources/best-nvme-ssd-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-nvme-ssd-monitoring-tools/Best Oracle Database Monitoring Tools: 10 Ranked for 2026https://www.netdata.cloud/resources/best-oracle-database-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-oracle-database-monitoring-tools/Best PHP-FPM Monitoring Tools: 10 Ranked (August 2026)https://www.netdata.cloud/resources/best-php-fpm-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-php-fpm-monitoring-tools/Best Postfix Monitoring Tools: 10 Compared (2026)https://www.netdata.cloud/resources/best-postfix-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-postfix-monitoring-tools/Best ProxySQL Monitoring Tools: 6 Ranked for 2026https://www.netdata.cloud/resources/best-proxysql-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-proxysql-monitoring-tools/Best RabbitMQ Monitoring Tools (2026): 10 Ranked & Reviewedhttps://www.netdata.cloud/resources/best-rabbitmq-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-rabbitmq-monitoring-tools/Best Redis Monitoring Tools: 10 Options Ranked for 2026https://www.netdata.cloud/resources/best-redis-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-redis-monitoring-tools/Best Traefik Monitoring Tools (10 Ranked for 2026)https://www.netdata.cloud/resources/best-traefik-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-traefik-monitoring-tools/Best uWSGI Monitoring Tools: 10 Ranked (2026)https://www.netdata.cloud/resources/best-uwsgi-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-uwsgi-monitoring-tools/Best VMware Monitoring Tools: 10 Ranked Picks for 2027https://www.netdata.cloud/resources/best-vmware-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-vmware-monitoring-tools/Best ZFS Monitoring Tools: 7 Ranked (August 2026)https://www.netdata.cloud/resources/best-zfs-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-zfs-monitoring-tools/Best ZooKeeper Monitoring Tools: 10 Ranked for 2026https://www.netdata.cloud/resources/best-zookeeper-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-zookeeper-monitoring-tools/The 10 Best CockroachDB Monitoring Tools for 2026https://www.netdata.cloud/resources/best-cockroachdb-monitoring-tools/Wed, 12 Aug 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-cockroachdb-monitoring-tools/1-Wire Sensorshttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/1-wire-sensors/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/1-wire-sensors/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->3Comhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/3com/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/3com/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->3Com Huaweihttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/3com-huawei/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/3com-huawei/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->A10https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/a10/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/a10/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Active Directory Certificate Servicehttps://www.netdata.cloud/integrations/data-collection/applications/active-directory-certificate-service/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/applications/active-directory-certificate-service/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Active Directory Federation Servicehttps://www.netdata.cloud/integrations/data-collection/applications/active-directory-federation-service/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/applications/active-directory-federation-service/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Adaptec RAIDhttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/adaptec-raid/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/adaptec-raid/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Alcatel Lucenthttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/alcatel-lucent/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/alcatel-lucent/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Alcatel Lucent ENThttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/alcatel-lucent-ent/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/alcatel-lucent-ent/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Alcatel Lucent INDhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/alcatel-lucent-ind/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/alcatel-lucent-ind/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Alcatel Lucent Omni Access WLChttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/alcatel-lucent-omni-access-wlc/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/alcatel-lucent-omni-access-wlc/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Alcatel-Lucent BGPhttps://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/alcatel-lucent-bgp/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/alcatel-lucent-bgp/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Alertahttps://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/alerta/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/alerta/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Alpine Linuxhttps://www.netdata.cloud/integrations/deploy/operating-systems/alpine-linux/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/deploy/operating-systems/alpine-linux/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->AM2320https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/am2320/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/am2320/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Amazon CloudWatchhttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/amazon-cloudwatch/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/amazon-cloudwatch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->AMD GPUhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/amd-gpu/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/amd-gpu/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Anuehttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/anue/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/anue/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->APChttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/apc/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/apc/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->APC Netbotzhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/apc-netbotz/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/apc-netbotz/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->APC UPS (go.d.plugin apcupsd)https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/apc-ups/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/apc-ups/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Arch Linuxhttps://www.netdata.cloud/integrations/deploy/operating-systems/arch-linux/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/deploy/operating-systems/arch-linux/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aristahttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/arista/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/arista/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Arista BGPhttps://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/arista-bgp/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/arista-bgp/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Arista Switchhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/arista-switch/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/arista-switch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Arubahttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/aruba/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/aruba/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aruba Access Pointhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/aruba-access-point/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/aruba-access-point/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aruba Clearpasshttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/aruba-clearpass/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/aruba-clearpass/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aruba Mobility Controllerhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/aruba-mobility-controller/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/aruba-mobility-controller/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aruba Switchhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/aruba-switch/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/aruba-switch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Aruba Wireless Controllerhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/aruba-wireless-controller/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/aruba-wireless-controller/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Audiocodes Mediant SBChttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/audiocodes-mediant-sbc/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/audiocodes-mediant-sbc/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Avayahttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avaya/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avaya/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Avaya Aura Media Serverhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avaya-aura-media-server/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avaya-aura-media-server/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Avaya Cajun Switchhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avaya-cajun-switch/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avaya-cajun-switch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Avaya Media Gatewayhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avaya-media-gateway/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avaya-media-gateway/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Avaya Nortel Ethernet Routing Switchhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avaya-nortel-ethernet-routing-switch/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avaya-nortel-ethernet-routing-switch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Avocent ACShttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avocent-acs/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avocent-acs/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Avtechhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avtech/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avtech/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Avtech Roomalert 32Shttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avtech-roomalert-32s/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avtech-roomalert-32s/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Avtech Roomalert 3Ehttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avtech-roomalert-3e/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avtech-roomalert-3e/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Avtech Roomalert 3Shttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avtech-roomalert-3s/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/avtech-roomalert-3s/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->AWS IP Rangeshttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/aws-ip-ranges/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/aws-ip-ranges/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->AWS Secrets Managerhttps://www.netdata.cloud/integrations/all/aws-secrets-manager/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/all/aws-secrets-manager/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->AWS SNShttps://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/aws-sns/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/aws-sns/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure IP Rangeshttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/azure-ip-ranges/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/azure-ip-ranges/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Azure Key Vault (Secret store)https://www.netdata.cloud/integrations/all/azure-key-vault/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/all/azure-key-vault/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Barracudahttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/barracuda/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/barracuda/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Barracuda Cloudgenhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/barracuda-cloudgen/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/barracuda-cloudgen/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->BCachehttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/bcache/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/bcache/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Beanstalkhttps://www.netdata.cloud/integrations/data-collection/databases/beanstalk/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/databases/beanstalk/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->bio-rd / RIPE RIShttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/bio-rd---ripe-ris/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/bio-rd---ripe-ris/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Blue Coat Licensinghttps://www.netdata.cloud/integrations/network-performance-monitoring/licensing-monitoring/blue-coat-licensing/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/licensing-monitoring/blue-coat-licensing/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bluecat Serverhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/bluecat-server/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/bluecat-server/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Bluecoat Proxysghttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/bluecoat-proxysg/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/bluecoat-proxysg/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->BMP (BGP Monitoring Protocol)https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/bmp-bgp-monitoring-protocol/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/bmp-bgp-monitoring-protocol/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Brocadehttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/brocade/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/brocade/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Brocade FC Switchhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/brocade-fc-switch/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/brocade-fc-switch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Brotherhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/brother/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/brother/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Brother NET Printerhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/brother-net-printer/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/brother-net-printer/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->BTRFShttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/btrfs/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/btrfs/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->CAIDA Routeviews Prefix-to-AShttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/caida-routeviews-prefix-to-as/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/caida-routeviews-prefix-to-as/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cassandrahttps://www.netdata.cloud/integrations/data-collection/databases/cassandra/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/databases/cassandra/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cato Networkshttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cato-networks/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cato-networks/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->CentOS Streamhttps://www.netdata.cloud/integrations/deploy/operating-systems/centos-stream/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/deploy/operating-systems/centos-stream/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Chatsworth PDUhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/chatsworth-pdu/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/chatsworth-pdu/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Checkpointhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/checkpoint/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/checkpoint/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Checkpoint Licensinghttps://www.netdata.cloud/integrations/network-performance-monitoring/licensing-monitoring/checkpoint-licensing/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/licensing-monitoring/checkpoint-licensing/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Chronyhttps://www.netdata.cloud/integrations/data-collection/networking/chrony/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/chrony/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Chrysalishttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/chrysalis/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/chrysalis/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Chrysalis Luna HSMhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/chrysalis-luna-hsm/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/chrysalis-luna-hsm/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco BGPhttps://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/cisco-bgp/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/cisco-bgp/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco Firepowerhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-firepower/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-firepower/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco Firepower ASAhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-firepower-asa/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-firepower-asa/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco Ironport Emailhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-ironport-email/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-ironport-email/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco ISEhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-ise/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-ise/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco Legacy WLChttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-legacy-wlc/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-legacy-wlc/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco Licensinghttps://www.netdata.cloud/integrations/network-performance-monitoring/licensing-monitoring/cisco-licensing/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/licensing-monitoring/cisco-licensing/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cisco Meraki (Cloud Controller)https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-meraki-cloud-controller/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cisco-meraki-cloud-controller/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Citrixhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/citrix/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/citrix/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Citrix Netscalerhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/citrix-netscaler/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/citrix-netscaler/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Citrix Netscaler SDXhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/citrix-netscaler-sdx/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/citrix-netscaler-sdx/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Classifiershttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/classifiers/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/classifiers/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Conntrackhttps://www.netdata.cloud/integrations/data-collection/networking/conntrack/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/conntrack/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->CPU performancehttps://www.netdata.cloud/integrations/data-collection/operating-systems/cpu-performance/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/cpu-performance/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cradlepointhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cradlepoint/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cradlepoint/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->CUPShttps://www.netdata.cloud/integrations/data-collection/applications/cups/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/applications/cups/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Customhttps://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/custom/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/custom/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Custom MMDB Databasehttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/custom-mmdb-database/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/custom-mmdb-database/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Cyberpower PDUhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cyberpower-pdu/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/cyberpower-pdu/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Debianhttps://www.netdata.cloud/integrations/deploy/operating-systems/debian/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/deploy/operating-systems/debian/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dellhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dell/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dell/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dell BGPhttps://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/dell-bgp/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/dell-bgp/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dell EMC Data Domainhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dell-emc-data-domain/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dell-emc-data-domain/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dell EMC ScaleIOhttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/dell-emc-scaleio/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/dell-emc-scaleio/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dell Force10https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dell-force10/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dell-force10/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dell OS10https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dell-os10/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dell-os10/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dell Powerconnecthttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dell-powerconnect/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dell-powerconnect/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dell Poweredgehttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dell-poweredge/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dell-poweredge/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dell PowerStorehttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/dell-powerstore/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/dell-powerstore/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dell PowerVault ME4/ME5https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/dell-powervault-me4-me5/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/dell-powervault-me4-me5/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dell Sonicwallhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dell-sonicwall/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dell-sonicwall/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->devstathttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/devstat/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/devstat/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dialogic Media Gatewayhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dialogic-media-gateway/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dialogic-media-gateway/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Discord (Agent notifications)https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/discord/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/discord/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Disk spacehttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/disk-space/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/disk-space/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Disk Statisticshttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/disk-statistics/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/disk-statistics/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dlinkhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dlink/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dlink/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Dlink DGS Switchhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dlink-dgs-switch/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/dlink-dgs-switch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->DMCache deviceshttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/dmcache-devices/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/dmcache-devices/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->DNS queryhttps://www.netdata.cloud/integrations/data-collection/synthetic-testing/dns-query/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/synthetic-testing/dns-query/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Docker (Deployment)https://www.netdata.cloud/integrations/deploy/docker-kubernetes/docker/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/deploy/docker-kubernetes/docker/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Docker (go.d.plugin docker)https://www.netdata.cloud/integrations/data-collection/containers-and-vms/docker/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/containers-and-vms/docker/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Docker Hub repositoryhttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/docker-hub-repository/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/containers-and-vms/docker-hub-repository/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Domain expiration datehttps://www.netdata.cloud/integrations/data-collection/synthetic-testing/domain-expiration-date/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/synthetic-testing/domain-expiration-date/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->eBPF Filedescriptorhttps://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-filedescriptor/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-filedescriptor/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->eBPF Filesystemhttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ebpf-filesystem/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ebpf-filesystem/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->eBPF SHMhttps://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-shm/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/ebpf-shm/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->eBPF Synchttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ebpf-sync/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ebpf-sync/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Emailhttps://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/email/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/email/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Envoyhttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/envoy/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/envoy/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Eximhttps://www.netdata.cloud/integrations/data-collection/applications/exim/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/applications/exim/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Extreme Switchinghttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/extreme-switching/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/extreme-switching/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->F5 BGPhttps://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/f5-bgp/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/f5-bgp/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->F5 BIG IPhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/f5-big-ip/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/f5-big-ip/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fail2banhttps://www.netdata.cloud/integrations/data-collection/applications/fail2ban/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/applications/fail2ban/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fedorahttps://www.netdata.cloud/integrations/deploy/operating-systems/fedora/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/deploy/operating-systems/fedora/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Files and directorieshttps://www.netdata.cloud/integrations/data-collection/synthetic-testing/files-and-directories/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/synthetic-testing/files-and-directories/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fireeyehttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/fireeye/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/fireeye/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fortinethttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/fortinet/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/fortinet/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fortinet Appliancehttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/fortinet-appliance/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/fortinet-appliance/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fortinet Fortigatehttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/fortinet-fortigate/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/fortinet-fortigate/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fortinet Fortiswitchhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/fortinet-fortiswitch/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/fortinet-fortiswitch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Fortinet Licensinghttps://www.netdata.cloud/integrations/network-performance-monitoring/licensing-monitoring/fortinet-licensing/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/licensing-monitoring/fortinet-licensing/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->FreeBSDhttps://www.netdata.cloud/integrations/deploy/operating-systems/freebsd/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/deploy/operating-systems/freebsd/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->GCP IP Rangeshttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/gcp-ip-ranges/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/gcp-ip-ranges/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Gearmanhttps://www.netdata.cloud/integrations/data-collection/applications/gearman/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/applications/gearman/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Generic BGP (BGP4-MIB)https://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/generic-bgp-bgp4-mib/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/generic-bgp-bgp4-mib/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Generic JSON-over-HTTP IPAMhttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/generic-json-over-http-ipam/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/generic-json-over-http-ipam/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Generic SNMP Devicehttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/generic-snmp-device/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/generic-snmp-device/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Generic UPS (UPS-MIB)https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/generic-ups-ups-mib/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/generic-ups-ups-mib/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Gigamonhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/gigamon/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/gigamon/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Go applications (EXPVAR)https://www.netdata.cloud/integrations/data-collection/applications/go-applications-expvar/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/applications/go-applications-expvar/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Google Secret Managerhttps://www.netdata.cloud/integrations/all/google-secret-manager/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/all/google-secret-manager/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Gotifyhttps://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/gotify/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/gotify/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Hardware information collected from kernel ring.https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/hardware-information-collected-from-kernel-ring./Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/hardware-information-collected-from-kernel-ring./<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->HP H3C Switchhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/hp-h3c-switch/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/hp-h3c-switch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->HP ICF Switchhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/hp-icf-switch/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/hp-icf-switch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->HPE Bladesystem Enclosurehttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/hpe-bladesystem-enclosure/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/hpe-bladesystem-enclosure/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->HPE Nimblehttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/hpe-nimble/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/hpe-nimble/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->HPE Prolianthttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/hpe-proliant/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/hpe-proliant/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->HPE Smart Arrayshttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/hpe-smart-arrays/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/hpe-smart-arrays/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Huaweihttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/huawei/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/huawei/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Huawei Access Controllershttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/huawei-access-controllers/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/huawei-access-controllers/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Huawei BGPhttps://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/huawei-bgp/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/huawei-bgp/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Huawei Routershttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/huawei-routers/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/huawei-routers/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Huawei Switcheshttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/huawei-switches/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/huawei-switches/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IBMhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ibm/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ibm/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IBM Datapower Gatewayhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ibm-datapower-gateway/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ibm-datapower-gateway/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IBM i (AS/400)https://www.netdata.cloud/integrations/data-collection/operating-systems/ibm-i-as-400/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/ibm-i-as-400/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IBM Lenovo Serverhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ibm-lenovo-server/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ibm-lenovo-server/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IBM MQ (ibm.d.plugin mq)https://www.netdata.cloud/integrations/data-collection/applications/ibm-mq/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/applications/ibm-mq/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IBM WebSphere JMXhttps://www.netdata.cloud/integrations/data-collection/applications/ibm-websphere-jmx/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/applications/ibm-websphere-jmx/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IBM WebSphere MicroProfilehttps://www.netdata.cloud/integrations/data-collection/applications/ibm-websphere-microprofile/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/applications/ibm-websphere-microprofile/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IIShttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/iis/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/iis/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ilert (Agent notifications)https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/ilert/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/ilert/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Infinera Coriant Groovehttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/infinera-coriant-groove/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/infinera-coriant-groove/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Infoblox Ipamhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/infoblox-ipam/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/infoblox-ipam/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Intel GPUhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/intel-gpu/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/intel-gpu/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Intelligent Platform Management Interface (IPMI)https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/intelligent-platform-management-interface-ipmi/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/intelligent-platform-management-interface-ipmi/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Inter Process Communicationhttps://www.netdata.cloud/integrations/data-collection/operating-systems/inter-process-communication/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/inter-process-communication/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Interruptshttps://www.netdata.cloud/integrations/data-collection/operating-systems/interrupts/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/interrupts/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IOPinghttps://www.netdata.cloud/integrations/data-collection/synthetic-testing/ioping/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/synthetic-testing/ioping/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IP Virtual Serverhttps://www.netdata.cloud/integrations/data-collection/networking/ip-virtual-server/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/ip-virtual-server/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IP2Location LITE IP-Countryhttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/ip2location-lite-ip-country/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/ip2location-lite-ip-country/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IPDeny Country Zoneshttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/ipdeny-country-zones/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/ipdeny-country-zones/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IPFIXhttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/flow-protocols/ipfix/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/flow-protocols/ipfix/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IPFShttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ipfs/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ipfs/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IPIP Country Databasehttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/ipip-country-database/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/ipip-country-database/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IPtoASNhttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/iptoasn/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/iptoasn/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->IRChttps://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/irc/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/irc/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ISC DHCPhttps://www.netdata.cloud/integrations/data-collection/networking/isc-dhcp/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/isc-dhcp/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ixsystems Truenashttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ixsystems-truenas/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ixsystems-truenas/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Juniperhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/juniper/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/juniper/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Juniper BGPhttps://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/juniper-bgp/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/juniper-bgp/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Juniper EXhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/juniper-ex/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/juniper-ex/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Juniper MXhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/juniper-mx/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/juniper-mx/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Juniper Pulse Securehttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/juniper-pulse-secure/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/juniper-pulse-secure/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Juniper QFXhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/juniper-qfx/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/juniper-qfx/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Juniper SRXhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/juniper-srx/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/juniper-srx/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kubernetes (Helm)https://www.netdata.cloud/integrations/deploy/docker-kubernetes/kubernetes-helm/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/deploy/docker-kubernetes/kubernetes-helm/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kubernetes API Serverhttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/kubernetes-api-server/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/containers-and-vms/kubernetes-api-server/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kubernetes Cluster Statehttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/kubernetes-cluster-state/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/containers-and-vms/kubernetes-cluster-state/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Kyocera Printerhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/kyocera-printer/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/kyocera-printer/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Libreswanhttps://www.netdata.cloud/integrations/data-collection/networking/libreswan/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/libreswan/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Lighttpdhttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/lighttpd/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/lighttpd/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Linksyshttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/linksys/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/linksys/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Linuxhttps://www.netdata.cloud/integrations/deploy/operating-systems/linux/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/deploy/operating-systems/linux/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Linux kernel SLAB allocator statisticshttps://www.netdata.cloud/integrations/data-collection/operating-systems/linux-kernel-slab-allocator-statistics/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/linux-kernel-slab-allocator-statistics/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Linux ZSwaphttps://www.netdata.cloud/integrations/data-collection/operating-systems/linux-zswap/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/linux-zswap/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Litespeedhttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/litespeed/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/litespeed/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->LVM logical volumeshttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/lvm-logical-volumes/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/lvm-logical-volumes/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->macOS (Deployment)https://www.netdata.cloud/integrations/deploy/operating-systems/macos/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/deploy/operating-systems/macos/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->macOS (macos.plugin mach_smi)https://www.netdata.cloud/integrations/data-collection/operating-systems/macos/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/macos/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->macOS Unified Logshttps://www.netdata.cloud/integrations/logs/macos-unified-logs/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/logs/macos-unified-logs/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Manjaro Linuxhttps://www.netdata.cloud/integrations/deploy/operating-systems/manjaro-linux/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/deploy/operating-systems/manjaro-linux/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Matrixhttps://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/matrix/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/matrix/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->MaxMind GeoIP / GeoLite2https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/maxmind-geoip---geolite2/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/maxmind-geoip---geolite2/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->MaxScalehttps://www.netdata.cloud/integrations/data-collection/databases/maxscale/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/databases/maxscale/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mcafee WEB Gatewayhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/mcafee-web-gateway/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/mcafee-web-gateway/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->MD RAIDhttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/md-raid/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/md-raid/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->MegaCLI MegaRAIDhttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/megacli-megaraid/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/megacli-megaraid/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Memcachedhttps://www.netdata.cloud/integrations/data-collection/databases/memcached/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/databases/memcached/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Memory Statistics (Win)https://www.netdata.cloud/integrations/data-collection/operating-systems/memory-statistics-win/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/memory-statistics-win/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Memory Usagehttps://www.netdata.cloud/integrations/data-collection/operating-systems/memory-usage/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/memory-usage/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Merakihttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/meraki/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/meraki/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->MessageBirdhttps://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/messagebird/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/messagebird/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Microsoft Teams (Agent notifications)https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/microsoft-teams/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/microsoft-teams/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->MikroTik Licensinghttps://www.netdata.cloud/integrations/network-performance-monitoring/licensing-monitoring/mikrotik-licensing/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/licensing-monitoring/mikrotik-licensing/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Mikrotik Routerhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/mikrotik-router/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/mikrotik-router/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Monithttps://www.netdata.cloud/integrations/data-collection/synthetic-testing/monit/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/synthetic-testing/monit/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nagios Plugins and Custom Scriptshttps://www.netdata.cloud/integrations/data-collection/synthetic-testing/nagios-plugins-and-custom-scripts/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/synthetic-testing/nagios-plugins-and-custom-scripts/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nasuni Filerhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/nasuni-filer/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/nasuni-filer/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NEC BGPhttps://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/nec-bgp/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/nec-bgp/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NEC Univergehttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/nec-univerge/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/nec-univerge/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Net-SNMP Hosthttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/net-snmp-host/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/net-snmp-host/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->net.inet.tcp.statshttps://www.netdata.cloud/integrations/data-collection/networking/net.inet.tcp.stats/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/net.inet.tcp.stats/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netapphttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/netapp/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/netapp/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NetBoxhttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/netbox/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/netbox/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netfilterhttps://www.netdata.cloud/integrations/data-collection/networking/netfilter/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/netfilter/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NetFlowhttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/flow-protocols/netflow/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/flow-protocols/netflow/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netgearhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/netgear/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/netgear/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netgear Access Pointhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/netgear-access-point/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/netgear-access-point/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netgear Readynashttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/netgear-readynas/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/netgear-readynas/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Netgear Switchhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/netgear-switch/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/netgear-switch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Network statisticshttps://www.netdata.cloud/integrations/data-collection/networking/network-statistics/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/network-statistics/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NFS Clienthttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/nfs-client/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/nfs-client/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NFS Serverhttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/nfs-server/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/nfs-server/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NGINX VTShttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/nginx-vts/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/nginx-vts/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nokia BGPhttps://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/nokia-bgp/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/nokia-bgp/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nokia Service Router OShttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/nokia-service-router-os/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/nokia-service-router-os/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Non-Uniform Memory Accesshttps://www.netdata.cloud/integrations/data-collection/operating-systems/non-uniform-memory-access/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/non-uniform-memory-access/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NSDhttps://www.netdata.cloud/integrations/data-collection/networking/nsd/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/nsd/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NUMA Architecturehttps://www.netdata.cloud/integrations/data-collection/operating-systems/numa-architecture/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/numa-architecture/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nvidiahttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/nvidia/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/nvidia/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->NVIDIA BGPhttps://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/nvidia-bgp/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/bgp-monitoring/nvidia-bgp/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nvidia Cumulus Linux Switchhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/nvidia-cumulus-linux-switch/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/nvidia-cumulus-linux-switch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nvidia Data Center GPU Manager (DCGM)https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/nvidia-data-center-gpu-manager-dcgm/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/nvidia-data-center-gpu-manager-dcgm/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nvidia GPUhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/nvidia-gpu/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/nvidia-gpu/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Nvidia Mellanox Switchxhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/nvidia-mellanox-switchx/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/nvidia-mellanox-switchx/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->OIDChttps://www.netdata.cloud/integrations/authentication/oidc/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/authentication/oidc/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Okta SSOhttps://www.netdata.cloud/integrations/authentication/okta-sso/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/authentication/okta-sso/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Omron CJ Ethernet IPhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/omron-cj-ethernet-ip/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/omron-cj-ethernet-ip/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Opengear Console Managerhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/opengear-console-manager/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/opengear-console-manager/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Opengear Infrastructure Managerhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/opengear-infrastructure-manager/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/opengear-infrastructure-manager/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->OpenLDAPhttps://www.netdata.cloud/integrations/data-collection/applications/openldap/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/applications/openldap/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->OpenShift Containershttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/openshift-containers/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/containers-and-vms/openshift-containers/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->OpenSIPShttps://www.netdata.cloud/integrations/data-collection/applications/opensips/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/applications/opensips/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->OpsGenie (Agent notifications)https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/opsgenie/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/opsgenie/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Oracle DBhttps://www.netdata.cloud/integrations/data-collection/databases/oracle-db/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/databases/oracle-db/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Oracle Linuxhttps://www.netdata.cloud/integrations/deploy/operating-systems/oracle-linux/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/deploy/operating-systems/oracle-linux/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Page typeshttps://www.netdata.cloud/integrations/data-collection/operating-systems/page-types/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/page-types/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Palo Altohttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/palo-alto/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/palo-alto/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Palo Alto Cloudgenixhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/palo-alto-cloudgenix/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/palo-alto-cloudgenix/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pandashttps://www.netdata.cloud/integrations/data-collection/databases/pandas/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/databases/pandas/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->PF Sensehttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/pf-sense/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/pf-sense/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Physical and Logical Disk Performance Metricshttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/physical-and-logical-disk-performance-metrics/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/physical-and-logical-disk-performance-metrics/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pi-holehttps://www.netdata.cloud/integrations/data-collection/networking/pi-hole/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/pi-hole/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pinghttps://www.netdata.cloud/integrations/data-collection/synthetic-testing/ping/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/synthetic-testing/ping/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Postfixhttps://www.netdata.cloud/integrations/data-collection/applications/postfix/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/applications/postfix/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->PostgreSQL (go.d.plugin postgres)https://www.netdata.cloud/integrations/data-collection/databases/postgresql/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/databases/postgresql/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Power Cappinghttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/power-capping/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/power-capping/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Power Supplyhttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/power-supply/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/power-supply/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Power Supply (Win)https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/power-supply-win/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/power-supply-win/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->PowerDNS Authoritative Serverhttps://www.netdata.cloud/integrations/data-collection/networking/powerdns-authoritative-server/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/powerdns-authoritative-server/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->PowerDNS Recursorhttps://www.netdata.cloud/integrations/data-collection/networking/powerdns-recursor/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/powerdns-recursor/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Pressure Stall Informationhttps://www.netdata.cloud/integrations/data-collection/operating-systems/pressure-stall-information/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/pressure-stall-information/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Prowlhttps://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/prowl/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/prowl/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Proxmox VE Monitoringhttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/proxmox-ve-monitoring/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/containers-and-vms/proxmox-ve-monitoring/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Puppethttps://www.netdata.cloud/integrations/data-collection/cloud-and-devops/puppet/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/cloud-and-devops/puppet/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->PushOverhttps://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/pushover/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/pushover/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Raritan Dominionhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/raritan-dominion/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/raritan-dominion/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->RethinkDBhttps://www.netdata.cloud/integrations/data-collection/databases/rethinkdb/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/databases/rethinkdb/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Riak KVhttps://www.netdata.cloud/integrations/data-collection/databases/riak-kv/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/databases/riak-kv/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Riverbedhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/riverbed/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/riverbed/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Riverbed Interceptorhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/riverbed-interceptor/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/riverbed-interceptor/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Riverbed Steelheadhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/riverbed-steelhead/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/riverbed-steelhead/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->RocketChat (Agent notifications)https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/rocketchat/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/rocketchat/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Rocky Linuxhttps://www.netdata.cloud/integrations/deploy/operating-systems/rocky-linux/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/deploy/operating-systems/rocky-linux/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Rspamdhttps://www.netdata.cloud/integrations/data-collection/applications/rspamd/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/applications/rspamd/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ruckushttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ruckus/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ruckus/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ruckus Unleashedhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ruckus-unleashed/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ruckus-unleashed/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ruckus WAPhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ruckus-wap/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ruckus-wap/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->S.M.A.R.T.https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/s.m.a.r.t./Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/s.m.a.r.t./<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sambahttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/samba/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/samba/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SCTP Statisticshttps://www.netdata.cloud/integrations/data-collection/networking/sctp-statistics/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/sctp-statistics/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Semaphore statisticshttps://www.netdata.cloud/integrations/data-collection/operating-systems/semaphore-statistics/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/semaphore-statistics/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sensorshttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/sensors/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/sensors/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Server Iron Switchhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/server-iron-switch/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/server-iron-switch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Servertechhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/servertech/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/servertech/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Servertech Pdu3https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/servertech-pdu3/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/servertech-pdu3/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Servertech Pdu4https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/servertech-pdu4/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/servertech-pdu4/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->sFlowhttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/flow-protocols/sflow/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/flow-protocols/sflow/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SIGNL4https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/signl4/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/signl4/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Silverpeak Edgeconnecthttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/silverpeak-edgeconnect/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/silverpeak-edgeconnect/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sinetica Eagle Ihttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/sinetica-eagle-i/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/sinetica-eagle-i/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Slack (Agent notifications)https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/slack/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/slack/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SMB Server Shareshttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/smb-server-shares/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/smb-server-shares/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SMSEaglehttps://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/smseagle/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/smseagle/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SNMP trap listenerhttps://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/snmp-trap-listener/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/snmp-traps/snmp-trap-listener/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SoftIRQ statisticshttps://www.netdata.cloud/integrations/data-collection/operating-systems/softirq-statistics/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/softirq-statistics/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sophos Licensinghttps://www.netdata.cloud/integrations/network-performance-monitoring/licensing-monitoring/sophos-licensing/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/licensing-monitoring/sophos-licensing/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Sophos XGS Firewallhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/sophos-xgs-firewall/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/sophos-xgs-firewall/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SpigotMChttps://www.netdata.cloud/integrations/data-collection/applications/spigotmc/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/applications/spigotmc/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Squidhttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/squid/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/squid/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Static Metadatahttps://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/static-metadata/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/network-flows/enrichment-methods/static-metadata/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->StoreCLI RAIDhttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/storecli-raid/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/storecli-raid/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->SUSE Linuxhttps://www.netdata.cloud/integrations/deploy/operating-systems/suse-linux/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/deploy/operating-systems/suse-linux/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Synproxyhttps://www.netdata.cloud/integrations/data-collection/networking/synproxy/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/synproxy/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->sysloghttps://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/syslog/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/syslog/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->System Load Averagehttps://www.netdata.cloud/integrations/data-collection/operating-systems/system-load-average/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/system-load-average/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->System Memory Fragmentationhttps://www.netdata.cloud/integrations/data-collection/operating-systems/system-memory-fragmentation/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/system-memory-fragmentation/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->System statistics (proc.plugin /proc/stat)https://www.netdata.cloud/integrations/data-collection/operating-systems/system-statistics-procplugin-procstat/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/system-statistics-procplugin-procstat/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->System statistics (windows.plugin PerflibProcesses)https://www.netdata.cloud/integrations/data-collection/operating-systems/system-statistics/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/system-statistics/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->System thermal zonehttps://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/system-thermal-zone/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/system-thermal-zone/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->System Uptimehttps://www.netdata.cloud/integrations/data-collection/operating-systems/system-uptime/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/system-uptime/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Systemd Journal Logs (Logs integration)https://www.netdata.cloud/integrations/logs/systemd-journal-logs/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/logs/systemd-journal-logs/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Systemd Unitshttps://www.netdata.cloud/integrations/data-collection/operating-systems/systemd-units/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/systemd-units/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->systemd-logind usershttps://www.netdata.cloud/integrations/data-collection/operating-systems/systemd-logind-users/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/systemd-logind-users/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->tc QoS classeshttps://www.netdata.cloud/integrations/data-collection/networking/tc-qos-classes/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/tc-qos-classes/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->TCP/UDP Endpointshttps://www.netdata.cloud/integrations/data-collection/synthetic-testing/tcp-udp-endpoints/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/synthetic-testing/tcp-udp-endpoints/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Telegram (Agent notifications)https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/telegram/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/telegram/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Timexhttps://www.netdata.cloud/integrations/data-collection/networking/timex/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/timex/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tomcathttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/tomcat/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/tomcat/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Torhttps://www.netdata.cloud/integrations/data-collection/networking/tor/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/tor/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->TP Linkhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/tp-link/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/tp-link/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tripplitehttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/tripplite/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/tripplite/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tripplite PDUhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/tripplite-pdu/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/tripplite-pdu/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Tripplite UPShttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/tripplite-ups/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/tripplite-ups/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Twiliohttps://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/twilio/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/notifications/agent-dispatched-notifications/twilio/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Typesensehttps://www.netdata.cloud/integrations/data-collection/databases/typesense/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/databases/typesense/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ubiquiti Unifihttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ubiquiti-unifi/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ubiquiti-unifi/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Ubiquiti Unifi Security Gatewayhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ubiquiti-unifi-security-gateway/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/ubiquiti-unifi-security-gateway/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->UPS (NUT)https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/ups-nut/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/ups-nut/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->User Groupshttps://www.netdata.cloud/integrations/data-collection/operating-systems/user-groups/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/user-groups/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Usershttps://www.netdata.cloud/integrations/data-collection/operating-systems/users/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/users/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->uWSGIhttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/uwsgi/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/uwsgi/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Varnishhttps://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/varnish/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/varnish/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Vaulthttps://www.netdata.cloud/integrations/all/vault/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/all/vault/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->vCenter Server Appliancehttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/vcenter-server-appliance/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/containers-and-vms/vcenter-server-appliance/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Velocloud Edgehttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/velocloud-edge/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/velocloud-edge/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Vertiv Liebert AChttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/vertiv-liebert-ac/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/vertiv-liebert-ac/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Vertiv Watchdoghttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/vertiv-watchdog/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/vertiv-watchdog/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->vm.stats.vm.v_swappgshttps://www.netdata.cloud/integrations/data-collection/operating-systems/vm.stats.vm.v_swappgs/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/vm.stats.vm.v_swappgs/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Vmware ESXhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/vmware-esx/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/vmware-esx/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Watchguardhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/watchguard/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/watchguard/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Western Digital Mycloud EX2 Ultrahttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/western-digital-mycloud-ex2-ultra/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/western-digital-mycloud-ex2-ultra/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Windows Event Logshttps://www.netdata.cloud/integrations/logs/windows-event-logs/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/logs/windows-event-logs/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Windows Services (apps.plugin services)https://www.netdata.cloud/integrations/data-collection/operating-systems/windows-services-appsplugin-services/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/windows-services-appsplugin-services/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Windows Services (windows.plugin PerflibServices)https://www.netdata.cloud/integrations/data-collection/operating-systems/windows-services/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/operating-systems/windows-services/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->WireGuardhttps://www.netdata.cloud/integrations/data-collection/networking/wireguard/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/wireguard/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Wireless network interfaceshttps://www.netdata.cloud/integrations/data-collection/networking/wireless-network-interfaces/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/networking/wireless-network-interfaces/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Xen XCP-nghttps://www.netdata.cloud/integrations/data-collection/containers-and-vms/xen-xcp-ng/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/containers-and-vms/xen-xcp-ng/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->YugabyteDBhttps://www.netdata.cloud/integrations/data-collection/databases/yugabytedb/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/databases/yugabytedb/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Zebra Printerhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/zebra-printer/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/zebra-printer/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->ZFS Poolshttps://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/zfs-pools/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/zfs-pools/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Zyxel Switchhttps://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/zyxel-switch/Wed, 12 Aug 2026 00:00:00 +0300https://www.netdata.cloud/integrations/network-performance-monitoring/device-metrics/zyxel-switch/<!-- AUTOGENERATED BY /scripts/build_integrations_md_files.py -->Introducing MCP Connections: Netdata AI Now Reads From the Tools You Already Runhttps://www.netdata.cloud/blog/netdata-ai-mcp-connections/Mon, 03 Aug 2026 00:00:00 +0000https://www.netdata.cloud/blog/netdata-ai-mcp-connections/<p>Netdata AI can now connect outward to the tools your team already runs, like GitHub, PagerDuty, Atlassian, or any custom MCP server, and read from them during an investigation. We call this <strong>MCP Connections</strong>. It&rsquo;s the missing piece in the middle of every root-cause investigation: the alert tells you what changed, but the why is usually somewhere else entirely.</p> <!--truncate--> <h2 id="the-missing-context">The missing context</h2> <p>A latency spike fires an alert. The metrics show exactly when it started and which service it hit. They don&rsquo;t show the deploy that went out four minutes earlier, the PagerDuty incident already open for the same symptom, or the runbook someone wrote for this exact failure mode six months ago. That context exists. It&rsquo;s just scattered across a pull request, a ticketing system, and a wiki page, in tools your monitoring platform has never been able to see.</p>Native macOS Monitoring: Logs, Sensors, GPU & Hardware Healthhttps://www.netdata.cloud/blog/macos-monitoring/Wed, 15 Jul 2026 00:00:00 +0000https://www.netdata.cloud/blog/macos-monitoring/<p><img src="../images/macos-monitoring.svg" alt="Native macOS monitoring with Netdata: unified logs, power, sensors, GPU, per-app metrics, storage, and network"></p> <p>We&rsquo;ve overhauled macOS monitoring in the latest Netdata release. Netdata already collects system metrics on Macs at per-second resolution; this release completes the picture with logs and hardware telemetry, areas that previously required users to run CLI tools like <code>log show</code> and <code>powermetrics</code>. The new collectors read this data through Apple&rsquo;s own frameworks, allowing users to trace application and OS errors and catch hardware issues early.</p>9 Best Container Monitoring Tools & How To Choosehttps://www.netdata.cloud/resources/best-container-monitoring-tools/Thu, 09 Jul 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-container-monitoring-tools/SolarWinds NPM Alternative: With Per-Second Metricshttps://www.netdata.cloud/solarwinds-npm-alternative/Mon, 29 Jun 2026 00:00:00 +0000https://www.netdata.cloud/solarwinds-npm-alternative/Replace 5-minute SNMP polling with per-second network monitoring, ML anomaly detection, and zero-template device discovery.SolarWinds NTA Alternative: NetFlow Traffic Analyzerhttps://www.netdata.cloud/solarwinds-nta-alternative/Mon, 29 Jun 2026 00:00:00 +0000https://www.netdata.cloud/solarwinds-nta-alternative/Replace SolarWinds NTA with Netdata for modern, per-second NetFlow analysis, interactive Sankey diagrams, street-level maps, and zero-config deployment.SolarWinds Observability Alternative: Real-Time & AIhttps://www.netdata.cloud/solarwinds-observability-alternative/Mon, 29 Jun 2026 00:00:00 +0000https://www.netdata.cloud/solarwinds-observability-alternative/Netdata is the modern alternative to SolarWinds Hybrid Cloud Observability: per-second resolution, edge-native ML on every metric, zero-config deployment, and flat per-node pricing with full data sovereignty.SolarWinds Orion Alternative: One Agent, Full Stackhttps://www.netdata.cloud/solarwinds-orion-alternative/Mon, 29 Jun 2026 00:00:00 +0000https://www.netdata.cloud/solarwinds-orion-alternative/Replace SolarWinds Orion Platform with Netdata: one agent, per-second visibility, ML anomaly detection, AI troubleshooting, and network flow analysis without stacked module licenses.SolarWinds SAM Alternative: Server & App Monitoringhttps://www.netdata.cloud/solarwinds-sam-alternative/Mon, 29 Jun 2026 00:00:00 +0000https://www.netdata.cloud/solarwinds-sam-alternative/Fleet Observability: Linux Edge Device Monitoringhttps://www.netdata.cloud/blog/fleet-observability/Sun, 28 Jun 2026 00:00:00 +0000https://www.netdata.cloud/blog/fleet-observability/<p>It feels less like managing devices and more like remote babysitting. You check the dashboard, everything is green, and then a customer in the field tells you a device has been down for two days. At a handful of servers, the rare failure is an event. Across thousands of distributed Linux endpoints — robots in warehouses, EV chargers across a city, kiosks in retail, IoT gateways in the field — the rare failure becomes a daily occurrence, and the tools built for a datacenter quietly stop telling you the truth.</p>Distributed & Edge Fleet Monitoringhttps://www.netdata.cloud/solutions/use-cases/edge-fleet-monitoring/Thu, 25 Jun 2026 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/edge-fleet-monitoring/Netdata brings real-time, AI-powered observability to distributed fleets of Linux endpoints — robots, kiosks, POS terminals, IoT gateways, and remote servers — keeping data and intelligence at the edge where it belongs.EV Charging Network Monitoringhttps://www.netdata.cloud/solutions/industries/ev-charging/Thu, 25 Jun 2026 00:00:00 +0000https://www.netdata.cloud/solutions/industries/ev-charging/Netdata gives charge point operators per-second visibility into every charger controller, with edge-resident storage and streaming that survives flaky site connectivity.Retail POS and Kiosk Fleet Monitoringhttps://www.netdata.cloud/solutions/industries/pos-kiosk-monitoring/Thu, 25 Jun 2026 00:00:00 +0000https://www.netdata.cloud/solutions/industries/pos-kiosk-monitoring/Netdata gives per-second visibility into every POS terminal and self-service kiosk across thousands of stores, with edge-resident monitoring that survives flaky in-store networks.Robot Fleet Monitoring with Per-Second Edge Intelligencehttps://www.netdata.cloud/solutions/industries/robotics/Thu, 25 Jun 2026 00:00:00 +0000https://www.netdata.cloud/solutions/industries/robotics/Netdata runs on each robot, collecting per-second metrics for compute, memory, storage, thermals, and network — keeping thousands of devices observable even on intermittent site networks, without centralized SaaS.School Safety Device Fleet Monitoringhttps://www.netdata.cloud/solutions/industries/education-device-monitoring/Thu, 25 Jun 2026 00:00:00 +0000https://www.netdata.cloud/solutions/industries/education-device-monitoring/Netdata runs on every campus device, giving IT teams per-second visibility into compute, connectivity, and OS health across thousands of school safety devices and endpoints.What Is Edge Monitoring? Edge Observability Explainedhttps://www.netdata.cloud/academy/what-is-edge-monitoring/Thu, 25 Jun 2026 00:00:00 +0000https://www.netdata.cloud/academy/what-is-edge-monitoring/<p>Edge monitoring means running the full observability pipeline - collection, storage, anomaly detection, alerting, and dashboards - on or near the monitored device itself, instead of shipping all raw telemetry to a central system first. Each node in the fleet collects and processes its own metrics locally, and only forwards what is needed upstream. This model is essential for distributed fleets of thousands of devices where centralizing all telemetry is economically and technically impractical.</p>NetFlow vs sFlow vs IPFIX: Differences & When To Usehttps://www.netdata.cloud/academy/netflow-sflow-ipfix/Wed, 24 Jun 2026 00:00:00 +0000https://www.netdata.cloud/academy/netflow-sflow-ipfix/<p>NetFlow, sFlow, and IPFIX are three network traffic export protocols that give visibility into traffic flows without requiring full packet capture. NetFlow and IPFIX aggregate packets into flow records on the device before exporting them, providing exact (if unsampled) accounting. sFlow takes a fundamentally different approach: it exports every Nth packet header plus interface counters, making it stateless and scalable but statistical rather than exact. IPFIX is the IETF-standardized evolution of NetFlow v9, adding vendor-neutral extensibility through template-based information elements.</p>Network Monitoring Dashboardhttps://www.netdata.cloud/features/network/dashboard/Wed, 24 Jun 2026 00:00:00 +0000https://www.netdata.cloud/features/network/dashboard/Netdata&rsquo;s Network Monitoring Dashboard unifies SNMP device metrics, NetFlow/sFlow traffic analysis, SNMP traps, and live topology into a single real-time, interactive view.Network Topology Mapping Explainedhttps://www.netdata.cloud/academy/network-topology-mapping/Wed, 24 Jun 2026 00:00:00 +0000https://www.netdata.cloud/academy/network-topology-mapping/<p>Network topology mapping is the process of discovering and visualizing how devices, endpoints, and services connect across a network. It captures both physical (Layer 2) relationships - which switch port links to which device - and logical (Layer 3) relationships - how subnets, routes, and autonomous systems reach each other. A topology map can range from a hand-drawn diagram to a live, continuously updated graph built from protocol data such as LLDP, CDP, ARP, FDB, OSPF, and BGP.</p>Real Time Network Monitoring: Topology, NetFlow, SNMPhttps://www.netdata.cloud/blog/network-monitoring/Wed, 24 Jun 2026 00:00:00 +0000https://www.netdata.cloud/blog/network-monitoring/<p>Interface counters tell you a port is busy. Bytes in, bytes out, errors, drops. That&rsquo;s enough to know a link is saturated, but not enough to know which conversations are saturating it, which devices are involved, or how a problem propagates across your network. For that you&rsquo;ve traditionally needed dedicated network performance monitoring tools, usually expensive, usually a separate console from the rest of your monitoring.</p> <p>Today we&rsquo;re closing that gap. Netdata has had solid network interface monitoring for a long time through its native collectors and SNMP support. We&rsquo;ve now built out the rest of the picture, and it adds up to NPM-class network monitoring: live network topology, NetFlow and sFlow traffic analysis, SNMP device monitoring across 200+ vendor profiles, SNMP trap handling, and a dedicated network monitoring dashboard. All of it runs alongside the infrastructure, application, and container metrics Netdata already collects, on the same timeline, in the same platform.</p>SNMP Monitoring Guide: How To Monitor Network Deviceshttps://www.netdata.cloud/academy/snmp-monitoring-guide/Wed, 24 Jun 2026 00:00:00 +0000https://www.netdata.cloud/academy/snmp-monitoring-guide/<p>To monitor SNMP devices you enable an SNMP agent on the device, open UDP/161 from the monitoring host, point your monitoring tool at the device with the correct credentials, and poll interface and health counters on a fixed interval. SNMP works by having a central manager query an agent that exposes numeric objects (OIDs) defined in MIBs, with optional push notifications (traps) for event-driven signals. The bulk of day-to-day network monitoring (interface utilization, errors, port state, CPU, memory) comes from periodic polling of those OIDs.</p>SNMP Traps vs Polling: What Is The Difference?https://www.netdata.cloud/academy/snmp-traps-vs-polling/Wed, 24 Jun 2026 00:00:00 +0000https://www.netdata.cloud/academy/snmp-traps-vs-polling/<p>SNMP polling is a pull model where a monitoring server periodically queries a device over UDP port 161 to read metrics and state. SNMP traps are a push model where the device itself sends an unsolicited notification over UDP port 162 the instant an event occurs. The two are not competing choices: mature network monitoring uses polling for continuous metrics and traps for immediate event alerts.</p> <h2 id="what-is-snmp-polling">What is SNMP polling?</h2> <p>Polling is the classic request-response model at the heart of SNMP-based monitoring. A central manager (your monitoring system) sends a GET, GETNEXT, or GETBULK request to an SNMP agent running on a router, switch, UPS, or other networked device. The agent responds with the requested values.</p>What Is NetFlow? Network Flow Monitoring Explainedhttps://www.netdata.cloud/academy/what-is-netflow/Wed, 24 Jun 2026 00:00:00 +0000https://www.netdata.cloud/academy/what-is-netflow/<p>NetFlow is a network protocol, originally developed by Cisco, for collecting metadata about IP traffic flows as they pass through a router, switch, or firewall. A flow is a unidirectional sequence of packets that share the same key fields - classically the 5-tuple of source IP, destination IP, source port, destination port, and protocol. NetFlow does not capture packet payloads; it exports compact metadata records that a collector stores and analyzes, giving you visibility into who is talking to whom, how much bandwidth they are using, and when.</p>5 Best SolarWinds Alternatives for 2026https://www.netdata.cloud/blog/solarwinds-alternatives-2026/Tue, 23 Jun 2026 00:00:00 +0000https://www.netdata.cloud/blog/solarwinds-alternatives-2026/<p>As organizations modernize their infrastructure and embrace cloud-native architectures, traditional monitoring solutions are showing their age. SolarWinds, while a long-established player in IT management, was designed for an era of static, on-premise infrastructure. In 2026, teams are seeking alternatives that can keep pace with dynamic, distributed systems—and they&rsquo;re finding better options.</p> <h2 id="what-is-solarwinds-is-it-still-the-right-choice">What Is SolarWinds? Is It Still The Right Choice?</h2> <p>SolarWinds Platform (formerly Orion) has been a cornerstone of IT monitoring for decades, offering comprehensive coverage of network devices, servers, applications, and databases. It&rsquo;s particularly strong in traditional enterprise environments with extensive hardware monitoring needs.</p>NetFlow Traffic Analyzerhttps://www.netdata.cloud/features/network/netflow-traffic-analyzer/Tue, 23 Jun 2026 00:00:00 +0000https://www.netdata.cloud/features/network/netflow-traffic-analyzer/Real-time NetFlow, IPFIX, and sFlow analysis with top talkers, Sankey diagrams, geographic traffic maps, and automatic GeoIP/ASN/NetBox enrichment — built into the Netdata Agent.Network Topology Viewerhttps://www.netdata.cloud/features/network/topology-viewer/Tue, 23 Jun 2026 00:00:00 +0000https://www.netdata.cloud/features/network/topology-viewer/Netdata Network Topology Viewer maps live TCP/UDP connections between processes, containers, and endpoints, plus SNMP device fabric via LLDP, CDP, BGP, and OSPF.SNMP & Network Device Monitoringhttps://www.netdata.cloud/features/network/network-device-monitoring/Tue, 23 Jun 2026 00:00:00 +0000https://www.netdata.cloud/features/network/network-device-monitoring/Real-time SNMP device monitoring with auto-matched vendor profiles, ML anomaly detection, and zero-config discovery.SNMP Trap Monitoringhttps://www.netdata.cloud/features/network/snmp-traps/Tue, 23 Jun 2026 00:00:00 +0000https://www.netdata.cloud/features/network/snmp-traps/Native SNMP trap receiver with MIB-resolved decoding, storm controls, health alerts, and SIEM forwarding — built into Netdata.SolarWinds Price Increases 2026: What Customers Need to Knowhttps://www.netdata.cloud/blog/solarwinds-price-increases-2026/Tue, 23 Jun 2026 00:00:00 +0000https://www.netdata.cloud/blog/solarwinds-price-increases-2026/<p>If you&rsquo;re a SolarWinds customer facing renewal, you&rsquo;ve likely noticed significant changes to pricing and licensing terms in 2024-2025. You&rsquo;re not alone. At Netdata, we&rsquo;ve been speaking with dozens of SolarWinds customers who are reassessing their monitoring strategies in light of these changes. This post provides factual information about what&rsquo;s changed, the real impact on organizations, and a practical framework for evaluating your path forward.</p> <h2 id="whats-happening-with-solarwinds-pricing">What&rsquo;s Happening with SolarWinds Pricing?</h2> <p>In February 2025, SolarWinds was acquired by private equity firm Turn/River Capital in a $4.4 billion transaction. As is common with PE-backed acquisitions, this has led to significant changes in pricing and business terms. Based on customer reports and public information, renewal prices have increased by 100-300% for many customers. One customer on the SolarWinds community forum reported their renewal more than doubled, a 225% increase from the previous year.</p>Grafana vs Datadog: The honest comparison in 2026https://www.netdata.cloud/comparisons/grafana-vs-datadog/Sat, 30 May 2026 00:00:00 +0000https://www.netdata.cloud/comparisons/grafana-vs-datadog/High Cardinality Metrics At Scale: A Better Playbookhttps://www.netdata.cloud/blog/high-cardinality-metrics-observability-scale/Sat, 30 May 2026 00:00:00 +0000https://www.netdata.cloud/blog/high-cardinality-metrics-observability-scale/<p>The &ldquo;high cardinality is expensive&rdquo; sentence has become observability&rsquo;s version of &ldquo;in this economy&rdquo;: said so often that nobody questions whether it&rsquo;s true. Every vendor pricing page invokes it. Every glossary article repeats it. Every architecture diagram shows aggregation buffers placed <em>before</em> the storage layer.</p> <!--truncate--> <p>&ldquo;High cardinality is expensive&rdquo; is not a fact about the universe; it&rsquo;s a fact about one architectural choice: centralizing time-series storage and querying it through an index that scales with unique series. Once you accept that choice, everything follows. You pay per metric, you drop labels you wish you&rsquo;d kept, you pre-aggregate before storage, and you discover that the bug you were debugging only existed at the full resolution you already threw away.</p>How To Reduce Alert Fatigue With Anomaly Detectionhttps://www.netdata.cloud/solutions/use-cases/alert-fatigue/Sat, 30 May 2026 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/alert-fatigue/Most alert-fatigue tools manage noise after the fact. Netdata prevents it by running 18 ML models per metric with consensus voting — anomalies only fire when multiple models agree, suppressing the false positives that drive on-call burnout.The best AI-powered observability platforms in 2026https://www.netdata.cloud/resources/best-ai-powered-observability-platforms/Sat, 30 May 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-ai-powered-observability-platforms/The best DevOps monitoring tools in 2026https://www.netdata.cloud/resources/best-devops-monitoring-tools/Sat, 30 May 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-devops-monitoring-tools/The Best Infrastructure Monitoring Tools In 2026https://www.netdata.cloud/resources/best-infrastructure-monitoring-tools/Sat, 30 May 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-infrastructure-monitoring-tools/The best open-source observability tools in 2026https://www.netdata.cloud/resources/best-open-source-observability-tools/Sat, 30 May 2026 00:00:00 +0000https://www.netdata.cloud/resources/best-open-source-observability-tools/Netdata Skills: Teach Your AI Coding Agent To Monitorhttps://www.netdata.cloud/blog/netdata-skills/Wed, 20 May 2026 00:00:00 +0000https://www.netdata.cloud/blog/netdata-skills/<p>There&rsquo;s a growing ecosystem of AI coding agents: Claude Code, Cursor, Copilot, Codex, Gemini CLI, Windsurf, and others. They&rsquo;re good at writing code, but they don&rsquo;t inherently know how to instrument that code for observability, configure monitoring infrastructure, or troubleshoot production systems using real telemetry data. That knowledge lives in documentation, runbooks, and the heads of your senior SREs.</p> <p>We&rsquo;ve open-sourced a repository that encodes this knowledge into a format AI agents can use directly. <a href="https://github.com/netdata/skills">netdata/skills</a> is a collection of agent skills, published in the open <a href="https://agentskills.io">agentskills.io</a> format, that teach AI coding agents how to set up Netdata, instrument applications with OpenTelemetry, build collector pipelines, troubleshoot 49 specific technologies, and verify everything against live data via MCP.</p>OpenTelemetry Backendhttps://www.netdata.cloud/opentelemetry/Wed, 20 May 2026 00:00:00 +0000https://www.netdata.cloud/opentelemetry/An open OTEL backend with native OTLP ingestion, per-second granularity, ML anomaly detection, and infrastructure correlation. Traces coming soon. No per-metric pricing. No vendor lock-in.OpenTelemetry and Netdata, Todayhttps://www.netdata.cloud/blog/opentelemetry-metrics-and-logs-ingestion/Fri, 15 May 2026 00:00:00 +0000https://www.netdata.cloud/blog/opentelemetry-metrics-and-logs-ingestion/<p>OpenTelemetry has become the default way to instrument applications and ship telemetry. The hard part has never been the data model. It&rsquo;s been picking a backend that handles OTLP without quietly turning into a per-metric bill or a black box that swallows your data.</p> <p>Netdata is a native OTLP backend. Stand up an OpenTelemetry Collector with any of its hundreds of receivers, point its OTLP exporter at Netdata, and you get per-second charts, ML anomaly detection on every signal, AI-assisted troubleshooting, and infrastructure correlation, with no per-metric, per-series, or per-host charges. Metrics and logs work today. Trace support is coming soon.</p>Dashboard Playlists: Cycle Through Dashboards in TV Modehttps://www.netdata.cloud/blog/dashboard-playlists/Tue, 12 May 2026 00:00:00 +0000https://www.netdata.cloud/blog/dashboard-playlists/<p>When we shipped TV mode, we heard almost immediately: &ldquo;Great, but I have five dashboards and one screen.&rdquo; A single dashboard on a wall display covers one view of your infrastructure. If you want to rotate between your network overview, database health, application metrics, and infrastructure summary, someone has to walk over and click, or you&rsquo;re buying more screens.</p> <p>Dashboard playlists solve this. You can now select a sequence of dashboards to cycle through in TV mode, with a configurable rotation interval. Set it up once, open the TV mode URL on your display, and the screen rotates through your chosen dashboards on its own.</p>Azure Local Migration: Monitor Both Sides In One Viewhttps://www.netdata.cloud/blog/azure-local-migration/Mon, 11 May 2026 00:00:00 +0000https://www.netdata.cloud/blog/azure-local-migration/<p><img src="../images/azure-local-migration.svg" alt="Monitoring Your Azure to Azure Local Migration: One Dashboard for Both Sides"></p> <p>More organizations are moving workloads from Azure public cloud to Azure Local (formerly Azure Stack HCI) than most people realize. The reasons vary: data sovereignty requirements, latency-sensitive workloads that need to be closer to the edge, cost optimization for predictable workloads where reserved cloud capacity doesn&rsquo;t make financial sense, or regulatory constraints that require data to stay on-premises.</p>Geo Maps: See Where Your Infrastructure Liveshttps://www.netdata.cloud/blog/geo-maps/Sat, 09 May 2026 00:00:00 +0000https://www.netdata.cloud/blog/geo-maps/<p>When your infrastructure is spread across regions, data centers, branch offices, or edge locations, knowing where a node is physically located matters more than people usually admit. During an incident, &ldquo;the node in the Singapore POP&rdquo; communicates faster than a hostname. When you&rsquo;re planning capacity, seeing geographic clustering tells you something that a flat list of nodes doesn&rsquo;t. When a subset of your fleet starts misbehaving, the first question is often &ldquo;is this regional?&rdquo;</p>NVIDIA DCGM Collector: Deep GPU Monitoring For AIhttps://www.netdata.cloud/blog/nvidia-dcgm-monitoring/Mon, 04 May 2026 00:00:00 +0000https://www.netdata.cloud/blog/nvidia-dcgm-monitoring/<p><img src="../images/dcgm-collector.svg" alt="NVIDIA DCGM Collector: Deep GPU Monitoring for Data Center and AI Infrastructure"></p> <p>GPU infrastructure is expensive and increasingly central to production workloads. Whether you&rsquo;re running ML training jobs, inference serving, video transcoding, or HPC workloads, understanding what your GPUs are actually doing, and what&rsquo;s going wrong when performance degrades, is not optional. The problem is that NVIDIA&rsquo;s Data Center GPU Manager (DCGM) exposes an enormous amount of telemetry, but getting that data into a monitoring system in a useful, organized way has traditionally required significant setup and custom dashboarding work.</p>Misconfigured Alert Detection: Tuning Made Easyhttps://www.netdata.cloud/blog/identifying-misconfigured-alerts/Tue, 28 Apr 2026 00:00:00 +0000https://www.netdata.cloud/blog/identifying-misconfigured-alerts/<p><img src="../images/miscon-alerts-1.png" alt="Misconfigured Alert Detection: Find the Alerts That Need Tuning"></p> <p>Netdata ships with hundreds of stock alerts. They cover a wide range of infrastructure conditions and they&rsquo;re designed with sensible defaults. But &ldquo;sensible defaults&rdquo; and &ldquo;correct for your environment&rdquo; are not the same thing. A CPU threshold that&rsquo;s perfectly reasonable for a build server might generate constant noise on a machine running batch jobs. An alert that&rsquo;s critical for production might be irrelevant in staging, where it fires daily and everyone ignores it.</p>Azure Monitor Collector: Monitor Azure Infrastructurehttps://www.netdata.cloud/blog/azure-monitor/Mon, 27 Apr 2026 00:00:00 +0000https://www.netdata.cloud/blog/azure-monitor/<p><img src="../images/azure-monitor-collector.svg" alt="Azure Monitor Collector: Monitor Your Entire Azure Infrastructure From Netdata"></p> <p>If you&rsquo;re running infrastructure on Azure, you&rsquo;ve probably dealt with the split between your Azure-native monitoring and the rest of your stack. Your VMs, databases, and Kubernetes clusters generate platform metrics through Azure Monitor, but those metrics live in a separate world from the OS-level, application, and on-prem metrics you&rsquo;re already watching in Netdata. You end up checking two (or more) places during incidents, building mental bridges between dashboards that don&rsquo;t talk to each other.</p>Database Performance Monitoring: 14+ DBs Supportedhttps://www.netdata.cloud/blog/dbm/Fri, 24 Apr 2026 00:00:00 +0000https://www.netdata.cloud/blog/dbm/<p><img src="../images/dbm-hero.svg" alt="Database Performance Monitoring: Query-Level Visibility Across 14+ Databases"></p> <p>Netdata has always collected database metrics: connections, throughput, replication lag, buffer cache hit ratios, and so on. These tell you that something is wrong, but they don&rsquo;t tell you why. When your PostgreSQL response time spikes, the metric alone doesn&rsquo;t tell you which query is responsible. For that, you&rsquo;ve traditionally needed to SSH into the box, connect to the database, and run diagnostic queries manually. Or set up a separate database monitoring tool entirely.</p>Nagios Plugins: Run Existing Checks & Custom Scriptshttps://www.netdata.cloud/blog/nagios-plugins/Wed, 22 Apr 2026 00:00:00 +0000https://www.netdata.cloud/blog/nagios-plugins/<p>A lot of teams have a collection of Nagios plugins and custom monitoring scripts that have been running reliably for years. Some are standard community plugins for checking disk health or SSL certificate expiry. Others are homegrown Bash or Python scripts that check something very specific to the business: whether an API endpoint returns the right payload, whether a batch job completed on time, whether a queue depth is within bounds. These scripts work, they&rsquo;re battle-tested, and nobody wants to rewrite them.</p>Secrets Management: Remove Credentials From Configshttps://www.netdata.cloud/blog/secrets-management/Mon, 20 Apr 2026 00:00:00 +0000https://www.netdata.cloud/blog/secrets-management/<p>If you&rsquo;re running Netdata collectors that connect to databases, APIs, or other authenticated services, there&rsquo;s a good chance you have passwords sitting in plain-text configuration files right now. It works, but it&rsquo;s the kind of thing that makes security teams nervous and makes credential rotation painful. Every password change means editing config files and restarting collectors.</p> <p>Netdata now supports secrets management natively. Instead of putting credentials directly in your collector configurations, you reference them using a resolver syntax, and Netdata resolves the actual values at runtime from whatever source you choose: environment variables, files on disk, the output of a command, or a centralized secret store like HashiCorp Vault or AWS Secrets Manager.</p>Netdata Complete Tutorial by LearnLinux.tvhttps://www.netdata.cloud/resources/netdata-tutorial/Thu, 16 Apr 2026 00:00:00 +0000https://www.netdata.cloud/resources/netdata-tutorial/LearnLinux.tv&rsquo;s Jay LaCroix built a complete video course on Netdata. Eight episodes taking you from first install to production best practices.Smarter Alerts: Test, Review & Preview Scheduleshttps://www.netdata.cloud/blog/smarter-alerts/Thu, 16 Apr 2026 00:00:00 +0000https://www.netdata.cloud/blog/smarter-alerts/<p>Alert fatigue usually isn&rsquo;t caused by one thing. It&rsquo;s the accumulation of thresholds that are slightly too sensitive, alerts that fire during known maintenance windows, and historical patterns that nobody has the tools to review easily. Fixing it requires better visibility into how alerts actually behave over time, and a way to test changes before they hit production.</p> <p>We&rsquo;ve shipped three improvements to alerting in Netdata that address different parts of this problem: the ability to evaluate alert definitions against historical data before deploying them, a timeline view of alert transitions, and a schedule preview for recurring silencing rules.</p>TV Mode: Put Your Dashboards on the Big Screenhttps://www.netdata.cloud/blog/tv-mode/Tue, 14 Apr 2026 00:00:00 +0000https://www.netdata.cloud/blog/tv-mode/<p>One of the most common requests we&rsquo;ve gotten since launching custom dashboards is deceptively simple: &ldquo;How do I put this on a TV?&rdquo; Teams want their dashboards on wall-mounted screens in NOCs, war rooms, and open office spaces. The dashboard is already built. The data is already there. They just need a way to display it on a screen that nobody is logged into, without exposing the full Netdata Cloud interface.</p>New Custom Dashboards: Metrics, Logs & Live Commandshttps://www.netdata.cloud/blog/new-custom-dashboards/Sun, 12 Apr 2026 00:00:00 +0000https://www.netdata.cloud/blog/new-custom-dashboards/<p>Custom dashboards in Netdata have always let you pull charts together on-the-fly into a single view. That&rsquo;s useful, but it&rsquo;s also limited. In practice, when you&rsquo;re running an incident or reviewing a service, you don&rsquo;t just want charts. You want to see the output of <code>top</code> alongside your CPU metrics. You want slow query logs next to your database latency charts. You want an infrastructure summary card that tells you how many nodes in a room are healthy without having to click through to find out.</p>Alert Acknowledgement: Mark It as Seen, Keep Workinghttps://www.netdata.cloud/blog/alert-acknowledge/Fri, 10 Apr 2026 00:00:00 +0000https://www.netdata.cloud/blog/alert-acknowledge/<p>If you&rsquo;ve ever opened the alerts tab during a busy period, you know the problem. There are alerts you&rsquo;ve already looked at, alerts someone on your team is handling, and alerts that fired on a known issue that&rsquo;s being worked on. They all sit together in the same list alongside the new ones you haven&rsquo;t seen yet. There&rsquo;s no way to say &ldquo;I&rsquo;ve seen this, move on&rdquo; without silencing or disabling the alert entirely, which is a much heavier action than the situation calls for.</p>Expanded Chart View: Investigate Without Leaving the Charthttps://www.netdata.cloud/blog/charts-expanded-view/Wed, 08 Apr 2026 00:00:00 +0000https://www.netdata.cloud/blog/charts-expanded-view/<p>Charts in Netdata have always been interactive. You can zoom, pan, select time ranges, and see per-second granularity across thousands of metrics. But when you spotted something interesting, the next steps usually meant leaving the chart: opening another tab to check a related metric, navigating to the correlation tool, or pulling up a different time range for comparison. The investigation workflow lived outside the chart, even though the chart was where the investigation started.</p>Monitor Your Azure to Azure Local Migrationhttps://www.netdata.cloud/solutions/use-cases/azure-local-migration/Wed, 08 Apr 2026 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/azure-local-migration/Netdata gives migration teams a single pane of glass across Azure cloud resources and Azure Local cluster nodes. Per-second metrics, edge-based ML, and 800+ collectors mean you can baseline source workloads, validate destination hardware, run parallel cutovers, and operate the new environment without changing tools.Conversations: Ask Netdata About Anything You're Looking Athttps://www.netdata.cloud/blog/converse-with-everything-in-netdata/Thu, 02 Apr 2026 00:00:00 +0000https://www.netdata.cloud/blog/converse-with-everything-in-netdata/<p>Netdata AI can already troubleshoot your alerts and generate Insights reports. What it couldn&rsquo;t do, until now, was have a back-and-forth conversation. You could get a one-shot analysis, but you couldn&rsquo;t ask follow-up questions, pull in additional context, or go from a quick question to a full investigation without starting over.</p> <p>We&rsquo;ve added a conversational layer to Netdata AI. You&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&rsquo;re in a conversation where the thing you clicked on is already the context. No copy-pasting metric names, no explaining what you&rsquo;re looking at.</p>Node Groups: Organize Infrastructure Into Viewshttps://www.netdata.cloud/blog/node-groups/Wed, 01 Apr 2026 00:00:00 +0000https://www.netdata.cloud/blog/node-groups/<p>When you&rsquo;re managing a handful of nodes, the flat list in the nodes tab works fine. When you&rsquo;re managing hundreds or thousands, it becomes a wall of hostnames. You end up applying the same filters repeatedly: all the production database servers, all the nodes in eu-west, all the Kubernetes workers in the staging cluster. The filters work, but they don&rsquo;t persist, and there&rsquo;s no way to share them with the rest of your team.</p>Netdata Product Roadmaphttps://www.netdata.cloud/roadmap/Fri, 13 Mar 2026 00:00:00 +0000https://www.netdata.cloud/roadmap/Netdata&rsquo;s product roadmap and strategic investment areas. From AI-native observability to full-stack signal coverage, see where Netdata is headed.Introducing the Netdata Cloud MCP Serverhttps://www.netdata.cloud/blog/netdata-cloud-mcp-server/Fri, 27 Feb 2026 00:00:00 +0000https://www.netdata.cloud/blog/netdata-cloud-mcp-server/<p>The Netdata Cloud MCP Server is now available — giving AI agents and assistants direct access to your Netdata through a single endpoint at <code>app.netdata.cloud/api/v1/mcp</code>.</p> <!--truncate--> <h2 id="ai-is-changing-how-we-monitor-infrastructure">AI Is Changing How We Monitor Infrastructure</h2> <p>If you&rsquo;re an engineer in 2026, chances are AI is already part of your daily workflow, whether that&rsquo;s a general-purpose assistant like ChatGPT, Claude, or Gemini that you bounce questions off, or a coding agent like <a href="https://docs.anthropic.com/en/docs/claude-code">Claude Code</a>, <a href="https://openai.com/codex/">Codex</a>, <a href="https://www.cursor.com/">Cursor</a>, or <a href="https://windsurf.com/">Windsurf</a> that writes and debugs code alongside you. These tools are incredibly powerful, but until now, they&rsquo;ve been blind to what&rsquo;s actually happening on your infrastructure.</p>Netdata for Homelabshttps://www.netdata.cloud/homelab/Wed, 18 Feb 2026 00:00:00 +0000https://www.netdata.cloud/homelab/Netdata&rsquo;s Homelab plan gives you enterprise-grade monitoring at a price that respects your hobby. Per-second metrics, ML anomaly detection, unlimited custom dashboards, and zero configuration — for $90/year.Howard Conference & Expo 2026: Smarter Observabilityhttps://www.netdata.cloud/blog/howard-expo-2026/Tue, 03 Feb 2026 00:00:00 +0000https://www.netdata.cloud/blog/howard-expo-2026/<p>The Netdata team will be at the <strong>Howard Conference and Expo &ldquo;Game On&rdquo;</strong> event, <strong>February 24-26, 2026 at the Grand Hotel Marriott Resort in Fairhope, Alabama</strong>. We&rsquo;re looking forward to meeting IT leaders and practitioners to talk about real-time observability—what it actually looks like in practice, and where traditional monitoring falls short.</p> <!--truncate--> <h2 id="what-well-be-showing">What We&rsquo;ll Be Showing</h2> <p>Stop by our booth to see Netdata in action and chat with our team about what you&rsquo;re dealing with in your own environment.</p>India DevOps Show 2026: Modern Observability Recaphttps://www.netdata.cloud/blog/india-devops-show-2026/Tue, 03 Feb 2026 00:00:00 +0000https://www.netdata.cloud/blog/india-devops-show-2026/<p>DevOps has fundamentally transformed how organizations build and deliver software. But as deployment velocity increases and infrastructure becomes more dynamic, the gap between shipping code and truly understanding system behavior continues to widen. Teams need observability that keeps pace with their pipelines, not tools that slow them down or break the budget.</p> <p>Netdata is proud to participate as a <strong>Silver Partner</strong> at the <strong>10th Edition India DevOps Show 2026</strong>, taking place on <strong>February 13, 2026 at Aloft ORR Hotel, Bengaluru</strong>. We&rsquo;re excited to engage with India&rsquo;s vibrant DevOps community and share our vision for efficient, intelligent observability.</p>Tech Show London 2026: Cloud & AI Observability Recaphttps://www.netdata.cloud/blog/techshow-london-2026/Tue, 03 Feb 2026 00:00:00 +0000https://www.netdata.cloud/blog/techshow-london-2026/<p>The intersection of cloud and AI is creating unprecedented infrastructure complexity. As organizations race to deploy AI workloads alongside traditional cloud services, the demand for intelligent, high-fidelity observability has never been greater. Understanding what&rsquo;s happening across your entire stack, in real time, is no longer a luxury, it&rsquo;s a necessity.</p> <p>That&rsquo;s why the Netdata team is excited to be part of <strong>Tech Show London 2025</strong>, taking place <strong>March 4-5 at ExCeL London</strong>. We&rsquo;ll be in the <strong>Cloud &amp; AI Infrastructure</strong> zone, ready to show you how modern observability should work.</p>Database Monitoring Software Without Query Languageshttps://www.netdata.cloud/solutions/built-for/dbas/Tue, 27 Jan 2026 00:00:00 +0000https://www.netdata.cloud/solutions/built-for/dbas/Netdata gives DBAs complete database visibility with per-second query performance, replication lag tracking, lock analysis, and connection pool monitoring across MySQL, PostgreSQL, SQL Server, Oracle, and MongoDB - all from one dashboard with zero configuration.Netdata vs ScienceLogic | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/sciencelogic/Wed, 14 Jan 2026 00:00:00 +0000https://www.netdata.cloud/comparisons/sciencelogic/Comprehensive comparison of Netdata and ScienceLogic Skylar One platforms, highlighting real-time per-second visibility, transparent pricing, and zero-configuration deployment advantages over enterprise-focused 5-minute polling.Netdata vs SolarWinds | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/solarwinds/Tue, 30 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/solarwinds/Introducing Real-Time Conversations with Netdata AIhttps://www.netdata.cloud/blog/ai-conversations/Tue, 23 Dec 2025 00:00:00 +0000https://www.netdata.cloud/blog/ai-conversations/<p>Over the past few months, we&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.</p> <p>But what about the moments <em>during</em> an investigation? What about the rapid-fire &ldquo;what if&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.</p>Update Your Netdata Agenthttps://www.netdata.cloud/please-update-your-agent/Fri, 19 Dec 2025 00:00:00 +0000https://www.netdata.cloud/please-update-your-agent/About Ushttps://www.netdata.cloud/about/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/about/Meet the team behind Netdata - engineers who transformed observability by distributing intelligence to the edge, making infrastructure transparent for teams worldwide.Access Control: Secure Observability Without Riskhttps://www.netdata.cloud/features/enterprise/access-control/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/enterprise/access-control/Secure your observability infrastructure with Netdata&rsquo;s edge-native access control: granular RBAC, automated SSO provisioning, true multi-tenancy through Spaces and Rooms, comprehensive audit logging, and SOC 2 Type 2 certification - all while keeping your data on your infrastructure.AI Co-Engineer For Instant Root Cause Insightshttps://www.netdata.cloud/features/aiml/ai-co-engineer/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/aiml/ai-co-engineer/Netdata&rsquo;s AI Co-Engineer combines edge-native machine learning with flexible AI integration, providing instant expert-level insights while keeping your data sovereign and secure.AI Reporting Software For Observability Datahttps://www.netdata.cloud/features/aiml/reporting/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/aiml/reporting/Generate professional infrastructure reports in minutes, not hours. Netdata&rsquo;s AI reporting delivers automated insights across metrics, logs, and alerts - from capacity planning to root cause analysis - with zero configuration and complete data sovereignty.AIOps Platform: Edge-Native ML, Zero Configurationhttps://www.netdata.cloud/features/aiml/aiops/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/aiml/aiops/Enterprise AIOps intelligence without enterprise complexity. Edge-native ML, automated insights, and transparent pricing deliver operational excellence from day one.Algorithmic Dashboards For Every Metrichttps://www.netdata.cloud/features/architecture/algorithmic-dashboards/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/architecture/algorithmic-dashboards/Netdata&rsquo;s algorithmic dashboards transform observability from a months-long configuration project into instant, comprehensive visibility. Every metric visualized automatically, every relationship revealed through intelligent point-and-click analysis, every engineer productive from day one.Anomaly Advisor: Root Cause In Seconds, Not Hourshttps://www.netdata.cloud/features/aiml/anomaly-advisor/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/aiml/anomaly-advisor/Netdata Anomaly Advisor uses edge-native machine learning with 18-model consensus to eliminate 99% of false positives while surfacing root causes in the top 30-50 metrics from thousands collected. Get sub-2-second correlation analysis at any scale without configuration, training delays, or specialist expertise.Anomaly Detection Software: 99% Fewer False Positiveshttps://www.netdata.cloud/features/aiml/anomaly-detection/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/aiml/anomaly-detection/Production-ready ML anomaly detection from installation. 18 consensus models per metric achieve 99% false positive reduction in anomaly detection while catching issues competitors miss. Zero configuration. Zero false promises.Anomaly Detection With 99% Fewer False Positiveshttps://www.netdata.cloud/features/aiml/machine-learning/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/aiml/machine-learning/Netdata trains 18 independent ML models per metric at the edge, achieving 99% false positive reduction in anomaly detection through unanimous consensus - all included at no additional cost.Application Performance Monitoring Softwarehttps://www.netdata.cloud/solutions/use-cases/application-performance/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/application-performance/Netdata revolutionizes application performance monitoring with distributed edge intelligence, zero-configuration deployment, and AI-powered troubleshooting that delivers enterprise-grade observability at a fraction of traditional APM costs.AWS Monitoring Software With 1 Second Visibilityhttps://www.netdata.cloud/solutions/technologies/aws-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/technologies/aws-monitoring/Netdata delivers true real-time AWS monitoring with 1-second granularity, ML-powered anomaly detection, and predictable per-node pricing - eliminating CloudWatch&rsquo;s complexity and cost unpredictability.Azure Monitoring Tool With Real-Time Visibilityhttps://www.netdata.cloud/solutions/technologies/azure-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/technologies/azure-monitoring/Netdata delivers true real-time Azure monitoring with per-second granularity, 90% lower costs, and zero learning curve. Monitor Azure VMs, containers, databases, and applications with automated dashboards, ML anomaly detection, and AI-powered root cause analysis.Blast Radius Detection For Faster Incident Responsehttps://www.netdata.cloud/features/aiml/blast-radius-detection/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/aiml/blast-radius-detection/Netdata reveals blast radius dynamically through real-time anomaly correlation and ML-powered pattern recognition, showing the complete story from first failure to full impact in seconds.Built-In MCP For AI Assistants To Query Metrics & Logshttps://www.netdata.cloud/features/aiml/mcp/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/aiml/mcp/Transform infrastructure troubleshooting with AI assistants that understand your systems. Netdata&rsquo;s built-in MCP server provides real-time metrics, ML anomaly detection, logs, and live system state - all accessible through natural language queries.Cloud Monitoring Software With Real-Time Metrics & AIhttps://www.netdata.cloud/solutions/use-cases/cloud-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/cloud-monitoring/Transform cloud operations with Netdata&rsquo;s distributed observability platform. Get per-second insights, AI-powered troubleshooting, and predictable costs - all while keeping your data sovereign.Cloud On-Premises Solution With Complete Observabilityhttps://www.netdata.cloud/product/cloud-on-premises/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/product/cloud-on-premises/Self-hosted Netdata Cloud for air-gapped environments and regulated industries. Complete control plane within your datacenter, zero external dependencies, full feature parity with SaaS. SOC 2 Type 2 certified observability that meets DORA, NIS2, HIPAA, and FedRAMP requirements by design.Container Monitoring Software With Zero Configurationhttps://www.netdata.cloud/solutions/use-cases/container-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/container-monitoring/Transform container monitoring with Netdata&rsquo;s edge-native platform. Get per-second metrics, automated dashboards, ML anomaly detection, and AI troubleshooting - all without complex setup or unpredictable costs.Custom Dashboards With Real-Time Precisionhttps://www.netdata.cloud/features/visualization/custom-dashboards/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/visualization/custom-dashboards/Netdata&rsquo;s algorithmic dashboards eliminate the false choice between pre-built rigidity and custom complexity. Each chart is a complete analytical tool equivalent to 25+ Grafana charts, providing 360° views with simple point-and-click. No query languages. No dashboard building. No maintenance burden.Data Center Monitoring Software With Real-Time Metricshttps://www.netdata.cloud/solutions/use-cases/datacenters/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/datacenters/Transform data center operations with Netdata&rsquo;s real-time monitoring platform. Per-second metrics, automated ML anomaly detection, and AI-powered troubleshooting deliver 80% faster MTTR at 90% lower cost than traditional solutions.Data Sovereignty With Metadata-Only Cloudhttps://www.netdata.cloud/features/enterprise/data-sovereignty/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/enterprise/data-sovereignty/Netdata delivers complete observability while keeping every metric and log exactly where you need it: on your infrastructure, in your jurisdiction, under your control. Meet GDPR, NIS2, DORA, and HIPAA requirements through architecture, not configuration.Database Monitoring Software With Real-Time Visibilityhttps://www.netdata.cloud/solutions/use-cases/database-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/database-monitoring/Real-time database monitoring with AI-powered troubleshooting, zero configuration, and predictable costs. Monitor 15+ database platforms with per-second granularity and ML-based anomaly detection.DevOps Monitoring Software With ML Anomaly Detectionhttps://www.netdata.cloud/solutions/built-for/devops/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/built-for/devops/Netdata delivers complete observability for DevOps teams with per-second metrics, zero-configuration deployment, and AI-powered root cause analysis. Monitor everything from bare metal to Kubernetes with a single platform that replaces 7 tools while reducing costs by 90%.Distributed Observability For Scale, Speed & Controlhttps://www.netdata.cloud/features/dataplatform/metrics-management/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/dataplatform/metrics-management/Collect unlimited metrics at per-second granularity with zero configuration. Netdata&rsquo;s edge-native architecture eliminates cardinality cost traps while delivering ML-based anomaly detection on every metric.Distributed Observability Without Centralized Pipelineshttps://www.netdata.cloud/features/architecture/distributed-observability-data-pipeline/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/architecture/distributed-observability-data-pipeline/Netdata&rsquo;s distributed architecture processes observability data at the edge, eliminating centralized bottlenecks while delivering per-second insights, automatic ML anomaly detection, and 90% cost reduction compared to traditional pipeline solutions.eBPF Network Monitoring With Real-Time Insightshttps://www.netdata.cloud/features/dataplatform/ebpf-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/dataplatform/ebpf-monitoring/Get kernel-level network insights - bandwidth, connections, retransmissions - embedded in your infrastructure observability platform. Zero eBPF expertise required. Zero configuration. Zero surprise bills.Edge Observability Without Cloud Dependencyhttps://www.netdata.cloud/features/architecture/edge-computing/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/architecture/edge-computing/Monitor thousands of edge nodes with per-second precision, &lt;5% CPU overhead, and 90% cost reduction. Netdata&rsquo;s edge-native architecture delivers complete visibility with autonomous operation, local ML, and zero configuration.Eliminate Log Pipelines: Native Log Query At Scalehttps://www.netdata.cloud/features/dataplatform/zero-pipeline-logs/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/dataplatform/zero-pipeline-logs/Netdata&rsquo;s Zero Pipeline Logs architecture eliminates traditional log aggregation pipelines by leveraging native system formats. Query logs directly where they live - no shipping, parsing, or indexing required - achieving 90% cost reduction and sub-2-second latency at any scale.Enterprise Monitoring At Scale Without Bottleneckshttps://www.netdata.cloud/features/architecture/infinite-scalability/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/architecture/infinite-scalability/Experience observability that grows naturally with your infrastructure - no rewrites, no bottlenecks, no compromise. Monitor everything, everywhere, at per-second resolution with predictable costs that scale with nodes, not data volume.Financial Transaction Monitoring Softwarehttps://www.netdata.cloud/solutions/industries/finance/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/industries/finance/Transform financial services operations with per-second monitoring, AI-powered troubleshooting, and zero-pipeline logs. Built for compliance, optimized for performance, designed for lean teams.Gaming Infrastructure Monitoring & Observabilityhttps://www.netdata.cloud/solutions/industries/gaming/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/industries/gaming/Netdata delivers true real-time monitoring for gaming infrastructure with per-second metrics, edge-based ML anomaly detection, and AI-powered troubleshooting - enabling lean teams to maintain 99.9% uptime while reducing monitoring costs by 90%.GCP Monitoring Tool With Per-Second Visibilityhttps://www.netdata.cloud/solutions/technologies/gcp-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/technologies/gcp-monitoring/Netdata delivers true real-time GCP monitoring with per-second granularity, zero-configuration deployment, and predictable per-node pricing - solving the cost unpredictability and complexity that plague organizations.Hetzner Monitoring With Real-Time Observabilityhttps://www.netdata.cloud/solutions/technologies/hetzner-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/technologies/hetzner-monitoring/Complete monitoring solution for Hetzner infrastructure with 1-second granularity, automated hardware health tracking, and AI-powered troubleshooting. Eliminates native monitoring gaps while reducing costs by 90%.High Cardinality Protection For Unlimited Metricshttps://www.netdata.cloud/features/architecture/extreme-cardinality/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/architecture/extreme-cardinality/Automated multi-layer protection handles extreme cardinality at the edge, enabling unlimited observability without manual tuning or cost explosions.HPC Monitoring Software With Per-Second Metricshttps://www.netdata.cloud/solutions/use-cases/hpc/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/hpc/Transform HPC operations with distributed edge-native monitoring that delivers sub-2-second insights, 90% cost reduction, and linear scalability to 100,000+ nodes - without the complexity.Hybrid Cloud Monitoring Solution At 90% Lower Costhttps://www.netdata.cloud/solutions/use-cases/hybrid-cloud-observability/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/hybrid-cloud-observability/Transform hybrid cloud monitoring with Netdata&rsquo;s distributed edge-native architecture. Get per-second visibility, ML-powered insights, and 90% cost savings without pipelines, sampling, or vendor lock-in.Infrastructure Health Monitoring Softwarehttps://www.netdata.cloud/solutions/industries/healthcare/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/industries/healthcare/Netdata delivers HIPAA-compliant, real-time observability for healthcare with 90% cost savings, per-second monitoring, and zero-configuration deployment. Monitor EHRs, medical devices, and critical infrastructure with edge-based ML and complete data sovereignty.Infrastructure Monitoring Software With AI & MLhttps://www.netdata.cloud/solutions/use-cases/infrastructure-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/infrastructure-monitoring/Transform infrastructure monitoring with Netdata&rsquo;s edge-native platform. Get per-second visibility, ML anomaly detection on every metric, and AI-powered troubleshooting - all while keeping your data sovereign and reducing costs by 90%.Infrastructure Observability Without Instrumentationhttps://www.netdata.cloud/features/enterprise/zero-code-instrumentation/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/enterprise/zero-code-instrumentation/Complete infrastructure visibility without touching code. Netdata monitors processes, containers, networks, and logs automatically through kernel-level instrumentation and intelligent auto-discovery.Instant Observability UI For Every Engineerhttps://www.netdata.cloud/product/netdata-ui/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/product/netdata-ui/Algorithmic dashboards, ML-powered insights, and point-and-click analysis that turns 100,000+ metrics into actionable intelligence in seconds.IoT Monitoring Solution With Full Data Sovereigntyhttps://www.netdata.cloud/solutions/use-cases/iot-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/iot-monitoring/Real-time IoT monitoring with per-device metrics, ML-powered anomaly detection, and transparent pricing. Monitor thousands of sensors, gateways, and edge devices with &lt;2s latency.Join Ushttps://www.netdata.cloud/join-us/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/join-us/Build infrastructure observability at massive scale with Netdata. Remote-first culture, open source core, 76K+ GitHub stars. Own the full stack, ship code used by millions, work with world-class engineers.Kubernetes Monitoring Tool Without Centralized Datahttps://www.netdata.cloud/solutions/technologies/kubernetes-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/technologies/kubernetes-monitoring/Transform Kubernetes observability with Netdata&rsquo;s edge-native architecture. Get per-second visibility, ML anomaly detection on every metric, and AI-powered root cause analysis - all at 90% lower cost than traditional solutions.Linux Monitoring Software With Per-Second Metricshttps://www.netdata.cloud/solutions/technologies/linux-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/technologies/linux-monitoring/Netdata delivers complete Linux monitoring with per-second granularity, edge-based ML anomaly detection, and zero-pipeline logs - all with zero configuration and predictable per-node pricing.Live Tab - Real-Time Netdata Functionshttps://www.netdata.cloud/features/visualization/live/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/visualization/live/The Live tab provides real-time access to Netdata Functions - specialized routines from collectors that deliver live information from your monitored nodes, including database monitoring, network topology maps, process explorers, and diagnostics.LLM Monitoring Platform With Per-Second Visibilityhttps://www.netdata.cloud/solutions/use-cases/llm-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/llm-monitoring/Real-time infrastructure monitoring for LLM deployments. Track GPU utilization, container resources, database performance, and system metrics with per-second granularity and ML-powered anomaly detection.Log Management Software With 90% Cost Reductionhttps://www.netdata.cloud/features/dataplatform/logs-management/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/dataplatform/logs-management/Eliminate expensive log pipelines and centralized clusters. Netdata queries systemd-journal and Windows Event Logs directly at the edge, delivering 90% cost savings, sub-second queries, and complete data sovereignty - all while maintaining superior analysis accuracy than traditional platforms.Manufacturing Monitoring Software Without Downtimehttps://www.netdata.cloud/solutions/industries/manufacturing/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/industries/manufacturing/Transform manufacturing operations with distributed observability that processes data at the edge. Monitor production metrics, predict equipment failures, and troubleshoot issues 80% faster - all while keeping costs predictable and data sovereign.Microservices Monitoring Tool Without Samplinghttps://www.netdata.cloud/solutions/use-cases/microservices-observability/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/microservices-observability/Netdata delivers comprehensive microservices observability with per-second metrics, ML-based anomaly detection, and AI-powered troubleshooting - all without the complexity, cost overruns, or tool sprawl that plague traditional solutions.Monitoring Agents For Accurate Production Insightshttps://www.netdata.cloud/product/netdata-agents/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/product/netdata-agents/Discover how Netdata Agents revolutionize infrastructure monitoring with edge-native intelligence, per-second granularity, and zero-configuration deployment. Complete observability in 60 seconds.MSP Monitoring Software With Multi-Tenant Isolationhttps://www.netdata.cloud/solutions/built-for/msp/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/built-for/msp/Netdata delivers the most cost-effective, scalable observability platform for MSPs - solving tool sprawl, alert fatigue, and unpredictable costs with true real-time monitoring, physical multi-tenancy, and edge-based ML.Multi-Cloud Monitoring Tools With Predictable Pricinghttps://www.netdata.cloud/solutions/use-cases/multi-cloud-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/multi-cloud-monitoring/Break free from fragmented multi-cloud monitoring. Netdata delivers unified per-second visibility across AWS, Azure, GCP, and on-premises with edge-native ML, zero configuration, and transparent per-node pricing - eliminating tool sprawl and surprise bills.Multi-Tenant Observability Access Without Data Egresshttps://www.netdata.cloud/features/dataplatform/alerts-notifications/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/dataplatform/alerts-notifications/Edge-intelligent alerting that delivers component-level precision through 400+ pre-configured templates, zero-configuration deployment, and sub-2-second evaluation latency - all while maintaining visibility during network partitions.Native iOS & Android Apps With AI Troubleshootinghttps://www.netdata.cloud/product/mobile-apps/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/product/mobile-apps/Transform on-call monitoring with Netdata&rsquo;s mobile apps for iOS and Android. Get push notifications for infrastructure alerts, AI-powered root cause analysis, and real-time dashboard access - all at a fixed, predictable price that includes mobile access for your entire team.Netdata Parents For Intelligent Observabilityhttps://www.netdata.cloud/product/netdata-parents/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/product/netdata-parents/Streaming aggregators that centralize data from thousands of nodes while keeping intelligence distributed at the edge. Handle million metrics per second with minimal resources, active-active clustering for high availability, and ML-powered insights without centralized bottlenecks.Netdata vs Amazon CloudWatch | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/cloudwatch/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/cloudwatch/Netdata provides 90% cost reduction vs CloudWatch with superior real-time monitoring (1-second vs 1-60 minutes), comprehensive ML on all metrics, and zero-configuration simplicity. Deploy in 60 seconds and eliminate CloudWatch&rsquo;s unpredictable costs while gaining better visibility.Netdata vs Azure Monitor | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/azuremonitor/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/azuremonitor/Netdata vs BetterStack | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/betterstack/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/betterstack/Netdata and BetterStack serve different observability needs. Netdata excels at deep infrastructure monitoring with per-second metrics and ML intelligence, while BetterStack focuses on incident coordination and uptime monitoring. Learn which solution fits your technical requirements.Netdata vs CardinalHQ | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/cardinalhq/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/cardinalhq/Comprehensive comparison of Netdata&rsquo;s edge-native monitoring platform versus CardinalHQ&rsquo;s AI-powered observability optimization layer. Learn which solution fits your infrastructure needs.Netdata vs Catchpoint | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/catchpoint/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/catchpoint/Netdata delivers real-time infrastructure visibility with per-second metrics, ML-based anomaly detection, and AI-powered troubleshooting - the essential internal monitoring layer that external testing platforms cannot provide.Netdata vs Checkmk | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/checkmk/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/checkmk/Netdata vs Checkmk comparison: Real-time monitoring (1-second vs 60-second), zero configuration (vs 700+ rule sets), AI-powered troubleshooting, 90% cost reduction, and operational simplicity. See why cloud-native teams choose Netdata for modern infrastructure monitoring.Netdata vs Coralogix | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/coralogix/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/coralogix/Netdata and Coralogix serve complementary observability needs. While Coralogix excels at centralized log analytics and SIEM, Netdata provides unmatched real-time infrastructure monitoring with per-second granularity, zero-configuration deployment, and transparent per-node pricing. Learn how Netdata addresses common Coralogix pain points including steep learning curves, slow production rollouts, unpredictable costs, and UI performance issues.Netdata vs Coroot | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/coroot/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/coroot/Netdata vs Coroot comparison: production-ready observability platform vs emerging Kubernetes tool. Learn why Netdata provides superior maturity, universal coverage, and operational simplicity for real-world infrastructure.Netdata vs Cribl | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/cribl/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/cribl/Netdata provides real-time infrastructure monitoring with ML-based anomaly detection and built-in dashboards. Cribl optimizes log pipelines and routes data for cost efficiency. Learn how these complementary solutions work together for complete observability.Netdata vs Dash0 | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/dash0/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/dash0/Netdata vs Dash0: Real-time edge intelligence with predictable pricing versus OpenTelemetry-native centralized monitoring. Compare features, costs, and capabilities to choose the right observability platform.Netdata vs Datadog | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/datadog/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/datadog/Netdata vs Dynatrace | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/dynatrace/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/dynatrace/Netdata provides superior infrastructure monitoring at a fraction of Dynatrace&rsquo;s cost, with true per-second granularity and complete data sovereignty. Learn when to use each platform and how a hybrid approach delivers complete observability at significantly lower total cost.Netdata vs EdgeDelta | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/edgedelta/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/edgedelta/Complete edge-native observability vs telemetry pipelines. See how Netdata provides real-time monitoring, ML-powered insights, and automated dashboards without the complexity of data routing infrastructure.Netdata vs ELK Stack | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/elk/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/elk/A comprehensive comparison between Netdata and the ELK Stack for infrastructure monitoring and observability. Learn which solution fits your real-time monitoring, log management, and troubleshooting needs.Netdata vs Fluentd | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/fluentd/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/fluentd/Netdata provides complete real-time observability with metrics, logs, ML anomaly detection, and AI troubleshooting in a single platform. Fluentd excels at log collection and routing. Learn how they complement each other and when Netdata replaces entire monitoring stacks.Netdata vs Grafana | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/grafana/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/grafana/Comprehensive comparison of Netdata and Grafana monitoring platforms, highlighting real-time performance, cost efficiency, and operational simplicity.Netdata vs Graylog | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/graylog/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/graylog/Netdata and Graylog serve different but complementary purposes in modern observability stacks. Netdata provides real-time infrastructure metrics monitoring with ML-based anomaly detection, while Graylog offers centralized log management for security analysis and forensic investigations. Together, they deliver complete observability.Netdata vs Grepr | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/grepr/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/grepr/Netdata vs Guance | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/guance/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/guance/Netdata vs HetrixTools | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/hetrixtools/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/hetrixtools/When HetrixTools alerts you&rsquo;re down, Netdata shows you why. Compare external uptime monitoring with internal infrastructure observability powered by ML and AI.Netdata vs Honeycomb | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/honeycomb/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/honeycomb/Compare Netdata and Honeycomb for infrastructure monitoring. Learn how Netdata provides comprehensive system visibility, predictable per node pricing, and zero-configuration deployment—solving the gaps in Honeycomb&rsquo;s application-centric observability.Netdata vs IBM Instana | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/instana/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/instana/Netdata vs Icinga | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/icinga/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/icinga/Comprehensive comparison of Netdata and Icinga monitoring platforms, highlighting real-time performance analysis, automated deployment, ML-based anomaly detection, and modern observability capabilities.Netdata vs Lansweeper | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/lansweeper/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/lansweeper/Netdata vs Last9 | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/last9/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/last9/Netdata vs LibreNMS | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/librenms/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/librenms/Compare Netdata and LibreNMS monitoring platforms. Learn how Netdata delivers per-second real-time monitoring, AI-powered anomaly detection, and native Windows support while LibreNMS excels at SNMP network device monitoring.Netdata vs LogicMonitor | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/logicmonitor/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/logicmonitor/Comprehensive comparison of Netdata and LogicMonitor monitoring platforms, highlighting real-time performance, cost efficiency, and deployment simplicity advantages.Netdata vs Logz.io | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/logz/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/logz/Netdata provides real-time, edge-native observability with predictable per-node pricing and zero-configuration deployment. Unlike Logz.io&rsquo;s centralized log aggregation model with volume-based billing, Netdata distributes intelligence to your systems - delivering 90% cost reduction, 80% faster MTTR, and complete data sovereignty.Netdata vs ManageEngine | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/manageengine/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/manageengine/Netdata vs ManageEngine: Real-time observability comparison for cloud-native infrastructure. See how per-second monitoring, distributed architecture, and zero-config deployment transform operations.Netdata vs Mezmo | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/mezmo/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/mezmo/Comprehensive comparison of Netdata and Mezmo observability platforms, highlighting real-time monitoring capabilities, cost efficiency, and deployment simplicity.Netdata vs Monit | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/monit/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/monit/Compare Netdata&rsquo;s real-time observability platform with Monit&rsquo;s lightweight process supervision. Learn how Netdata provides per-second monitoring, ML anomaly detection, AI troubleshooting, and unlimited scalability versus Monit&rsquo;s basic service checks and 1,000-host ceiling.Netdata vs N-able: Real-Time Monitoring Comparisonhttps://www.netdata.cloud/comparisons/nable/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/nable/Netdata provides per-second infrastructure monitoring with ML-based anomaly detection and AI troubleshooting - capabilities N-able&rsquo;s 5-10 minute intervals and basic dashboards can&rsquo;t match. See how Netdata solves the monitoring gaps N-able customers experience daily.Netdata vs Nagios | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/nagios/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/nagios/Netdata vs Netmon: Real-Time Observability Comparedhttps://www.netdata.cloud/comparisons/netmon/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/netmon/Netdata transforms infrastructure monitoring with real-time per-second data collection, ML-based anomaly detection, and AI-powered troubleshooting - replacing traditional appliance-based solutions with modern cloud-native observability.Netdata vs New Relic | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/newrelic/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/newrelic/Netdata vs Observium | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/observium/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/observium/Netdata vs Observium comparison: Real-time full-stack observability with ML and AI versus SNMP-based network device monitoring. See how Netdata&rsquo;s distributed architecture, per-second granularity, and automated intelligence deliver comprehensive infrastructure visibility that network-only monitoring cannot provide.Netdata vs Prometheus: No PromQL Complexityhttps://www.netdata.cloud/comparisons/prometheus/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/prometheus/Netdata vs Prometheus comparison: Real-time monitoring with zero configuration, built-in ML, and 90% lower costs. See how Netdata solves Prometheus pain points while maintaining enterprise-grade capabilities.Netdata vs PRTG | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/prtg/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/prtg/Netdata vs Rakuten SixthSense | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/rakuten/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/rakuten/Netdata provides per-second real-time infrastructure monitoring with AI-powered troubleshooting for 90% less than traditional APM tools. Compare features, pricing, and capabilities to see why infrastructure teams choose Netdata over Rakuten SixthSense.Netdata vs Sensu | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/sensu/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/sensu/Netdata vs Sensu: Real-time monitoring that just works vs a platform in decline. See why thousands of teams are switching to Netdata for instant deployment, beautiful dashboards, and 90% cost savings.Netdata vs Sentry | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/sentry/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/sentry/Netdata and Sentry serve different but complementary purposes in modern observability. Netdata provides real-time infrastructure monitoring with ML-based anomaly detection, while Sentry excels at application error tracking. Learn how using both tools together delivers complete visibility at lower total cost.Netdata vs SigLens | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/siglens/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/siglens/Comprehensive comparison of Netdata and SigLens observability platforms. Learn how these complementary tools work together to provide complete infrastructure monitoring and log analysis at a fraction of traditional enterprise costs.Netdata vs SigNoz | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/signoz/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/signoz/Comprehensive comparison of Netdata and SigNoz observability platforms, highlighting operational simplicity, real-time performance, and cost efficiency for infrastructure monitoring teams.Netdata vs Splunk | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/splunk/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/splunk/Netdata vs StackState | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/stackstate/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/stackstate/Real-time monitoring in 60 seconds vs months of topology setup. Netdata provides per-second observability, ML anomaly detection, and AI troubleshooting at 90% lower cost - perfect for lean teams who need comprehensive monitoring without enterprise complexity.Netdata vs Sumo Logic | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/sumologic/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/sumologic/Comprehensive comparison of Netdata and Sumo Logic: real-time monitoring, pricing models, deployment complexity, and use cases. Learn which platform fits your DevOps and observability needs.Netdata vs Uptime Kuma | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/uptimekuma/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/uptimekuma/Netdata vs UptimeRobot | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/uptimerobot/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/uptimerobot/Netdata and UptimeRobot serve different purposes: UptimeRobot monitors external availability while Netdata provides deep infrastructure diagnostics. Learn when to use each tool and how Netdata&rsquo;s component-level alerts and ML-based anomaly detection provide deeper visibility.Netdata vs VictoriaMetrics | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/victoriametrics/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/victoriametrics/Comprehensive comparison of Netdata vs VictoriaMetrics covering real-time monitoring, ML anomaly detection, visualization, scalability, and total cost of ownership.Netdata vs Virtana: Real-Time Operations Monitoringhttps://www.netdata.cloud/comparisons/virtana/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/virtana/Netdata delivers per-second operational monitoring for engineering teams, while Virtana provides strategic cost optimization for IT executives. Learn how these complementary platforms serve different needs within modern organizations.Netdata vs WhatsUp Gold | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/whatsup-gold/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/whatsup-gold/Netdata vs WhatsUp Gold: Real-time observability with per-second granularity, zero configuration, and built-in ML/AI vs traditional Windows-centric network monitoring. See how Netdata delivers 90% cost reduction and 80% faster MTTR for modern infrastructure.Netdata vs Zabbix | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/zabbix/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/zabbix/Netdata vs Zenoss | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/zenoss/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/zenoss/Comprehensive comparison of Netdata and Zenoss monitoring platforms, highlighting Netdata&rsquo;s advantages in real-time performance, ease of use, resource efficiency, and transparent pricing.Network Monitoring Software For Educationhttps://www.netdata.cloud/solutions/industries/education/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/industries/education/Netdata delivers comprehensive observability for educational institutions with zero-configuration deployment, complete data sovereignty, and 90% cost savings. Monitor everything from learning management systems to research clusters with per-second precision.Observability Cost Control With Per-Node Pricinghttps://www.netdata.cloud/features/enterprise/cost-efficiency/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/enterprise/cost-efficiency/Transform observability from unpredictable cost center to fixed operational expense. Netdata&rsquo;s distributed architecture and transparent pricing deliver 90% cost savings while providing unlimited metrics, logs, and per-second visibility.Open Sourcehttps://www.netdata.cloud/open-source/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/open-source/The world&rsquo;s most popular open source monitoring platform. Deploy complete infrastructure observability in 60 seconds with zero configuration. Trusted by millions of engineers worldwide.Operations Center Monitoring & 24/7 NOC Teamshttps://www.netdata.cloud/solutions/built-for/ops/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/built-for/ops/Real-time observability platform designed for 24/7 operations centers. Per-second monitoring, zero-configuration deployment, and AI-powered troubleshooting reduce MTTR by 80%.Our Values and Promiseshttps://www.netdata.cloud/values/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/values/Discover the 12 principles that guide every decision at Netdata. From radical transparency to edge-native intelligence, learn how we invest engineering effort to eliminate complexity and align our success with your operational needs.Per-Second Observability Without Cardinality Limitshttps://www.netdata.cloud/features/architecture/real-time-at-scale/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/architecture/real-time-at-scale/Netdata delivers true real-time monitoring at planetary scale through distributed edge intelligence - maintaining per-second granularity and sub-2-second latency whether you&rsquo;re monitoring 10 nodes or 100,000, with 90% cost reduction and 80% MTTR improvement.Point-and-Click Analysis Without Query Languageshttps://www.netdata.cloud/features/visualization/no-query-language/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/visualization/no-query-language/Experience genuine queryless observability with Netdata&rsquo;s algorithmic dashboards and NIDL framework. Each chart delivers the equivalent of 25+ Grafana visualizations through simple point-and-click navigation - making expert-level analysis accessible to every engineer from day one.Proxmox Monitoring With Real-Time Observabilityhttps://www.netdata.cloud/solutions/technologies/proxmox-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/technologies/proxmox-monitoring/Netdata delivers enterprise-grade Proxmox monitoring with per-second granularity, automated dashboards, and ML anomaly detection - all without the complexity or cost of traditional solutions.Query Systemd-Journal Logs Without Pipelineshttps://www.netdata.cloud/solutions/use-cases/systemd-journal-logs/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/systemd-journal-logs/Netdata revolutionizes systemd-journal log management by querying logs directly where they live, eliminating costly pipelines and delivering faster queries with zero configuration. Get complete visibility into Linux system logs with AI-powered troubleshooting, unified metrics correlation, and 90% cost reduction compared to traditional log management platforms.Real-Time GPU Monitoring For AI Infrastructurehttps://www.netdata.cloud/solutions/industries/ai/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/industries/ai/Monitor AI training clusters, inference APIs, and ML workloads with Netdata&rsquo;s edge-native platform. Per-second visibility, ML-powered insights, predictable pricing.Real-Time Infrastructure Monitoring For Freelancershttps://www.netdata.cloud/solutions/built-for/freelancers/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/built-for/freelancers/Real-time infrastructure monitoring built for technical freelancers managing multiple client environments. Zero configuration, AI-powered insights, and predictable costs let you focus on delivering value, not managing monitoring tools.Real-Time Infrastructure Monitoring For Tech Industryhttps://www.netdata.cloud/solutions/industries/technology/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/industries/technology/Netdata delivers per-second observability for technology infrastructure with ML-based anomaly detection, zero-configuration deployment, and predictable per-node pricing - solving the cost, complexity, and visibility challenges facing modern tech teams.Real-Time Infrastructure Observability For CISOshttps://www.netdata.cloud/solutions/built-for/cisos/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/built-for/cisos/Transform infrastructure security monitoring with real-time visibility, edge-based ML anomaly detection, and zero-configuration deployment. Netdata empowers CISOs to detect threats faster, reduce operational burden, and maintain data sovereignty - all at 90% lower cost than traditional SIEMs.Real-Time Infrastructure Troubleshooting With AIhttps://www.netdata.cloud/solutions/use-cases/troubleshooting/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/troubleshooting/Transform troubleshooting from hours to minutes with Netdata&rsquo;s real-time observability platform. Get per-second metrics, automatic anomaly detection, and AI-guided investigations—all with zero configuration and 90% cost savings.Real-Time Monitoring & ML Detection For Sysadminshttps://www.netdata.cloud/solutions/built-for/sysadmins/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/built-for/sysadmins/Purpose-built observability for sysadmins: per-second metrics, automatic dashboards, ML-powered anomaly detection, and predictable pricing. Monitor everything from bare metal to Kubernetes without learning query languages or building dashboards.Real-Time Observability For 24/7 Operationshttps://www.netdata.cloud/solutions/use-cases/continuous-operations/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/continuous-operations/Real-time observability built for continuous operations. Per-second metrics, ML anomaly detection, and AI root cause analysis keep your infrastructure running around the clock.Real-Time Observability For Developers Who Ship Fasthttps://www.netdata.cloud/solutions/built-for/developers/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/built-for/developers/Stop context switching between tools. Netdata provides developers with real-time infrastructure visibility, AI-assisted debugging, and zero-configuration monitoring—all in one unified platform that integrates directly into your IDE and workflow.Real-Time Observability For Government & Public Sectorhttps://www.netdata.cloud/solutions/industries/government/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/industries/government/Netdata delivers enterprise-grade observability for government agencies with per-second monitoring, configurable multi-year log retention, edge-based ML anomaly detection, and 90% cost savings vs. legacy monitoring - all while keeping data sovereign on your infrastructure.Real-Time Observability For Platform Engineershttps://www.netdata.cloud/solutions/built-for/platform-engineers/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/built-for/platform-engineers/Empower platform engineering teams with Netdata&rsquo;s distributed observability platform. Get per-second visibility, automated dashboards, ML anomaly detection, and predictable costs - all without query languages or complex pipelines.Real-Time Observability For SRE Teamshttps://www.netdata.cloud/solutions/built-for/sre/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/built-for/sre/Transform SRE operations with Netdata&rsquo;s edge-native observability platform. Get per-second visibility, ML anomaly detection on every metric, and AI-powered troubleshooting at 90% lower cost than traditional solutions.Real-Time Troubleshooting With Sub-2-Second Latencyhttps://www.netdata.cloud/features/visualization/troubleshooting/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/visualization/troubleshooting/Interactive debugging with per-second precision and full historical context. Netdata transforms troubleshooting through edge-native ML, automated correlation, and AI-powered analysis.Red Hat OpenShift Monitoring Tool At Scalehttps://www.netdata.cloud/solutions/technologies/redhat-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/technologies/redhat-monitoring/Netdata delivers real-time, AI-powered observability for Red Hat OpenShift with 90% cost savings, per-second metrics, ML anomaly detection on every metric, and zero-configuration deployment. Eliminate Prometheus memory exhaustion, Loki query timeouts, and RHACM complexity.Retail Monitoring Software Without PromQLhttps://www.netdata.cloud/solutions/industries/retail/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/industries/retail/Transform retail operations with Netdata&rsquo;s edge-native observability platform. Monitor POS systems, payment processing, store networks, and inventory infrastructure in real-time with per-second granularity, ML-powered anomaly detection, and predictable per-node pricing.Root Cause Analysis (RCA) With 80% MTTR Reductionhttps://www.netdata.cloud/features/aiml/root-cause-analysis/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/aiml/root-cause-analysis/Netdata&rsquo;s edge-native ML detects anomalies as they happen, automated correlation surfaces root causes in the top 30-50 results, and AI explains incidents in plain English - achieving 80% MTTR reduction at 90% lower cost.Service Mesh Observability Without Overheadhttps://www.netdata.cloud/solutions/use-cases/service-mesh-observability/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/service-mesh-observability/Netdata revolutionizes service mesh observability with true real-time monitoring, automatic anomaly detection, and transparent pricing - solving the cost explosion, performance overhead, and complexity that plague traditional solutions.Synthetic Monitoring Solution For APIs & Serviceshttps://www.netdata.cloud/solutions/use-cases/synthetic-checks/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/synthetic-checks/Real-time synthetic monitoring for APIs, certificates, DNS, and network health - unified with infrastructure observability for faster troubleshooting and predictable costs.Team Collaboration With Real-Time Observabilityhttps://www.netdata.cloud/features/enterprise/team-collaboration/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/enterprise/team-collaboration/Unite teams with real-time visibility, intelligent collaboration features, and enterprise-grade access control - all while maintaining data sovereignty and predictable costs.Telecom Network Monitoring Software At Scalehttps://www.netdata.cloud/solutions/industries/telecom/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/industries/telecom/Transform telecom operations with distributed edge monitoring that delivers complete infrastructure visibility, ML-powered anomaly detection, and zero-configuration deployment in minutes.Text-To-Alert: Create Alerts From Natural Languagehttps://www.netdata.cloud/blog/ai-alerts/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/blog/ai-alerts/<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 &ldquo;Netdata expert&rdquo; on the team who has spent the time digging through the documentation.</p>Tiered Retention With 0.6 Bytes/Sample Storagehttps://www.netdata.cloud/features/dataplatform/tiered-retention/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/dataplatform/tiered-retention/Netdata redefines tiered retention through edge-native architecture that updates all storage tiers simultaneously during collection, eliminating batch jobs and maintenance overhead while providing 15× better efficiency than traditional systems.Unified Observability Platform With Predictable Costshttps://www.netdata.cloud/solutions/use-cases/unified-observability-architecture/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/unified-observability-architecture/Netdata delivers unified observability through edge-native architecture - metrics, logs, and AI-powered insights at per-second granularity without the complexity, cost explosion, or tool sprawl of traditional platforms.VMware Monitoring Software Without Centralized Datahttps://www.netdata.cloud/solutions/technologies/vmware-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/technologies/vmware-monitoring/Netdata delivers per-second VMware monitoring with zero configuration, built-in ML anomaly detection, and 90% cost savings. Monitor vSphere, ESXi hosts, VMs, and hybrid clouds with true real-time visibility.Web Server Monitoring Software For Complete Visibilityhttps://www.netdata.cloud/solutions/use-cases/webserver-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/webserver-monitoring/Transform web server monitoring with Netdata&rsquo;s edge-native platform. Get per-second metrics, automated root cause analysis, and complete infrastructure visibility without complex setup or unpredictable costs.Windows Event Log Monitoring Softwarehttps://www.netdata.cloud/solutions/use-cases/windows-event-logs/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/windows-event-logs/Netdata revolutionizes Windows Event Log monitoring by combining infrastructure metrics with native log access, ML anomaly detection, and AI troubleshooting - delivering comprehensive observability at a fraction of traditional SIEM costs.Windows Server Monitoring Software At Scalehttps://www.netdata.cloud/solutions/technologies/windows-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/solutions/technologies/windows-monitoring/Transform Windows Server monitoring with Netdata&rsquo;s edge-native platform. Get per-second visibility, automatic discovery, and AI-powered troubleshooting at a fraction of traditional costs.Zero Configuration Observability In 60 Secondshttps://www.netdata.cloud/features/architecture/zero-configuration/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/architecture/zero-configuration/True zero-configuration observability: from installation to troubleshooting production issues in 60 seconds, without specialized skills or months of integration work.Zero Data Storage In SaaS With Unified Visibilityhttps://www.netdata.cloud/product/netdata-cloud-saas/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/product/netdata-cloud-saas/Access your entire infrastructure from anywhere while all observability data stays on-premises. Unlimited horizontal scalability with predictable per-node pricing. Role-based access control, dynamic organization, infrastructure-level dashboards, centralized alerts, and managed AI troubleshooting.Zero-Downtime Monitoring For Real-Time Deploymentshttps://www.netdata.cloud/features/architecture/zero-downtime-monitoring/Thu, 18 Dec 2025 00:00:00 +0000https://www.netdata.cloud/features/architecture/zero-downtime-monitoring/Netdata&rsquo;s distributed architecture eliminates single points of failure in monitoring, delivering sub-2-second visibility with automatic failover, zero data loss, and production-safe resource overhead—ensuring complete observability during the moments that matter most.Dashboard Gaps During Outages: Research Reporthttps://www.netdata.cloud/resources/research/dashboard-gaps-during-outages/Mon, 01 Dec 2025 00:00:00 +0000https://www.netdata.cloud/resources/research/dashboard-gaps-during-outages/<blockquote> <p><strong>Research Notice</strong>: This document was compiled through online research conducted on December 1, 2025. It serves as reference material for our blog post: <a href="https://www.netdata.cloud/blog/monitor-everything-is-an-anti-pattern/">Monitor Everything is an Anti-Pattern!</a>. Sources are cited inline and summarized at the end.</p> </blockquote> <h2 id="outage-incidents-with-monitoring-gaps-missing-dashboards--quantified-impact">Outage Incidents With Monitoring Gaps, Missing Dashboards &amp; Quantified Impact</h2> <h2 id="executive-summary">Executive Summary</h2> <p>This report documents multiple real-world outage incidents where monitoring systems failed to collect critical data, engineers created dashboards ad-hoc during crises, and teams implemented systematic improvements post-incident. The research reveals consistent patterns across major technology companies including Cloudflare, Datadog, GitLab, AWS, Azure, PagerDuty, and Google SRE, with quantified financial impacts reaching <strong>$2 million per hour</strong> for high-impact outages.</p>Monitor Everything is an Anti-Pattern!https://www.netdata.cloud/blog/monitor-everything-is-an-anti-pattern/Mon, 01 Dec 2025 00:00:00 +0000https://www.netdata.cloud/blog/monitor-everything-is-an-anti-pattern/<p><strong>Bullshit and nonsense.</strong></p> <p>But let&rsquo;s take it from the beginning.</p> <p>The industry&rsquo;s story goes something like this:</p> <blockquote> <p><em>&ldquo;Monitor everything is universally recognized as an anti-pattern.&rdquo;</em><br/> <em>&ldquo;You&rsquo;ll drown in metrics, burn out your engineers, and blow your budget.&rdquo;</em><br/> <em>&ldquo;Just focus on 3–10 signals — the Four Golden Signals, RED, USE — and ignore everything else.&rdquo;</em><br/> <em>&ldquo;Trust us, you don&rsquo;t want that much telemetry.&rdquo;</em><br/> <br/> (<a href="https://www.netdata.cloud/resources/research/monitor-everything-anti-pattern/">true, read the whole story here</a>)</p> </blockquote> <p>Then, in the same breath:</p>Why 'Monitor Everything' Is An Anti-Pattern: Researchhttps://www.netdata.cloud/resources/research/monitor-everything-anti-pattern/Mon, 01 Dec 2025 00:00:00 +0000https://www.netdata.cloud/resources/research/monitor-everything-anti-pattern/<blockquote> <p><strong>Research Notice</strong>: This document was compiled through online research conducted on December 1, 2025. It serves as reference material for our blog post: <a href="https://www.netdata.cloud/blog/monitor-everything-is-an-anti-pattern/">Monitor Everything is an Anti-Pattern!</a>. Sources are cited inline and summarized at the end.</p> </blockquote> <h2 id="tldr">TL;DR</h2> <p>&ldquo;Monitor everything&rdquo; is universally recognized as an anti-pattern by SRE experts, observability leaders, and major tech companies. The core reasons are:</p> <ol> <li><strong>Metric Fatigue</strong>: Teams become overwhelmed by excessive data, unable to identify critical signals</li> <li><strong>Alert Fatigue</strong>: 63% of organizations face 1,000+ daily alerts with 72-99% false positives, costing $300,000+/hour in missed incidents</li> <li><strong>Lack of Actionability</strong>: 97% of alerts are non-actionable noise rather than signals requiring response</li> <li><strong>High Costs</strong>: Organizations spend 20-40% of cloud budgets on observability (vs. optimal 10-15%), with cardinality explosions creating exponential cost increases</li> <li><strong>Employee Burnout</strong>: Costs $4,000-$21,000 per employee annually, totaling $5M+ for 1,000-person companies</li> <li><strong>System Complexity</strong>: Monitoring systems themselves become fragile, requiring constant maintenance</li> <li><strong>Monitoring Tools Creating Problems</strong>: Monitoring agents can cause the latency outliers they&rsquo;re meant to detect</li> </ol> <p><strong>Expert Consensus</strong>: Focus on 3-10 key metrics (Google&rsquo;s Four Golden Signals, RED Method, USE Method) that indicate symptoms rather than attempting comprehensive monitoring of all possible metrics.</p>Gartner IOCS 2025: Tackling Observability Overspendhttps://www.netdata.cloud/blog/gartner-iocs-2025/Fri, 07 Nov 2025 00:00:00 +0000https://www.netdata.cloud/blog/gartner-iocs-2025/<p>The observability market is facing a paradox. As organizations spend more than ever on monitoring tools, their infrastructure complexity continues to grow, and incident resolution times often remain stubbornly high. Teams are drowning in data, struggling with tool sprawl, and facing unpredictable, budget-breaking bills.</p> <p>This challenge, how to gain better visibility without spiraling costs, is one of the most critical conversations for IT leaders today.</p> <!--truncate--> <p>That&rsquo;s why the Netdata team is heading to Las Vegas for the <strong>Gartner IT Infrastructure, Operations &amp; Cloud Strategies (IOCS) Conference</strong> from December 9-11, 2025. We&rsquo;ll be there to discuss this challenge head-on and share our vision for a more efficient and intelligent future for observability.</p>ServiceNow Integration: Streamline Incident Responsehttps://www.netdata.cloud/blog/servicenow-integration/Fri, 07 Nov 2025 00:00:00 +0000https://www.netdata.cloud/blog/servicenow-integration/<p>When a critical alert fires at 2 AM, the last thing your on-call engineer should be doing is manual administrative work. Yet, for many teams, that&rsquo;s exactly what happens. You see the alert in your monitoring tool, then you have to switch contexts, open a new browser tab, log into your ITSM platform, and manually create an incident—all while your systems are failing.</p> <p>This &ldquo;swivel-chairing&rdquo; between tools is slow, error-prone, and a significant drag on your Mean Time to Resolution (MTTR).</p>SOC 2 Type 2: Validated Security Controls Over Timehttps://www.netdata.cloud/blog/soc2-type-2-compliance/Thu, 16 Oct 2025 00:00:00 +0000https://www.netdata.cloud/blog/soc2-type-2-compliance/<p>We&rsquo;re excited to share that Netdata has successfully achieved SOC 2 Type 2 attestation.</p> <!--truncate--> <p>Following a five-month audit conducted by Sensiba LLP, we can now confirm that our security controls work consistently in practice. The audit covered the period from April 1 to August 31, 2025, and tested whether our controls operated effectively throughout that entire timeframe.</p> <p>Back in April, we announced our <a href="https://www.netdata.cloud/blog/soc2-type1/">SOC 2 Type 1 attestation</a>, which validated that our security controls were properly designed at a specific point in time. We also mentioned we were entering the monitoring period for Type 2. Today we can share the results.</p>Automate Infrastructure Analysis With AI Reportshttps://www.netdata.cloud/blog/scheduled-reports-insights-investigations/Tue, 23 Sep 2025 00:00:00 +0000https://www.netdata.cloud/blog/scheduled-reports-insights-investigations/<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.</p> <p>We believe that if a process is repeatable, it should be automated.</p> <!--truncate--> <p>That&rsquo;s why we’re introducing <strong>Scheduled AI Investigations and Insights</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.</p>Elasticsearch Yellow Cluster: Unassigned Shards Fixhttps://www.netdata.cloud/academy/elasticsearch-yellow-cluster-access/Sun, 07 Sep 2025 00:00:00 +0000https://www.netdata.cloud/academy/elasticsearch-yellow-cluster-access/<p>You run a health check on your production cluster and the result comes back: <code>status: yellow</code>. It&rsquo;s not the dreaded red status, so your application is likely still serving requests, but this is a critical warning sign. An Elasticsearch yellow cluster status is a direct indication that your data&rsquo;s high availability is compromised. While all your primary shards are active, one or more replica shards have failed to be assigned to a node. Ignoring this warning can lead to data loss if another node fails, or worse, it could be a symptom of a network partition risking an Elasticsearch split-brain.</p>Docker Layer Caching in CI Pipelines Cut Build Times by 70 %https://www.netdata.cloud/academy/docker-layer-caching/Sat, 06 Sep 2025 00:00:00 +0000https://www.netdata.cloud/academy/docker-layer-caching/<p>You push a one-line code change, and your CI/CD pipeline kicks off. You grab a coffee, come back, and it&rsquo;s still running, stuck on the <code>docker build</code> step. Slow container builds are a silent productivity killer, delaying feedback, slowing down deployments, and frustrating developers. In an ephemeral CI environment where every job starts with a clean slate, Docker often has to rebuild your entire application image from scratch, every single time.</p>Linux Cgroups V2 Memory Throttling & OOM Fixhttps://www.netdata.cloud/academy/diagnosing-linux-cgroups/Fri, 05 Sep 2025 00:00:00 +0000https://www.netdata.cloud/academy/diagnosing-linux-cgroups/<p>Your critical service is lagging. Users are complaining about timeouts. You check your orchestration platform and see the dreaded <code>OOMKilled</code> status on a container. You dive into the node&rsquo;s logs (<code>dmesg</code>) and confirm it: the kernel&rsquo;s Out-of-Memory (OOM) killer has claimed another victim. The immediate fix is easy—restart the container, maybe give it more memory—but the real question remains unanswered: <em>why</em> did it happen? Was it a sudden memory leak, a traffic spike, or something more subtle?</p>Designing Error Budget Policies For SLOs At Scalehttps://www.netdata.cloud/academy/designing-error-budget-policies/Thu, 04 Sep 2025 00:00:00 +0000https://www.netdata.cloud/academy/designing-error-budget-policies/<p>In every engineering organization, there&rsquo;s a constant, fundamental tension: the push to ship new features versus the need to maintain a stable, reliable service. Move too fast, and you risk outages that erode user trust. Move too slowly, and you risk being outpaced by the competition. For years, this balancing act was managed by intuition, late-night heroics, and tense priority meetings. Site Reliability Engineering (SRE) offers a better way: the error budget.</p>Consul Service Discovery Failures: Causes & Fixeshttps://www.netdata.cloud/academy/consul-service-discovery-failures/Wed, 03 Sep 2025 00:00:00 +0000https://www.netdata.cloud/academy/consul-service-discovery-failures/<p>It’s a scenario that keeps DevOps and SRE teams up at night: your application logs fill with connection errors, services start failing, and you realize a critical component can&rsquo;t find the database it depends on. The culprit? A breakdown in your service discovery mechanism. For many, that mechanism is HashiCorp Consul, the backbone of modern microservice architectures. When Consul falters, your entire ecosystem can become unstable.</p> <p>Understanding how to diagnose these failures is crucial. The problem often lies deep within the operational layers—agent communication issues, misconfigured health checks, or disruptions in the gossip protocol that maintains cluster state. In this guide, we&rsquo;ll dissect the most common causes of Consul service discovery failures, providing you with the tools to troubleshoot and resolve them. More importantly, we&rsquo;ll show you how to shift from a reactive, fire-fighting mode to a proactive one, using comprehensive monitoring to build a truly resilient Consul deployment.</p>AI Troubleshooting GA With On-Demand Creditshttps://www.netdata.cloud/blog/ai-credits/Tue, 02 Sep 2025 00:00:00 +0000https://www.netdata.cloud/blog/ai-credits/<p>Since launching our AI investigations and insights in a research preview, one thing has become clear: <strong>automated root cause analysis delivers a significant return on investment.</strong> Teams have confirmed that instant insights don&rsquo;t just save a few minutes; they fundamentally shorten incident response cycles, free up valuable engineering hours, and reduce the business impact of downtime.</p> <p>The preview successfully demonstrated this value, with 10 free AI sessions per month allowing teams to integrate AI into their workflows. Now, based on the success and maturity of the capabilities, we are proud to announce that <strong>Netdata&rsquo;s AI investigations and insights are graduating from research preview to General Availability.</strong></p>Fix NGINX 502/504 Double-Proxy Errors With CloudFronthttps://www.netdata.cloud/academy/cloudfront-nginx-origin-solving-proxy/Tue, 02 Sep 2025 00:00:00 +0000https://www.netdata.cloud/academy/cloudfront-nginx-origin-solving-proxy/<p>You’ve set up a modern, resilient architecture: NGINX as your robust origin server and Cloudflare as your global CDN and security layer. Then, it happens. A visitor reports seeing a dreaded white screen with &ldquo;502 Bad Gateway&rdquo; or &ldquo;504 Gateway Timeout.&rdquo; The immediate question is, who&rsquo;s to blame? Is Cloudflare having an <code>edge_error</code>, or is your NGINX origin server failing? This confusion is a common pitfall in a <code>double_reverse_proxy</code> setup where requests pass through multiple layers.</p>PostgreSQL 17 Cardinality Estimation & Tuning Tipshttps://www.netdata.cloud/academy/cardinality-estimation-in-postgres/Mon, 01 Sep 2025 00:00:00 +0000https://www.netdata.cloud/academy/cardinality-estimation-in-postgres/<p>You&rsquo;ve seen it before: a query that runs in milliseconds on your staging server takes minutes to execute in production. Or a seemingly simple <code>JOIN</code> causes the <code>query_planner</code> to choose a disastrously slow Nested Loop over a much faster Hash Join. In almost every case, the root cause of these performance mysteries is not a bug in PostgreSQL, but a flaw in its understanding of your data. This is the challenge of <code>cardinality_estimation</code>. The planner is only as smart as the statistics it&rsquo;s given, and when its <code>row_estimation</code> is wrong, the consequences are severe.</p>Using FOR UPDATE SKIP LOCKED For Queue Workflowshttps://www.netdata.cloud/academy/update-skip-locked/Fri, 29 Aug 2025 00:00:00 +0000https://www.netdata.cloud/academy/update-skip-locked/<p>One of the most common and powerful patterns in modern application development is the job queue. Whether you&rsquo;re sending emails, processing images, or running complex calculations, offloading tasks to background workers is essential for building responsive and scalable systems. Many developers reach for dedicated queueing software like RabbitMQ or Redis, but for many use cases, your primary PostgreSQL database already has all the tools you need to build a robust, transactional, and incredibly performant <code>job_queue_postgres</code>.</p>SSL/TLS Handshake Failures Causing NGINX 502 Errorshttps://www.netdata.cloud/academy/ssl-tls-handshake-failures-nginx/Wed, 27 Aug 2025 00:00:00 +0000https://www.netdata.cloud/academy/ssl-tls-handshake-failures-nginx/<p>You&rsquo;ve set up NGINX as a reverse proxy, pointing it to a secure upstream service. You refresh your browser, and instead of your application, you&rsquo;re greeted by a stark &ldquo;502 Bad Gateway&rdquo; page. You check your upstream service; it&rsquo;s running perfectly. Puzzled, you turn to the NGINX error logs and find a cryptic message that seems to complicate things even further: <code>SSL_do_handshake() failed</code>.</p> <p>This scenario is frustratingly common. A 502 error suggests a problem with the upstream server, but in many cases, NGINX itself is failing to establish a secure connection with that server. The true culprit is an SSL/TLS handshake failure, often masked by this generic HTTP error code. Understanding the root cause is key to a quick resolution, preventing prolonged downtime and tedious debugging sessions.</p>How Autovacuum Causes PostgreSQL Deadlockshttps://www.netdata.cloud/academy/autovaccum-vs-deadlock/Tue, 26 Aug 2025 00:00:00 +0000https://www.netdata.cloud/academy/autovaccum-vs-deadlock/<p>You&rsquo;ve meticulously optimized your application queries. Your transaction logic is sound. Yet, under heavy load, your system seizes up, logging the dreaded &ldquo;deadlock detected&rdquo; error. You dig into the logs, expecting to find two application transactions locked in a deadly embrace, but instead, you find a surprising culprit: one of the participants is the PostgreSQL <code>autovacuum</code> process. How can a routine maintenance task, designed to keep the database healthy, be the cause of a production-stopping <code>postgres_deadlock</code>?</p>Real-World PostgreSQL Deadlock Examples & Fixeshttps://www.netdata.cloud/academy/10-real-world-postgresql-deadlock/Mon, 25 Aug 2025 00:00:00 +0000https://www.netdata.cloud/academy/10-real-world-postgresql-deadlock/<p>It’s 3 AM. The pager screams. Your application is throwing a cascade of errors, and users are reporting that the system is completely frozen. You dive into the logs and see the same ominous message repeating over and over: <code>ERROR: deadlock detected</code>. A PostgreSQL deadlock is one of the most abrupt and disruptive failures a database can experience. It&rsquo;s not a performance degradation; it&rsquo;s a hard stop where two or more transactions are locked in a fatal embrace, each waiting for a resource the other holds.</p>Redis Sentinel Failover & Split-Brain Recovery Guidehttps://www.netdata.cloud/academy/redis-cluster-split/Sun, 24 Aug 2025 00:00:00 +0000https://www.netdata.cloud/academy/redis-cluster-split/<p>You&rsquo;re on call. An alert fires—your Redis master node is unreachable. Your heart rate quickens. You&rsquo;ve set up Redis Sentinel for high availability, but is it working? Did the failover succeed? Or worse, are you now in a Redis cluster split-brain situation where two nodes think they&rsquo;re the master, leading to data inconsistency and eventual loss? In these critical moments, blindly trusting the automation isn&rsquo;t enough; you need to verify what&rsquo;s happening.</p>Fix NGINX 503 Errors From Misconfigured limit_reqhttps://www.netdata.cloud/academy/rate-limiting-gone-wrong-nginx/Sat, 23 Aug 2025 00:00:00 +0000https://www.netdata.cloud/academy/rate-limiting-gone-wrong-nginx/<p>You’ve done the responsible thing. To protect your application from abusive bots and prevent any single user from overwhelming your services, you&rsquo;ve implemented rate limiting in NGINX. You add the <code>limit_req_zone</code> and <code>limit_req</code> directives, push the configuration, and watch. But instead of seeing a drop in malicious traffic, your monitoring dashboards light up with a sea of red. A massive <code>503 Service Unavailable</code> spike appears, and legitimate users are complaining they can&rsquo;t access your site. Your shield has become a weapon turned against yourself.</p>Prometheus Alertmanager: Noise Reduction Ruleshttps://www.netdata.cloud/academy/prometheus-alert-manager/Fri, 22 Aug 2025 00:00:00 +0000https://www.netdata.cloud/academy/prometheus-alert-manager/<p>It’s 3 AM, and a torrent of PagerDuty notifications floods your phone. A single network partition has triggered a cascade, making every service instance that can&rsquo;t reach the database fire its own individual alert. You&rsquo;re drowning in hundreds of notifications, all pointing to the same root cause. This is alert fatigue, a critical problem for any SRE or on-call engineer. When you&rsquo;re constantly bombarded with low-signal noise, you risk becoming desensitized, potentially overlooking the one critical alert that signals a major incident.</p>Tune NGINX Timeouts: Eliminate Upstream Errorshttps://www.netdata.cloud/academy/nginx-eliminate-upstream-timeout/Thu, 21 Aug 2025 00:00:00 +0000https://www.netdata.cloud/academy/nginx-eliminate-upstream-timeout/<p>The <code>504 Gateway Timeout</code> error is a familiar and frustrating sight for anyone managing web applications. It signifies a breakdown in communication, but not between the user and your server. Instead, it means NGINX, acting as your trusty reverse proxy, gave up waiting for a response from a backend, or &ldquo;upstream,&rdquo; service. This could be your Node.js application, a PHP-FPM process, or a Python microservice.</p> <p>While your first instinct might be to blame the application, the root cause is often a simple configuration mismatch. NGINX has built-in timers to protect itself from unresponsive backends. When a backend process takes too long—longer than NGINX is configured to wait—NGINX proactively closes the connection and serves the dreaded 504 error. Understanding and tuning directives like <code>proxy_read_timeout</code> and <code>fastcgi_read_timeout</code> is the key to resolving these issues and building a more resilient infrastructure.</p>Linux Load Average Spikes: IO Wait & Bottleneckshttps://www.netdata.cloud/academy/linux-system-load-average-spike/Tue, 19 Aug 2025 00:00:00 +0000https://www.netdata.cloud/academy/linux-system-load-average-spike/<p>An alert fires: &ldquo;High load average on production server.&rdquo; Your heart rate quickens. You SSH into the machine and run a command like top, only to be confused. The CPU usage is hovering at 10%, but the load average is sky-high. What’s going on? If the CPU isn&rsquo;t busy, what is the system &ldquo;loaded&rdquo; with? This common scenario highlights one of the most misunderstood metrics in <a href="https://www.netdata.cloud/solutions/technologies/linux-monitoring/">Linux performance troubleshooting</a>: the system load average.</p>Kubernetes CrashLoopBackOff: Causes & Quick Fixeshttps://www.netdata.cloud/academy/kubernetes-crash-loop-backoff/Mon, 18 Aug 2025 00:00:00 +0000https://www.netdata.cloud/academy/kubernetes-crash-loop-backoff/<p>You’ve deployed your application to Kubernetes, but a quick check on your pods reveals the dreaded <code>CrashLoopBackOff</code> status. Your pod is stuck in a restart loop, and your service is down. This isn&rsquo;t an error itself, but a status indicating that Kubernetes is trying to start a container, it crashes, and Kubernetes waits an exponentially increasing amount of time before trying again. This back-off mechanism prevents a faulty pod from overwhelming the cluster with constant restart attempts.</p>Jenkins Declarative Pipeline: Parallelism Fixeshttps://www.netdata.cloud/academy/jenkins-declarative-pipeline/Sun, 17 Aug 2025 00:00:00 +0000https://www.netdata.cloud/academy/jenkins-declarative-pipeline/<p>You&rsquo;ve embraced the power of Jenkins Declarative Pipelines, and now you&rsquo;re looking to take the next step in CI/CD optimization: running stages in parallel. The promise is alluring—slashing your build times by running tests, linting, and security scans simultaneously. You eagerly refactor your <code>Jenkinsfile</code>, commit the change, and watch your pipeline trigger. But instead of blazing-fast execution, your build gets stuck, silently hanging with no obvious error.</p> <p>This frustrating scenario is often caused by two insidious problems: executor starvation and node label mismatch. While the <code>parallel</code> step in Jenkins is incredibly powerful, using it naively can lead to deadlocked pipelines and misconfigured jobs that fail in subtle ways. Understanding how Jenkins allocates resources is the key to unlocking true parallelism without the headaches. This guide will walk you through these common pitfalls and provide the best practices to avoid them.</p>Buffering keepalive and Hidden 500-Series Errors in NGINXhttps://www.netdata.cloud/academy/hidden-500-ngnix-series-errors/Sat, 16 Aug 2025 00:00:00 +0000https://www.netdata.cloud/academy/hidden-500-ngnix-series-errors/<p>Your NGINX instance is humming along, handling traffic flawlessly. Then, a sudden traffic spike or a deployment of a new feature that handles larger files occurs, and your monitoring dashboards light up with 500-series errors. You check the NGINX error logs, but find nothing conclusive—just generic <code>502 Bad Gateway</code> or <code>504 Gateway Timeout</code> messages that don&rsquo;t point to a root cause. These are the hidden, frustrating errors that often stem not from your application code, but from poorly tuned NGINX buffering and <code>keepalive</code> settings.</p>Fix Helm Chart Rollback & Pending-Upgrade Failureshttps://www.netdata.cloud/academy/helm-chart-rollback-failures/Fri, 15 Aug 2025 00:00:00 +0000https://www.netdata.cloud/academy/helm-chart-rollback-failures/<p>It’s a scenario that every Kubernetes operator dreads. A production deployment has gone wrong, you confidently initiate a Helm rollback, and then&hellip; nothing. The command hangs, and a quick check reveals the dreaded <code>pending-rollback</code> status. Your application is now in a broken state, and you&rsquo;re blocked from deploying any new fixes. This is more than a minor inconvenience; it&rsquo;s a critical failure that can leave your services unstable and your deployment pipeline paralyzed.</p>Fix NGINX 502 Bad Gateway In Kubernetes Ingresshttps://www.netdata.cloud/academy/debugging-nginx-errors-inside-kubernetes/Wed, 13 Aug 2025 00:00:00 +0000https://www.netdata.cloud/academy/debugging-nginx-errors-inside-kubernetes/<p>You’ve deployed your application to Kubernetes, and everything seems fine until a user reports the dreaded <code>502 Bad Gateway</code> or <code>504 Gateway Timeout</code>. In a traditional VM setup, your first step would be to SSH into the server and check the NGINX configuration and logs. But in the ephemeral, abstracted world of Kubernetes, the problem is rarely that simple. A gateway error from the NGINX Ingress Controller is often a symptom of a deeper issue within the cluster’s networking or health management systems.</p>Blue-Green And Canary Deployments With NGINXhttps://www.netdata.cloud/academy/blue-green-canary-deployments-nginx/Tue, 12 Aug 2025 00:00:00 +0000https://www.netdata.cloud/academy/blue-green-canary-deployments-nginx/<p>The moment of truth arrives. You&rsquo;ve tested the new version of your application, the container image is pushed, and the deployment pipeline is ready. You click &ldquo;deploy,&rdquo; and a wave of anxiety hits. Will this be a smooth, zero-downtime rollout, or will your dashboards soon light up with <code>502 Bad Gateway</code> and <code>504 Gateway Timeout</code> errors? For many teams using advanced deployment strategies like Blue-Green or Canary, this fear is all too real.</p>Docker Compose Networking: Service Discovery & Portshttps://www.netdata.cloud/academy/docker-compose-networking-mysteries/Sun, 10 Aug 2025 00:00:00 +0000https://www.netdata.cloud/academy/docker-compose-networking-mysteries/<p>You&rsquo;ve meticulously crafted your docker-compose.yml file, your services build correctly, and the startup process finishes without a single error. Yet, when your application tries to connect to its database, you get a &ldquo;Connection refused&rdquo; or &ldquo;Host not found&rdquo; error. This is a classic and frustrating scenario in Docker Compose networking. Your containers are running, but they&rsquo;re isolated in their own digital worlds, unable to communicate.</p> <p>These issues almost always boil down to two core mysteries: service discovery failed events, where containers can&rsquo;t find each other, and docker compose port conflict problems, where port mappings are misunderstood or misconfigured. To build reliable containerized applications, you must look beyond the docker-compose.yml file and understand the virtual network that Docker creates. This guide will demystify that network, providing you with the tools and techniques to troubleshoot and resolve these common connectivity challenges.</p>Metric Cardinality In Observability: Strategieshttps://www.netdata.cloud/academy/metric-cardinality-in-observability/Sun, 10 Aug 2025 00:00:00 +0000https://www.netdata.cloud/academy/metric-cardinality-in-observability/<p>It’s a story familiar to any SRE or DevOps engineer. You add a seemingly innocuous label to a key metric—<code>user_id</code>, <code>request_id</code>, <code>container_id</code>—to gain deeper insight. Suddenly, your monitoring bill skyrockets, your <code>Prometheus_TSDB</code> instance starts gasping for memory, and dashboards slow to a crawl. You have just triggered a <code>label_explosion</code>, the single biggest challenge in modern metrics-based observability: <code>metrics_cardinality</code>.</p> <p>High cardinality isn&rsquo;t an edge case; it&rsquo;s the new normal in a world of microservices, containers, and complex user interactions. As the number of unique time series grows into the millions or even billions, it places immense pressure on monitoring systems, impacting <code>storage_costs</code>, query performance, and the fundamental ability to scale.</p>Early Deadlock Detection With pg_stat_kcache & eBPFhttps://www.netdata.cloud/academy/early-deadlock-detection/Sat, 09 Aug 2025 00:00:00 +0000https://www.netdata.cloud/academy/early-deadlock-detection/<p>The dreaded deadlock. For anyone managing a high-traffic PostgreSQL database, it&rsquo;s a familiar nemesis. The database logs a &ldquo;deadlock detected&rdquo; message, a transaction is unceremoniously aborted, and your application has to handle the fallout. This reactive cycle is frustrating; by the time you&rsquo;re alerted, the damage is already done. Traditional <code>postgres_metrics</code> and monitoring tools are excellent at telling you <em>that</em> a deadlock occurred, but they fall short of explaining the subtle conditions that led to it.</p>Save Hours on Troubleshooting with Automated Investigationshttps://www.netdata.cloud/blog/automated-investigations/Mon, 04 Aug 2025 00:00:00 +0000https://www.netdata.cloud/blog/automated-investigations/<p>How many times has your team stared at a dashboard, pointed to a spike, and asked a question that charts alone can&rsquo;t answer? &ldquo;What was the real impact of that deployment?&rdquo; &ldquo;Why are our Kubernetes pods in the us-east-1 cluster suddenly crashing?&rdquo; &ldquo;Are we wasting money on overprovisioned servers?&rdquo;</p> <!--truncate--> <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.</p>Netdata Now Troubleshoots Your Alerts for Youhttps://www.netdata.cloud/blog/automated-alert-troubleshooting/Sun, 03 Aug 2025 00:00:00 +0000https://www.netdata.cloud/blog/automated-alert-troubleshooting/<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&rsquo;re sleep-deprived is a Herculean task.</p> <!--truncate--> <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.</p>GitLab Runner Executor Failures: Docker & Kuberneteshttps://www.netdata.cloud/academy/gitlab-runner-executor/Thu, 24 Jul 2025 00:00:00 +0000https://www.netdata.cloud/academy/gitlab-runner-executor/<p>You’ve been there. You push your code, a new CI/CD pipeline kicks off in GitLab, and you wait for that satisfying green checkmark. Instead, you get a dreaded red &lsquo;X&rsquo;. The pipeline failed. Digging into the job logs, you find a cryptic message: &ldquo;ERROR: Job failed (system failure): prepare environment: exit code 1&rdquo;. The culprit is often the GitLab Runner executor—the very engine responsible for running your jobs—failing in its environment.</p>Apache Kafka Consumer Lag: Troubleshooting & Fixeshttps://www.netdata.cloud/academy/apache-kafka-consumer-lags/Wed, 23 Jul 2025 00:00:00 +0000https://www.netdata.cloud/academy/apache-kafka-consumer-lags/<p>You&rsquo;ve built a powerful, real-time data pipeline with Apache Kafka, but suddenly, things grind to a halt. The dreaded consumer lag is exploding, alerts are firing, and your downstream applications are starved for data. This scenario is all too common for teams running Kafka at scale. Often, the culprit is a subtle interplay between consumer group rebalancing, partition assignment, and suboptimal consumer configurations. Understanding these mechanics is not just about fixing a problem; it&rsquo;s about building resilient, high-throughput streaming systems from the ground up.</p>Apache mod_rewrite Debugging & Log Analysishttps://www.netdata.cloud/academy/apache-http-server-mod/Wed, 23 Jul 2025 00:00:00 +0000https://www.netdata.cloud/academy/apache-http-server-mod/<p>You&rsquo;ve crafted what seems like a perfect rewrite rule, uploaded it to your <code>.htaccess</code> file, and refreshed your browser, only to be met with a &ldquo;Too many redirects&rdquo; error. You&rsquo;re stuck in an Apache redirect loop, a frustrating and all-too-common problem when working with Apache mod_rewrite. This powerful module can manipulate URLs in almost any way imaginable, but its complexity means that a small mistake in a regular expression or a missing condition can lead to unexpected behavior, broken links, or infinite loops.</p>AWS ELB 5xx Surge Analysis: Health & Draininghttps://www.netdata.cloud/academy/aws-elb-surge-investigation/Wed, 23 Jul 2025 00:00:00 +0000https://www.netdata.cloud/academy/aws-elb-surge-investigation/<p>The alert notification chimes, and your dashboard lights up with an ELB 5xx error rate spike. Your application, running behind an AWS Application Load Balancer (ALB), is suddenly returning 502, 503, or 504 errors. This is a high-stakes scenario where every second of downtime impacts users. The load balancer is often just the messenger; the real culprit lies somewhere in your backend infrastructure. Is a target group unhealthy? Are your connections timing out? Is a misconfigured deployment process wreaking havoc?</p>25 NGINX Directives to Audit Before Opening a Support Tickethttps://www.netdata.cloud/academy/25-nginx-directives-to-audit/Wed, 09 Jul 2025 00:00:00 +0000https://www.netdata.cloud/academy/25-nginx-directives-to-audit/<p>You&rsquo;ve built a robust application, but it&rsquo;s sluggish or throwing intermittent errors. Your first instinct might be to blame the code, but often the culprit lies in the intricate web of your NGINX configuration. Before you spend hours debugging your application or drafting a support ticket, a thorough NGINX config check can save you time and reveal simple yet impactful misconfigurations.</p> <p>An NGINX configuration audit isn&rsquo;t just for troubleshooting; it&rsquo;s a proactive step toward better performance, tighter security, and greater stability. Many common issues related to performance bottlenecks, security vulnerabilities, or proxy errors stem from overlooked or poorly optimized directives. This checklist covers 25 essential directives you should review. Working through this list can help you pinpoint problems, implement best practices, and gain a deeper understanding of how NGINX operates.</p>Short vs Long Transactions In PostgreSQL Benchmarkshttps://www.netdata.cloud/academy/benchmarking-short-long-transactions-in-postgresql/Wed, 09 Jul 2025 00:00:00 +0000https://www.netdata.cloud/academy/benchmarking-short-long-transactions-in-postgresql/<p>Every developer working with a database faces a fundamental design choice: how to structure their transactions. Should a complex business operation, involving multiple database writes, be wrapped in a single, all-or-nothing transaction? Or is it better to break it down into a series of smaller, faster commits? On the surface, the <code>long_running_transaction</code> seems safer, guaranteeing perfect atomicity. But as traffic grows, a mysterious performance degradation can set in. Latency spikes, throughput drops, and users start seeing errors. The culprit is often not the queries themselves, but the invisible contention they create.</p>Netdata vs Auvik: Real-Time Auvik Alternativehttps://www.netdata.cloud/comparisons/auvik/Tue, 24 Jun 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/auvik/Netdata vs Auvik comparison: real-time full-stack observability with ML vs network-centric MSP SaaS with NCM.Netdata vs Cacti: Real-Time Cacti Alternativehttps://www.netdata.cloud/comparisons/cacti/Tue, 24 Jun 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/cacti/Netdata vs Cacti comparison — real-time full-stack network observability vs legacy SNMP graphing.Netdata vs ManageEngine OpManager: Which Is Better?https://www.netdata.cloud/comparisons/opmanager/Tue, 24 Jun 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/opmanager/Netdata vs ManageEngine OpManager — real-time, unified, ML-powered observability vs traditional modular NMS.Netdata vs NeDi: Network Discovery Tool Comparisonhttps://www.netdata.cloud/comparisons/nedi/Tue, 24 Jun 2025 00:00:00 +0000https://www.netdata.cloud/comparisons/nedi/Compare Netdata and NeDi for network monitoring, topology, flow analysis, and full-stack observability.Network Device Auto-Discoveryhttps://www.netdata.cloud/features/network/device-discovery/Tue, 24 Jun 2025 00:00:00 +0000https://www.netdata.cloud/features/network/device-discovery/Automatically discover, classify, and monitor every SNMP-reachable network device with zero manual MIB mapping.Netdata Implements MCP Protocolhttps://www.netdata.cloud/blog/netdata-mcp-server/Wed, 18 Jun 2025 00:00:00 +0000https://www.netdata.cloud/blog/netdata-mcp-server/<p><strong>Update (February 2026):</strong> Netdata now also provides MCP via Netdata Cloud at <code>app.netdata.cloud/api/v1/mcp</code> for infrastructure-wide access (Business/Homelab plan). See <a href="https://learn.netdata.cloud/docs/netdata-ai/mcp">MCP documentation</a> for details.</p> <hr> <p>We are excited to announce that Netdata has officially implemented the Model Context Protocol (MCP), joining the forefront of AI-powered infrastructure monitoring.</p> <p>By enabling direct connections between AI assistants and your data sources and tools, the Model Context Protocol is a new open standard that builds a crucial link between artificial intelligence and practical systems. Instead of the AI providing generic suggestions that don’t understand your environment, MCP enables it to communicate and then interact with your infrastructure data in real time. Being among the first monitoring platforms to adopt this groundbreaking protocol, Netdata is at the forefront of intelligent observability. With the help of this integration, traditional monitoring becomes a dialogue that your entire technical team is able to participate in. We encourage you to dive deeper into the technical foundations of MCP, explore <a href="https://www.anthropic.com/news/model-context-protocol">Anthropic&rsquo;s comprehensive</a> explanation, and discover how this protocol is reshaping the future of AI-data interaction.</p>How Can Generative AI (Gen AI) Be Used In Cybersecurityhttps://www.netdata.cloud/academy/generative-ai-in-cybersecurity/Tue, 10 Jun 2025 00:00:00 +0000https://www.netdata.cloud/academy/generative-ai-in-cybersecurity/<p>Generative AI has exploded into the mainstream, changing how we create content, write code, and interact with technology. But beyond its creative applications, <code>what is generative AI</code> doing in the high-stakes world of cybersecurity? The answer is complex. GenAI is rapidly becoming one of the most powerful tools for security professionals, but it&rsquo;s also a formidable weapon in the hands of their adversaries.</p> <p>For security teams grappling with an ever-expanding attack surface and increasingly sophisticated threats, GenAI offers a way to automate, predict, and respond faster than ever before. However, understanding <code>how generative AI can be used in cybersecurity</code> requires looking at both sides of the coin—its potential to fortify our defenses and its capacity to create entirely new kinds of attacks.</p>How To Find And Fix Memory Leaks in C or C++https://www.netdata.cloud/academy/how-to-find-memory-leak-in-c/Tue, 10 Jun 2025 00:00:00 +0000https://www.netdata.cloud/academy/how-to-find-memory-leak-in-c/<p>Your application feels sluggish. It runs perfectly after a restart, but over hours or days, it slows to a crawl before eventually crashing. If you&rsquo;re working with C or C++, this behavior is a classic symptom of a memory leak—a silent bug that can drain system resources and destabilize your services. Because these languages put memory management directly in your hands, understanding how to find and fix memory leaks is a critical skill for building robust, long-running applications.</p>How To Fix Packet Loss - A Step-by-Step Guide To Reduce Ithttps://www.netdata.cloud/academy/how-to-fix-packet-loss/Tue, 10 Jun 2025 00:00:00 +0000https://www.netdata.cloud/academy/how-to-fix-packet-loss/<p>You have a fast internet connection, but your online game is lagging, your video call is choppy, or your application feels unresponsive. You run a speed test, and everything looks fine—low ping, high bandwidth. So, what’s the problem? The likely culprit is <code>packet loss</code>, a frustrating and often misunderstood network issue that can occur even on the best internet connections.</p> <p>Unlike high latency (ping), which is a measure of delay, <code>packet loss meaning</code> refers to data that never arrives at its destination at all. These lost pieces of data, or &ldquo;packets,&rdquo; must be re-sent, creating hitches, stutters, and lag. This guide will walk you through what causes this issue and provide a clear, step-by-step process for <code>how to fix packet loss</code>.</p>How To Secure Sensitive Data In Cloud Environmentshttps://www.netdata.cloud/academy/how-to-secure-sensitive-data-in-cloud/Tue, 10 Jun 2025 00:00:00 +0000https://www.netdata.cloud/academy/how-to-secure-sensitive-data-in-cloud/<p>Migrating to the cloud offers unparalleled benefits in scalability, flexibility, and collaboration. However, this shift also introduces new complexities and risks, especially when it comes to protecting your most valuable asset—your data. Securing sensitive data in the cloud is not a one-time task; it&rsquo;s a continuous process that requires a deep understanding of your cloud environment, robust security practices, and a proactive mindset.</p> <p>Many organizations mistakenly assume their cloud service provider (CSP) handles all aspects of security. In reality, security is a shared responsibility. While the CSP is responsible for the security <em>of</em> the cloud (i.e., the physical data centers and underlying infrastructure), you, the customer, are responsible for security <em>in</em> the cloud. This includes securing your data, applications, and user access. Let&rsquo;s explore the essential strategies for <code>how to secure sensitive data in cloud environments</code>.</p>Kubernetes Security Posture Management (KSPM) Explainedhttps://www.netdata.cloud/academy/kubernetes-security-posture-management/Tue, 10 Jun 2025 00:00:00 +0000https://www.netdata.cloud/academy/kubernetes-security-posture-management/<p>Kubernetes has become the de facto standard for container orchestration, offering incredible power and scalability. But this complexity introduces a massive attack surface. A single misconfiguration in a YAML file, an overly permissive role, or a vulnerable container image can create a critical security gap. Traditional security tools, designed for static infrastructure, struggle to keep up with the dynamic, ephemeral nature of Kubernetes environments.</p> <p>This is where <code>Kubernetes Security Posture Management</code> (KSPM) comes in. It’s not just another security tool; it&rsquo;s a specialized practice designed to continuously monitor, assess, and enforce security policies across your entire Kubernetes ecosystem. For any team running mission-critical workloads on Kubernetes, understanding and implementing <code>KSPM</code> is no longer a luxury—it’s a necessity.</p>OpenSearch vs Elasticsearch Which One Is Better In 2025?https://www.netdata.cloud/academy/elasticsearch-vs-opensearch/Tue, 10 Jun 2025 00:00:00 +0000https://www.netdata.cloud/academy/elasticsearch-vs-opensearch/<p>If you&rsquo;re building a system for log analytics, application search, or security monitoring, you&rsquo;ve almost certainly faced a critical decision: OpenSearch vs Elasticsearch. For years, Elasticsearch was the undisputed king, but since 2021, its open-source fork, OpenSearch, has emerged as a powerful and popular alternative. What began as a dispute over licensing has evolved into two distinct projects with different philosophies, features, and performance characteristics.</p> <p>Choosing between them is no longer a simple matter. It&rsquo;s a strategic decision that impacts everything from your budget and licensing compliance to your system&rsquo;s performance and future scalability. As we move through 2025, the paths of these two search engines have diverged enough that making an informed choice is more important than ever. This guide breaks down the key differences to help you decide which platform is right for your needs.</p>What Is A Flaky Test How To Detect Fix & Avoid Themhttps://www.netdata.cloud/academy/flaky-tests/Tue, 10 Jun 2025 00:00:00 +0000https://www.netdata.cloud/academy/flaky-tests/<p>You push a new feature, all local tests pass, and you open a pull request. The continuous integration (CI) pipeline kicks off, but a few minutes later, you see a dreaded red &lsquo;X&rsquo;. A test failed. You scrutinize your code, find nothing wrong, and re-run the job. This time, it passes with a green checkmark. If this scenario feels familiar, you&rsquo;ve encountered a flaky test.</p> <p>A flaky test is a test that exhibits non-deterministic behavior—it can both pass and fail across multiple runs without any changes to the code or its environment. While it might seem like a minor annoyance, test flakiness is a significant problem that can erode your team&rsquo;s confidence in your test suite, slow down development velocity, and ultimately allow real bugs to slip into production. Understanding what causes these inconsistencies is the first step toward building a more reliable and trustworthy testing process.</p>What Is A Memory Leak In Java How To Detect And Fix Themhttps://www.netdata.cloud/academy/java-memory-leak/Tue, 10 Jun 2025 00:00:00 +0000https://www.netdata.cloud/academy/java-memory-leak/<p>Your Java application runs smoothly after a fresh deploy, but over hours or days, its performance steadily degrades. Response times creep up, garbage collection pauses become longer and more frequent, and then, the inevitable happens: the application crashes, logging a fatal OutOfMemoryError. This classic scenario is often the calling card of a subtle but dangerous problem—a memory leak.</p> <p>Even though Java features automatic memory management via its garbage collector (GC), applications are not immune to leaks. A Java memory leak occurs when objects are no longer in use by the application, but the GC is unable to reclaim their memory because they are still being referenced. Over time, these orphaned objects accumulate, consuming the available heap space and leading to performance degradation and eventual failure. Understanding how to detect and fix these leaks is a critical skill for any Java developer.</p>What Is Distributed Tracing How It Works And Use Caseshttps://www.netdata.cloud/academy/distributed-tracing/Tue, 10 Jun 2025 00:00:00 +0000https://www.netdata.cloud/academy/distributed-tracing/<p>Your team has deployed a new feature, but users are reporting that a specific action in your application is painfully slow. You look at the metrics for your frontend service, and they seem fine. You check the logs for the user authentication service, and there are no errors. The database CPU usage is normal. So where is the bottleneck? In a modern distributed architecture built with microservices, a single user request can trigger a complex chain reaction across dozens of independent services. Finding the root cause of a problem can feel like searching for a needle in a global haystack.</p>Agentless Network Monitoring A Complete Guide To Understandhttps://www.netdata.cloud/academy/agentless-network-monitoring/Mon, 09 Jun 2025 00:00:00 +0000https://www.netdata.cloud/academy/agentless-network-monitoring/<p>As your infrastructure grows, so does the complexity of monitoring it. The traditional approach often involves deploying a software &ldquo;agent&rdquo; on every server, virtual machine, and container. While effective, this can quickly become a management nightmare. You have to install, configure, update, and secure hundreds or even thousands of agents, each <a href="https://www.netdata.cloud/academy/how-to-fix-cpu-overload/">consuming precious CPU</a> and memory on the hosts you&rsquo;re trying to monitor. What if there was a less intrusive way?</p>Garbage Collection In Java What It Is and How It Workshttps://www.netdata.cloud/academy/java-garbage-collection/Mon, 09 Jun 2025 00:00:00 +0000https://www.netdata.cloud/academy/java-garbage-collection/<p>One of the most powerful features of the Java platform is its automatic memory management. Unlike languages like <a href="https://www.netdata.cloud/academy/how-to-find-memory-leak-in-c/">C or C++</a>, where developers must manually allocate and deallocate memory, Java handles this process for you through a process called garbage collection (GC). This frees developers to focus on application logic rather than the complexities of memory management, which is a major reason for Java&rsquo;s enduring popularity.</p> <p>But what exactly is garbage collection in Java, and how does it work under the hood? While it&rsquo;s an automatic process, a solid understanding of the Java garbage collector is crucial for writing high-performance, stable applications and for troubleshooting <a href="https://www.netdata.cloud/academy/java-memory-leak/">memory-related issues</a> like the dreaded <code>OutOfMemoryError</code>.</p>How To View Docker Container Logs A Step-by-Step Guidehttps://www.netdata.cloud/academy/docker-logs/Mon, 09 Jun 2025 00:00:00 +0000https://www.netdata.cloud/academy/docker-logs/<p>Your containerized application is misbehaving. The service is unresponsive, or worse, it&rsquo;s <a href="https://www.netdata.cloud/guides/docker/docker-container-exits-immediately/">crash-looping</a>. As a developer or SRE, your first instinct is to ask, &ldquo;What do the logs say?&rdquo; For applications running in <a href="https://www.netdata.cloud/guides/docker/">Docker</a>, accessing and understanding container logs is the most fundamental troubleshooting skill you can possess. These logs are the raw, unfiltered story of what your application is doing, thinking, and feeling.</p> <p>But <code>docker logging</code> is more than just a single action. It&rsquo;s a comprehensive system with layers of functionality, from quickly tailing real-time output to implementing robust, production-grade log management strategies. This guide will walk you through everything you need to know to effectively <code>view docker container logs</code>, starting with the basics and progressing to the best practices that will keep your applications observable and your on-call nights quiet.</p>Logging As A Service (LaaS): Simplify Log Managementhttps://www.netdata.cloud/academy/logging-as-a-service/Mon, 09 Jun 2025 00:00:00 +0000https://www.netdata.cloud/academy/logging-as-a-service/<p>In the world of modern software development, logs are the lifeblood of observability. They are the detailed, chronological record of every event, error, and transaction that occurs within your applications and infrastructure. When something goes wrong, logs are the first place developers and SREs turn to for answers. But with the rise of microservices, containers, and distributed cloud architectures, the sheer volume and complexity of log data have exploded.</p> <p>The old way of managing logs—SSHing into a server and using <code>grep</code> to search through a text file—simply doesn&rsquo;t scale. This approach becomes an impossible, time-consuming, and error-prone task when you have hundreds of services spread across dozens of servers. This is the problem that Logging as a Service (LaaS) was created to solve.</p>What Is AIOps (Artificial Intelligence For IT Operations)https://www.netdata.cloud/academy/aiops/Mon, 09 Jun 2025 00:00:00 +0000https://www.netdata.cloud/academy/aiops/<p>Your team is drowning in data. Your monitoring systems generate thousands of alerts every day, most of which are just noise. When a real issue strikes your complex, distributed application, engineers scramble, jumping between a dozen different dashboards to piece together clues. This frantic, reactive firefighting is the reality for many IT Operations, DevOps, and SRE teams. It’s stressful, inefficient, and unsustainable.</p> <p>This is where AIOps (Artificial Intelligence for IT Operations) enters the picture. It&rsquo;s not just another industry buzzword; it&rsquo;s a fundamental shift in how we manage technology. AIOps is the practice of applying artificial intelligence—specifically machine learning and big data analytics—to automate and streamline every aspect of IT operations. By intelligently processing the massive volumes of data your systems generate, AIOps platforms help you move from a reactive state of constant crisis to a proactive, predictive model of management.</p>What Is Container Orchestration & Why Do We Need Ithttps://www.netdata.cloud/academy/container-orchestaration/Mon, 09 Jun 2025 00:00:00 +0000https://www.netdata.cloud/academy/container-orchestaration/<p>If you&rsquo;re building modern applications, you&rsquo;re likely using containers. They&rsquo;re lightweight, portable, and provide a consistent environment for your code. Deploying a single container is simple. Managing a handful is manageable. But what happens when your application grows from a few containers to hundreds or even thousands, all working together as a complex system of microservices?</p> <p>This is where manual management breaks down. You face a storm of questions: How do you deploy updates without downtime? How do you scale to handle a sudden traffic surge? What happens if a server fails in the middle of the night? Answering these questions manually is an operational nightmare. This is precisely the problem that container orchestration was created to solve.</p>What Is OpenTelemetry How It Works Benefits and Use Caseshttps://www.netdata.cloud/academy/opentelemetry/Mon, 09 Jun 2025 00:00:00 +0000https://www.netdata.cloud/academy/opentelemetry/<p>If you manage modern applications, you&rsquo;re dealing with complexity. Your system isn&rsquo;t a single program running on one server; it&rsquo;s a distributed web of microservices, serverless functions, and third-party APIs running across a hybrid cloud infrastructure. Understanding what&rsquo;s happening inside this complex system is a monumental challenge. Each component and vendor has its own proprietary way of exporting performance data, leaving you to juggle dozens of agents and formats, leading to data silos and vendor lock-in.</p>What Is Remote Infrastructure Management (RIM)https://www.netdata.cloud/academy/remote-infrastructure-management/Mon, 09 Jun 2025 00:00:00 +0000https://www.netdata.cloud/academy/remote-infrastructure-management/<p>The days of managing servers neatly racked in a single on-premise data center are over for most businesses. Today’s IT landscape is a sprawling mix of public cloud instances, private cloud infrastructure, edge devices, and SaaS applications. This distribution is powerful, but it creates a significant management challenge: How do you maintain control, ensure uptime, and secure an infrastructure that’s physically everywhere and nowhere at once?</p> <p>This is the problem that <code>Remote Infrastructure Management</code> (RIM) solves. It’s a strategic approach that moves IT operations from a hands-on, on-site model to a centralized, remote-first paradigm. For DevOps and SRE teams, understanding RIM is no longer optional; it&rsquo;s fundamental to building and maintaining resilient, scalable, and efficient systems in the modern era.</p>Whats The Difference Between PostgreSQL vs MySQLhttps://www.netdata.cloud/academy/postgres-mysql-differences/Mon, 09 Jun 2025 00:00:00 +0000https://www.netdata.cloud/academy/postgres-mysql-differences/<p>When building an application, one of the most fundamental decisions you&rsquo;ll make is choosing the right database. For many developers, this choice boils down to two of the most popular open-source relational databases in the world: PostgreSQL and MySQL. Both are powerful, reliable, and backed by strong communities, but they operate on different philosophies and excel in different areas.</p> <p>Making the right choice between <code>PostgreSQL vs MySQL</code> isn&rsquo;t about finding a single &ldquo;best&rdquo; database, but understanding which one aligns with your application&rsquo;s specific needs. This guide breaks down the critical differences in their architecture, features, performance characteristics, and ideal use cases to help you make an informed decision for your next project.</p>Introducing Netdata Insightshttps://www.netdata.cloud/blog/netdata-insights/Tue, 27 May 2025 00:00:00 +0000https://www.netdata.cloud/blog/netdata-insights/<p>We&rsquo;ve been thinking a lot about synthesis lately.</p> <p>Netdata already samples every metric every second at the edge. Engineers told us the remaining pain point was synthesis, the ability to pull hours or days or months of high‑resolution time‑series into a concise explanation they could hand to a teammate (or use themselves to debug faster).</p> <!--truncate--> <p>You know the pattern. An incident happens, and suddenly you&rsquo;re context-switching between dozens of dashboards, trying to reconstruct a timeline. Or you need to write a capacity planning report, and you&rsquo;re copy-pasting screenshots into slides, manually correlating trends across different retention windows. The raw data is there, but the synthesis step (the part where you turn metrics into narrative) doesn&rsquo;t scale.</p>What Is Canary Deployment? Benefits, Metrics & Setuphttps://www.netdata.cloud/academy/canary-deployment/Tue, 27 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/canary-deployment/<p>Releasing new software versions can be a nerve-wracking experience. Even with rigorous testing, the real world of production traffic often uncovers unforeseen issues. A problematic deployment can lead to downtime, frustrated users, and a frantic scramble to roll back. This is where a canary deployment strategy shines, offering a more cautious and controlled approach to rolling out updates.</p> <p>Instead of a big-bang release, a canary release exposes the new version to a small subset of users first, allowing you to monitor its performance and gather feedback before a full-scale rollout. This technique significantly de-risks the deployment process, especially in complex environments like Kubernetes.</p>What Is Structured Logging And How To Utilize It Effectivelyhttps://www.netdata.cloud/academy/what-is-structured-logging/Tue, 27 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/what-is-structured-logging/<p>Dealing with gigabytes of plain text log files can feel like searching for a needle in a haystack, especially when critical systems are down. Unstructured logs make it incredibly difficult to quickly pinpoint issues, correlate events, or gain meaningful insights from the vast amount of data your applications generate. If you&rsquo;ve ever struggled to filter logs by a specific customer ID or trace a transaction across multiple services, you understand the pain. This is precisely where structured logging steps in, transforming your log data from a chaotic stream of text into a valuable, queryable asset.</p>Nodejs Memory Leak How To Identify Debug And Avoid Themhttps://www.netdata.cloud/academy/nodejs-memory-leak/Mon, 26 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/nodejs-memory-leak/<p>In the fast-paced world of Node.js development, performance and reliability are non-negotiable. However, a silent saboteur often lurks in the shadows – the Node.js memory leak. These insidious issues can gradually degrade your application&rsquo;s performance, leading to slowdowns, crashes, and frustrated users. Understanding how to effectively identify, debug, and <a href="https://www.netdata.cloud/academy/how-to-find-memory-leak-in-c/">prevent memory leaks</a> is a critical skill for any developer, DevOps engineer, or SRE working with Node.js. This guide will walk you through the intricacies of Node.js memory management and equip you with the knowledge to tackle these challenging problems.</p>What Is A Bare Metal Server? Benefits & Use Caseshttps://www.netdata.cloud/academy/bare-metal-server/Mon, 26 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/bare-metal-server/<p>In a world increasingly dominated by virtualized cloud environments, the concept of a bare metal server might seem like a throwback. However, these physical powerhouses continue to play a critical role in modern IT infrastructure, offering distinct advantages for specific workloads. Understanding what is a bare metal server and why you might choose one over virtualized alternatives is key to designing efficient and high-performing systems.</p> <h2 id="what-is-a-bare-metal-server-definition--how-it-works">What Is A Bare Metal Server? Definition &amp; How It Works</h2> <p>At its core, a bare metal server is a physical computer server dedicated entirely to a single customer or tenant. Unlike virtual machines (VMs) that share the resources of a physical host through a hypervisor layer, a bare metal server gives the user direct, unmediated access to the underlying hardware – the &ldquo;bare metal.&rdquo; This means you have exclusive use of the server&rsquo;s CPU, RAM, storage, and network interface cards.</p>Application Monitoring Best Practices In 2025https://www.netdata.cloud/academy/application-monitoring-2025/Sun, 25 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/application-monitoring-2025/<p>In today&rsquo;s digitally driven world, application performance is not just a technical concern; it&rsquo;s a critical business imperative. Users expect applications to be fast, reliable, and seamlessly available. Any deviation can lead to frustrated users, lost revenue, and damaged reputation. This makes application monitoring a cornerstone of successful software development and operations. It&rsquo;s the continuous process of collecting, analyzing, and acting on data to ensure your applications meet performance, availability, and user experience expectations.</p>The Three Pillars Of Observability Logs Metrics And Traceshttps://www.netdata.cloud/academy/pillars-of-observability/Sun, 25 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/pillars-of-observability/<p>In the realm of modern, complex IT systems, especially those involving microservices, cloud-native architectures, and distributed environments, understanding what&rsquo;s happening internally is paramount. This is where observability comes into play. Observability isn&rsquo;t just about monitoring; it&rsquo;s the ability to infer the internal state and health of a system by examining its outputs. To achieve this, we rely on what are commonly known as the three pillars of observability: logs, metrics, and traces.</p>What Is Event Correlation Benefits Use Cases And Techniqueshttps://www.netdata.cloud/academy/event-correlation/Sun, 25 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/event-correlation/<p>In today&rsquo;s complex and dynamic IT environments, organizations are inundated with a massive volume of events generated by countless sources – applications, servers, network devices, security systems, and more. This flood of data, while rich in potential insights, can easily become overwhelming. The core challenge lies in sifting through this &ldquo;sea of data&rdquo; to identify events that truly matter and understand their relationships. This is precisely where event correlation becomes indispensable. It&rsquo;s the process of sensing and analyzing relationships between disparate events to uncover meaningful patterns, diagnose root causes, and enable proactive responses.</p>What Is Synthetic Transaction Monitoringhttps://www.netdata.cloud/academy/synthetic-monitoring/Sun, 25 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/synthetic-monitoring/<p>In today&rsquo;s digital-first world, the performance and availability of web applications are paramount to business success. Users expect seamless, fast, and reliable interactions, and any hiccup can lead to frustration, lost revenue, and a tarnished brand reputation. This is where synthetic transaction monitoring (STM) emerges as a critical proactive strategy. Unlike monitoring that relies on actual user traffic, STM uses simulated user journeys to continuously test and validate application functionality, performance, and availability, even before real users encounter issues.</p>What Is Blue-Green Deployment? Benefits & Processhttps://www.netdata.cloud/academy/blue-green-deployment/Sat, 24 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/blue-green-deployment/<p>Software teams today face the challenge of releasing updates quickly without disrupting users. Traditional deployment methods often cause downtime and raise the risk of bugs reaching production. Blue green deployment offers a solution: by running two identical environments and switching traffic seamlessly, teams can deliver new versions with minimal risk and zero downtime. In this guide, we’ll explain what blue green deployment is, how it works, its benefits and challenges, and the best practices for implementing it.</p>LLM Observability and Monitoring A Comprehensive Guidehttps://www.netdata.cloud/academy/llm-observability/Wed, 21 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/llm-observability/<p>The rapid proliferation of Large Language Models (LLMs) like GPT and LLaMA is transforming how businesses operate, from enhancing office productivity with tools like Microsoft Copilot to innovative fraud management at Stripe. However, deploying and managing these powerful LLM applications in production environments presents unique hurdles. The sheer size of these models, their complex architectures, and often non-deterministic outputs make them challenging to manage. If you&rsquo;re a developer, DevOps engineer, or SRE, you understand that ensuring consistent performance, security, and accuracy in LLM-driven systems requires a new level of insight. This is where LLM observability and LLM monitoring become indispensable.</p>Understanding Digital Experience Monitoring DEMhttps://www.netdata.cloud/academy/digital-experience-monitoring/Sun, 18 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/digital-experience-monitoring/<p>In today&rsquo;s digital-first world, the way users interact with your online services defines their perception of your brand. A slow-loading webpage, a confusing mobile app, or an unavailable critical feature can quickly lead to frustration and churn. This is where Digital Experience Monitoring (DEM) becomes indispensable, offering a critical lens into how users truly perceive and interact with your digital platforms. Understanding and optimizing these interactions is no longer a luxury but a necessity for businesses aiming to thrive.</p>Understanding Error Budgets And Their Importance In SREhttps://www.netdata.cloud/academy/error-budget/Sun, 18 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/error-budget/<p>In the quest for flawless digital experiences, the reality is that 100% uptime is an elusive, if not impossible, goal. Systems inevitably encounter issues, and services can experience disruptions. This is where the concept of an <strong>error budget</strong> becomes a cornerstone for modern <a href="https://www.netdata.cloud/academy/sre-vs-devops-what-are-the-main-differences-between-them/">Site Reliability Engineering (SRE) and DevOps</a> practices. Understanding and effectively managing your <strong>error budget</strong> can mean the difference between fostering innovation and constantly firefighting.</p> <p>So, <strong>what is an error budget</strong>? Simply put, it&rsquo;s the quantifiable amount of unreliability or downtime that a service can tolerate over a specific period without breaching its Service Level Objectives (SLOs) or upsetting users. It&rsquo;s the acknowledged margin for error, a critical component in balancing the drive for new features with the imperative of maintaining a stable and reliable service. For SRE teams, the <strong>sre error budget</strong> is not just a metric- it&rsquo;s a vital tool for decision-making.</p>A Comprehensive Guide To Database Performance Optimizationhttps://www.netdata.cloud/academy/database-performance/Sat, 17 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/database-performance/<p>Sluggish database performance can be a silent killer for applications, leading to frustrated users, missed opportunities, and a direct hit to your bottom line. In today&rsquo;s data-intensive environments, ensuring your database operates at peak efficiency isn&rsquo;t just a technical task- it&rsquo;s a critical business imperative. If you&rsquo;re grappling with slow queries, high resource consumption, or concerns about <code>data scalability</code>, this guide will walk you through essential <code>database optimization</code> strategies.</p> <h2 id="tldr-summary">TL;DR Summary</h2> <ul> <li>Database performance issues usually come down to a few repeat offenders: slow or poorly designed queries, CPU pressure, disk I/O bottlenecks, weak indexing, and locking or concurrency contention.</li> <li>To manage and improve performance, track core metrics like response time, throughput, scalability, and resource utilization (CPU, memory, disk I/O), then optimize iteratively rather than treating tuning as a one-time fix.</li> <li>The biggest wins typically come from query tuning (EXPLAIN/EXPLAIN ANALYZE, rewriting queries, caching) and smart indexing (right index types, best-practice column selection, and regular maintenance).</li> <li>For growth and resilience, use techniques like partitioning, sharding, connection pooling, read replicas, HA setups, and archiving via history tables, backed by continuous monitoring (for example, real-time per-second visibility and alerts) to catch issues before users feel them.</li> </ul> <h2 id="understanding-the-roots-of-database-performance-issues">Understanding The Roots Of Database Performance Issues</h2> <p>Before diving into solutions, it&rsquo;s crucial to understand what <code>database performance</code> truly means and what typically causes it to degrade. Performance refers to the speed and efficiency with which your database handles queries, transactions, and data retrieval. When performance suffers, it’s often due to one or more common culprits.</p>OpenShift vs Kubernetes What Are The Differenceshttps://www.netdata.cloud/academy/openshift-vs-kubernetes/Fri, 16 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/openshift-vs-kubernetes/<p>Container orchestration is a cornerstone of modern cloud-native application development, and when it comes to managing containers at scale, two names often dominate the conversation- OpenShift vs Kubernetes. While both platforms are designed to <a href="https://www.netdata.cloud/academy/deployment-automation/">automate the deployment</a>, scaling, and management of containerized applications, they have distinct characteristics and cater to slightly different needs. Understanding the difference between OpenShift and Kubernetes is crucial for organizations making strategic decisions about their containerization strategy.</p>SOC 2 Type 1: Committed To Security & Trusthttps://www.netdata.cloud/blog/soc2-type1/Fri, 16 May 2025 00:00:00 +0000https://www.netdata.cloud/blog/soc2-type1/<p>We are pleased to announce that Netdata has successfully achieved SOC 2 Type 1 attestation!</p> <!--truncate--> <p>Following an independent examination performed by AssuranceLab CPAs LLC, the report confirms that—as of April 25, 2025—the design of Netdata’s controls meets the Security, Availability, and Confidentiality Trust Services Criteria defined by the AICPA.</p> <p>At Netdata, the security and integrity of the monitoring data our users entrust to us are paramount. This significant milestone, validated through a rigorous, independent third-party audit conducted by AssuranceLab, formally attests to the robustness of our security controls and practices as designed and implemented at a specific point in time.</p>What Is Apache Kafka Used For Everything You Need To Knowhttps://www.netdata.cloud/academy/what-is-apache-kafka/Fri, 16 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/what-is-apache-kafka/<p>In today&rsquo;s data-driven world, applications generate vast streams of information that need to be processed and acted upon in real time. Managing these high-velocity, high-volume data flows presents a significant challenge for developers, DevOps engineers, and Site Reliability Engineers (SREs). This is precisely where Apache Kafka shines, offering a powerful platform for building robust, scalable, and real-time data pipelines. Understanding what Apache Kafka is used for and how its underlying Kafka technology works is crucial for anyone looking to harness the power of event streaming.</p>What Is Incident Management Benefits Process Best Practiceshttps://www.netdata.cloud/academy/what-is-incident-management/Wed, 07 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/what-is-incident-management/<p>When your critical services face unexpected disruptions, the clock starts ticking. For developers, DevOps engineers, and Site Reliability Engineers (SREs), understanding <strong>what is incident management</strong> is paramount. A slow or disorganized response not only impacts users but can also strain resources and damage your organization&rsquo;s reputation. Effectively managing these events is key to maintaining system stability and ensuring business continuity.</p> <p><strong>Incident management</strong> is the set of actions an organization takes to identify, analyze, correct, and prevent future occurrences of service disruptions or losses in operations. An &ldquo;incident,&rdquo; in ITIL terms, is any event that disrupts, or could disrupt, a service. This could range from a complete application outage to a web server running slowly, impacting productivity and posing a risk of total failure. The primary goal of <strong>IT incident management</strong> is to restore normal service operation as quickly as possible and minimize the adverse impact on business operations.</p>What Is Database Concurrency? Problems & Control Techniqueshttps://www.netdata.cloud/academy/what-is-database-concurrency/Sun, 04 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/what-is-database-concurrency/<p>Imagine trying to book the very last seat on a popular flight online. At the exact same moment, another person clicks &ldquo;confirm&rdquo; for the same seat. How does the system ensure only one booking goes through and the database remains accurate? This scenario highlights the core challenge of <strong>database concurrency</strong>.</p> <p>In today&rsquo;s world, <a href="https://www.netdata.cloud/academy/what-is-application-performance-monitoring-apm/">almost every application interacts with databases</a> accessed by multiple users or processes simultaneously. <strong>Database concurrency</strong> is the ability of a Database Management System (DBMS) to handle these simultaneous operations efficiently while maintaining data integrity and consistency. For developers, DevOps engineers, and SREs, understanding concurrency is vital for building reliable and performant applications. Let&rsquo;s explore what concurrency entails, the problems it can cause if unmanaged, and the techniques used to control it.</p>Normalized vs Denormalized - Choosing The Right Data Modelhttps://www.netdata.cloud/academy/normalized-vs-denormalized/Sat, 03 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/normalized-vs-denormalized/<p>When designing databases, one of the fundamental decisions you&rsquo;ll face is how to structure your data. Two primary approaches dominate this discussion: normalization and denormalization. Choosing between a <strong>normalized vs denormalized</strong> model significantly impacts data integrity, storage efficiency, and query performance. Understanding this trade-off is crucial for developers, database administrators, and SREs responsible for building and maintaining reliable, efficient systems.</p> <p>Getting the data model right from the start can save considerable headaches down the line. Let&rsquo;s explore what <strong>normalized data</strong> and <strong>denormalized data</strong> mean, their respective strengths and weaknesses, and how to decide which strategy best fits your specific needs.</p>Cloud Managed Services: Definition, Types & Benefitshttps://www.netdata.cloud/academy/what-are-cloud-managed-services/Fri, 02 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/what-are-cloud-managed-services/<p>Moving to the cloud offers incredible benefits like scalability and flexibility, but managing cloud infrastructure isn&rsquo;t always simple. Configuring networks, ensuring security, optimizing costs, performing maintenance, and staying compliant can quickly become overwhelming, especially for growing teams or those new to the cloud landscape. This is where <strong>cloud managed services</strong> come into play.</p> <p>Understanding <strong>managed cloud services</strong> is essential for developers, DevOps engineers, and SREs. It represents a strategic approach to handling cloud complexity, allowing technical teams to offload operational burdens and focus on innovation and core business objectives. Let&rsquo;s explore what these services entail, how they work, and their potential advantages and disadvantages.</p>How To Check Your Firewall Logs On Windowshttps://www.netdata.cloud/academy/how-to-check-firewall-logs-on-windows/Thu, 01 May 2025 00:00:00 +0000https://www.netdata.cloud/academy/how-to-check-firewall-logs-on-windows/<p>Every Windows system comes equipped with a built-in firewall, a critical component of its security posture. The <strong>Microsoft Defender Firewall</strong> (previously Windows Firewall) acts as a gatekeeper, controlling incoming and outgoing network traffic based on predefined rules. While it diligently protects your system, its default configuration doesn&rsquo;t tell you much about the traffic it&rsquo;s allowing or blocking.</p> <p>This is where <strong>Windows Firewall logs</strong> come in. These logs record detailed information about the firewall&rsquo;s activity, providing invaluable insights for <a href="https://www.netdata.cloud/academy/what-is-uptime-monitoring/">troubleshooting network connectivity problems</a>, identifying potential security threats, and ensuring compliance. For developers, DevOps engineers, and SREs, knowing <strong>how to check firewall logs</strong> is a fundamental skill for <a href="https://www.netdata.cloud/blog/windows-monitoring-improvements/">maintaining secure and reliable Windows environments</a>, whether on workstations or <strong>Windows Server</strong> instances. This guide will walk you through enabling, locating, interpreting, and managing these essential logs.</p>Cloud Workload - Definition, Types & Challengeshttps://www.netdata.cloud/academy/cloud-workload/Wed, 30 Apr 2025 00:00:00 +0000https://www.netdata.cloud/academy/cloud-workload/<p>Cloud computing has transformed how businesses operate, offering unprecedented scalability, flexibility, and access to powerful resources. As organizations increasingly migrate applications and services to the cloud, you&rsquo;ll frequently encounter the term &ldquo;cloud workload.&rdquo; But what is a cloud workload exactly? Understanding this concept is crucial, especially for DevOps engineers, SREs, and developers tasked with deploying, managing, and optimizing applications in cloud environments.</p> <p>A workload in cloud computing is essentially the specific amount of processing or computing task assigned to or running on cloud resources at any given time. It&rsquo;s the fundamental unit of work – an application, a service, a set of processes – that consumes cloud resources like compute, storage, and networking. Misunderstanding or mismanaging these workloads can lead to performance issues, security vulnerabilities, and runaway costs. This guide dives into the cloud workload definition, explores the various types of workloads, and highlights the common challenges associated with their management.</p>Industrial Remote Monitoring: Process & Exampleshttps://www.netdata.cloud/academy/industrial-remote-monitoring/Wed, 30 Apr 2025 00:00:00 +0000https://www.netdata.cloud/academy/industrial-remote-monitoring/<p>Imagine needing to know the exact operating temperature of a critical pump in a remote processing plant, or wanting to predict if a crucial piece of machinery on your factory floor is about to fail – all without sending a technician on-site. This is the power of <strong>industrial remote monitoring</strong>. In today&rsquo;s competitive landscape, industries from manufacturing to energy to logistics are under constant pressure to improve efficiency, reduce costs, and ensure safety. <strong>Remote machine monitoring</strong> provides the critical visibility and data needed to achieve these goals.</p>Ecommerce Infrastructure: Components & Benefitshttps://www.netdata.cloud/academy/ecommerce-infrastructure/Tue, 29 Apr 2025 00:00:00 +0000https://www.netdata.cloud/academy/ecommerce-infrastructure/<p>The world of online shopping has exploded, offering convenience and accessibility like never before. Businesses can reach global audiences, and consumers can browse and buy from anywhere. But behind every successful online store, from small boutiques to giants like Amazon, lies a complex system working tirelessly: the <strong>ecommerce infrastructure</strong>. Without this foundation, websites crash during peak traffic, customer data gets compromised, and orders get lost – leading to frustrated customers and lost revenue.</p>Database Backup - Types, Process and Benefitshttps://www.netdata.cloud/academy/what-is-database-backup/Mon, 28 Apr 2025 00:00:00 +0000https://www.netdata.cloud/academy/what-is-database-backup/<p>Data is often called the lifeblood of modern organizations. From customer details and financial records to <a href="https://www.netdata.cloud/solutions/use-cases/webserver-monitoring/">application configurations and operational logs</a>, databases store the critical information that powers business operations. But what happens if that data is lost due to hardware failure, accidental deletion, software corruption, or a cyberattack? Without a safety net, the consequences can be catastrophic, leading to costly downtime, reputational damage, and potentially irreparable business harm. This is where <strong>database backup</strong> becomes indispensable.</p>Server Security - What It Is & Why It Is So Importanthttps://www.netdata.cloud/academy/server-security/Fri, 25 Apr 2025 00:00:00 +0000https://www.netdata.cloud/academy/server-security/<p>Servers are the workhorses of the modern digital world. They store critical data, run essential applications, host websites, and power the services we rely on every day. But with great power comes great responsibility – specifically, the responsibility of server security. An unsecured server is like leaving your front door wide open, inviting potential threats that can lead to data breaches, service disruptions, and significant financial or reputational damage.</p> <p>For developers, DevOps engineers, and Site Reliability Engineers (SREs), understanding and implementing robust server protection is not just an IT task; it&rsquo;s fundamental to building reliable, trustworthy, and resilient systems. Whether you&rsquo;re managing a single web server or a complex distributed infrastructure, knowing how to secure a server is paramount. This guide will walk you through what server security entails, why it&rsquo;s critically important, and the essential server security best practices you need to implement.</p>What Is Web Server Capacity Planning & How Does It Work?https://www.netdata.cloud/academy/web-server-capacity-planning/Thu, 24 Apr 2025 00:00:00 +0000https://www.netdata.cloud/academy/web-server-capacity-planning/<p>Imagine launching a major marketing campaign or experiencing peak holiday traffic, only to have your website slow to a crawl or crash entirely. Users encounter frustrating error messages, abandon their carts, and your business suffers. This scenario often happens when web <strong>servers are at capacity</strong>, unable to handle the incoming load. The solution? Proactive <strong>web server capacity planning</strong>.</p> <p>For DevOps engineers, SREs, and system administrators, capacity planning isn&rsquo;t just a &ldquo;nice-to-have&rdquo;; it&rsquo;s a fundamental practice for ensuring the reliability, performance, and availability of web services. It&rsquo;s about understanding your current <strong>server capacity</strong>, anticipating future needs, and ensuring you have the right resources in place <em>before</em> demand overwhelms your infrastructure. This guide explores what web server capacity planning involves, why it&rsquo;s critical, and the process for implementing it effectively.</p>Container vs VM - Which Is Better Option For Youhttps://www.netdata.cloud/academy/container-vs-vm-which-is-better-for-you/Tue, 22 Apr 2025 00:00:00 +0000https://www.netdata.cloud/academy/container-vs-vm-which-is-better-for-you/<p>Deploying applications efficiently and reliably often requires isolating them from the underlying infrastructure and from each other. Virtualization makes this possible by creating virtual representations of computing resources. Two leading technologies dominate this space: containers and virtual machines (VMs). While both offer isolation and deployment benefits, they operate fundamentally differently. Choosing between a <strong>container vs VM</strong> approach is a critical decision that impacts performance, resource usage, security, and deployment speed.</p>Infrastructure Monitoring vs Application Monitoringhttps://www.netdata.cloud/academy/infrastructure-monitoring-vs-application-monitoring/Tue, 22 Apr 2025 00:00:00 +0000https://www.netdata.cloud/academy/infrastructure-monitoring-vs-application-monitoring/<p>Navigating the divide between infrastructure monitoring vs application monitoring requires a strategic approach. Infrastructure monitoring assesses system health, such as network bandwidth adequacy. <em>Is your network performing optimally?</em> On the other hand, application monitoring focuses on software performance issues. <em>What causes slow response times?</em></p> <p><em>How can your organization merge these monitoring capabilities to proactively identify and address potential issues?</em></p> <p>Let’s find out.</p> <h2 id="what-is-infrastructure-performance-monitoring-ipm">What Is Infrastructure Performance Monitoring (IPM)?</h2> <p><strong>Infrastructure Performance Monitoring</strong> (IPM) is a critical facet of IT operations. It focuses on the continuous oversight of essential system components such as hardware, cloud networks, and overall system performance. <a href="https://www.netdata.cloud/academy/what-is-infrastructure-monitoring-and-why-you-need-it/">IPM involves real-time data analysis</a> to ensure system health and efficiency, with a focus on identifying and pinpointing issues that can affect system performance and stability.</p>What Is Real-Time Monitoring? 5 Benefits & How It Workshttps://www.netdata.cloud/academy/real-time-monitoring-benefits/Mon, 21 Apr 2025 00:00:00 +0000https://www.netdata.cloud/academy/real-time-monitoring-benefits/<p><strong>Real-time monitoring</strong> is an essential tool for any business aiming to safeguard its digital operations and boost network performance. If your goal is to maintain smooth operations and robust security, you shouldn’t overlook <strong>real-time data monitoring</strong>, as it is crucial for detecting and addressing issues instantly, keeping your systems efficient and protected.</p> <p>In this article, we will explore how real-time monitoring works and its key benefits. Understanding these elements can significantly enhance your approach to network management and operational efficiency.</p>What Is Cloud Workload Protectionhttps://www.netdata.cloud/academy/cloud-workload-protection-and-challenges/Sun, 20 Apr 2025 00:00:00 +0000https://www.netdata.cloud/academy/cloud-workload-protection-and-challenges/<p>The shift to cloud computing offers incredible advantages in scalability, agility, and innovation. Businesses leverage cloud platforms like AWS, <a href="https://www.netdata.cloud/solutions/technologies/azure-monitoring/">Azure</a>, and <a href="https://www.netdata.cloud/solutions/technologies/gcp-monitoring/">GCP</a> to build and deploy applications faster than ever before. However, this migration introduces new complexities, particularly around securing the actual applications and processes running in these dynamic environments – the cloud workloads.</p> <p>Traditional security approaches focused on protecting the network perimeter are no longer sufficient. Cloud workload protection (CWP) has emerged as a critical security strategy designed specifically for the unique nature of cloud and hybrid environments. It focuses on securing the workload itself, regardless of where it runs. Understanding what CWP is, why it&rsquo;s essential, and the role of a Cloud Workload Protection Platform (CWPP) is vital for anyone responsible for cloud workload security. This guide explores the core concepts, benefits, and challenges of CWP.</p>What Is Network Congestion & How To Fix Ithttps://www.netdata.cloud/academy/what-is-network-congestion/Sun, 20 Apr 2025 00:00:00 +0000https://www.netdata.cloud/academy/what-is-network-congestion/<p><em>Site congestion found.</em> Let’s fix this before it gets worse! <strong>Network congestion</strong> can cripple your digital operations, slowing down processes and frustrating users. What causes congestion in your network? How does it affect your system, and what can you do to resolve – or prevent – these traffic jams? Keep your network up and running. Here is how!</p> <h2 id="what-is-network-congestion">What Is Network Congestion?</h2> <p><strong>Network congestion</strong> is like a traffic jam on your data highway; it occurs when there&rsquo;s more data trying to travel across a network than the available bandwidth can handle. This overload leads to annoying performance issues such as increased latency, jitter, packet loss, and reduced <a href="https://aws.amazon.com/compare/the-difference-between-throughput-and-latency/" target="_blank">throughput</a>.</p>What Are Windows Event Logs? The Ultimate Guidehttps://www.netdata.cloud/academy/what-are-windows-event-logs/Fri, 18 Apr 2025 00:00:00 +0000https://www.netdata.cloud/academy/what-are-windows-event-logs/<p>What could the dream of every IT professional be? Systems running flawlessly, no question about that. In reality, though, crashes, errors, and performance issues are inevitable. When problems arise, <strong>Windows event logs</strong> provide you with a detailed record of what happened, helping you diagnose and resolve issues efficiently.</p> <p><a href="https://gs.statcounter.com/os-market-share/desktop/worldwide" target="_blank">Windows powers about 71.9% of desktops worldwide</a>, making it the most widely used operating system. Moreover, Windows servers generate a massive amount of event logs. Some can log up to <a href="https://community.splunk.com/t5/Installation/Windows-Event-log-volume-is-extremely-high-on-one-server-where/m-p/135541" target="_blank">500 events per second</a>. With this kind of data flow, <strong>managing and analyzing logs efficiently</strong> is crucial to keeping your systems running smoothly and securely.</p>All Types Of Databases: Advantages & Exampleshttps://www.netdata.cloud/academy/types-of-databases/Thu, 17 Apr 2025 00:00:00 +0000https://www.netdata.cloud/academy/types-of-databases/<p>This is a tech-savvy exploration of <strong>database types</strong>! From the structured precision of relational models to the dynamic versatility of NoSQL, we’re diving deep into each <strong>DB type</strong>, unpacking their perks, and dishing out some examples to help you pick the perfect fit for your digital toolbox.</p> <h2 id="what-is-a-database">What Is A Database?</h2> <p><strong>A database is a structured collection of stored data</strong>, that allows easy access, management, and updating. They come in various types to suit different needs; from hierarchical databases that organize data in a tree-like format to relational databases that use tables and relationships among those data. Databases are essential to build any tech product from small mobile apps to large-scale enterprise systems. They help you handle, search, and efficiently utilize large data sets.</p>FreeBSD vs Linux - Which Is Better?https://www.netdata.cloud/academy/freebsd-vs-linux/Tue, 15 Apr 2025 00:00:00 +0000https://www.netdata.cloud/academy/freebsd-vs-linux/<p>When choosing an operating system for servers, embedded systems, or even desktops, <a href="https://www.netdata.cloud/solutions/built-for/developers/">developers</a> and system administrators often encounter two powerful, free, and open-source Unix-like options: FreeBSD and <a href="https://www.netdata.cloud/solutions/technologies/linux-monitoring/">Linux</a>. Both share a common heritage tracing back to the original UNIX, but they have evolved along different paths, resulting in distinct philosophies, architectures, and strengths. The <strong>FreeBSD vs Linux</strong> debate isn&rsquo;t about one being definitively &ldquo;better&rdquo; but rather understanding which is better suited for <em>your</em> specific needs.</p>Real-Time Data Visualization: Examples & Use Caseshttps://www.netdata.cloud/academy/real-time-data-visualization/Tue, 15 Apr 2025 00:00:00 +0000https://www.netdata.cloud/academy/real-time-data-visualization/<p>Data is increasingly generated at an unprecedented velocity. From application logs and system metrics to user interactions and IoT sensor readings, the sheer volume can be overwhelming. Simply collecting this data isn&rsquo;t enough; the real value lies in understanding it <em>as it happens</em>. This is where <strong>real-time data visualization</strong> comes into play. It transforms relentless streams of raw data into clear, intuitive visuals, allowing you to grasp trends, spot anomalies, and make informed decisions instantly.</p>What Is Network Security Monitoring - A Comprehensive Guidehttps://www.netdata.cloud/academy/network-security-monitoring/Mon, 14 Apr 2025 00:00:00 +0000https://www.netdata.cloud/academy/network-security-monitoring/<p>Imagine attackers silently infiltrating your network, hiding like the Greeks inside the Trojan Horse. They could remain undetected for weeks or even months, mapping your systems, <a href="https://www.netdata.cloud/academy/how-to-secure-sensitive-data-in-cloud/">stealing sensitive data</a>, and preparing for a larger attack. By the time you realize they&rsquo;re inside, significant damage might already be done. This scenario highlights a critical challenge in modern cybersecurity: perimeter defenses like firewalls are essential, but they aren&rsquo;t foolproof. You need visibility <em>inside</em> your network to detect threats that slip through.</p>Deployment Automation: Tools, Benefits & Practiceshttps://www.netdata.cloud/academy/deployment-automation/Wed, 02 Apr 2025 00:00:00 +0000https://www.netdata.cloud/academy/deployment-automation/<p>Getting new features and bug fixes from a developer’s machine into the hands of users quickly and reliably is paramount when it comes to successful software development. Manual deployment processes, however, are often slow, error-prone, and stressful.</p> <p>Manual tasks in application deployments frequently lead to configuration errors and make the software deployment process a time consuming process, especially for complex deployments. This is where <strong>deployment automation</strong> comes in – a crucial practice in <a href="https://www.netdata.cloud/solutions/built-for/devops/">modern DevOps</a> and agile methodologies.</p>Monitoring Netdata Restarts: A Reliable Solutionhttps://www.netdata.cloud/blog/2025-03-06-monitoring-netdata-restarts/Thu, 06 Mar 2025 00:00:00 +0000https://www.netdata.cloud/blog/2025-03-06-monitoring-netdata-restarts/<p>For a tool like Netdata, monitoring crashes and abnormal events extends far beyond bug fixing—it&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.</p> <h2 id="the-challenge-with-traditional-solutions">The Challenge with Traditional Solutions</h2> <p>Over the years, we&rsquo;ve evaluated many monitoring tools, each with significant limitations:</p> <table> <thead> <tr> <th>Tool</th> <th>Strengths</th> <th>Limitations</th> </tr> </thead> <tbody> <tr> <td><strong>Sentry</strong></td> <td>• Comprehensive error tracking features<br/>• Detailed stack traces</td> <td>• Per-event pricing model becomes prohibitive at scale<br/>• Forces sampling which reduces visibility into critical issues<br/>• Compromises complete error capture for cost control</td> </tr> <tr> <td><strong><a href="https://www.netdata.cloud/solutions/technologies/gcp-monitoring/">GCP</a> BigQuery &amp; Similar</strong></td> <td>• Powerful query capabilities<br/>• Flexible data processing<br/>• High scalability potential</td> <td>• Complex reporting setup and maintenance<br/>• Significant costs at high event volumes<br/>• Requires specialized technical expertise</td> </tr> <tr> <td><strong>Other Solutions</strong></td> <td>• Various specialized features<br/>• Some open-source flexibility</td> <td>• Either too inflexible for custom requirements<br/>• Or prohibitively expensive at full-capture scale<br/>• Often require compromising between detail and cost</td> </tr> </tbody> </table> <p>We consistently encountered these core challenges:</p>What Is Database Clustering? Types & Benefitshttps://www.netdata.cloud/academy/whatisdatabaseclusteringtypesbenefits/Thu, 06 Mar 2025 00:00:00 +0000https://www.netdata.cloud/academy/whatisdatabaseclusteringtypesbenefits/<p><strong>Database clustering</strong> is a robust strategy employed to enhance the <strong>performance</strong>, <strong>scalability</strong>, and <strong>availability</strong> of databases by orchestrating the distribution of data across multiple servers. This setup doesn&rsquo;t just streamline handling big data; it also keeps things running smoothly, even if some nodes go down. That way, your service stays up and available no matter what happens.</p> <p>By diving into the various <strong>types of database clustering architectures</strong>, in this article we explain how each setup addresses specific needs and challenges within IT environments. We&rsquo;ll also examine the tangible benefits that database clustering brings to businesses, from improved data redundancy to enhanced query response times.</p>Docker Monitoring Tool With Unlimited Containershttps://www.netdata.cloud/solutions/technologies/docker-monitoring/Mon, 27 Jan 2025 00:00:00 +0000https://www.netdata.cloud/solutions/technologies/docker-monitoring/Netdata brings the simplicity Docker promised to monitoring. One command install, instant visibility into every container&rsquo;s CPU, memory, disk, and network. No agents per container, no complex pipelines, no surprise bills.Infrastructure Monitoring For Network Engineershttps://www.netdata.cloud/solutions/built-for/network-engineers/Mon, 27 Jan 2025 00:00:00 +0000https://www.netdata.cloud/solutions/built-for/network-engineers/Netdata gives network engineers the full picture: live topology maps, NetFlow/sFlow/IPFIX flow analysis, SNMP monitoring with 100+ device profiles, a native SNMP trap receiver, per-second interface metrics, and ML that learns your traffic patterns. Deploy in minutes and stop hearing about outages from users.Netdata vs Prometheus: A 2025 Performance Analysishttps://www.netdata.cloud/blog/netdata-vs-prometheus-2025/Thu, 23 Jan 2025 00:00:00 +0000https://www.netdata.cloud/blog/netdata-vs-prometheus-2025/<p>When it comes to infrastructure monitoring, performance, scalability, and efficiency are critical considerations. In this blog post, we revisit two widely adopted open-source monitoring solutions: <strong>Netdata</strong> and <strong>Prometheus</strong>. Both tools have introduced notable improvements in their latest versions, emphasizing scalability and enhanced efficiency.</p> <p>In our previous <a href="https://www.netdata.cloud/blog/netdata-vs-prometheus-performance-analysis/">analysis</a>, we explored key differences between these systems, focusing on resource consumption and data retention. This follow-up expands on that comparison by subjecting both tools to a significantly larger workload. With the number of monitored nodes increased to 1000, containers to 80k, and metrics ingestion reaching 4.6 million metrics per second, we examine how each system performs under these demanding conditions, focusing on CPU utilization, memory requirements, disk I/O, network usage, and data retention during data ingestion.</p>Long-Term Data Storage and Retention in Netdatahttps://www.netdata.cloud/blog/long-term-data-retention/Tue, 21 Jan 2025 00:00:00 +0000https://www.netdata.cloud/blog/long-term-data-retention/<p>Netdata&rsquo;s database engine (dbengine) provides a sophisticated multi-tiered storage system designed for efficient long-term data retention while maintaining high granularity. This article explores the technical details of how Netdata handles metric storage, the advantages of its distributed architecture, and how to configure it for your specific needs.</p> <hr> <h2 id="database-engine-architecture">Database Engine Architecture</h2> <p>Netdata&rsquo;s database engine provides a sophisticated, efficient solution for long-term metric storage through:</p> <ul> <li>Intelligent multi-tiered storage architecture</li> <li>Efficient compression and caching mechanisms</li> <li>Flexible retention strategies</li> <li>Distributed deployment options</li> </ul> <p>This design enables organizations to maintain detailed historical data while optimizing storage use and maintaining query performance.</p>Network Monitoring Software With Real-Time Visibilityhttps://www.netdata.cloud/solutions/use-cases/network-monitoring/Wed, 15 Jan 2025 00:00:00 +0000https://www.netdata.cloud/solutions/use-cases/network-monitoring/Real-time network monitoring with per-second visibility, ML-powered anomaly detection, and zero-configuration deployment.Best Of Category Badges Earned In 2024: G2 & Capterrahttps://www.netdata.cloud/blog/netdata-best-of-category-badges-in-2024/Mon, 23 Dec 2024 00:00:00 +0000https://www.netdata.cloud/blog/netdata-best-of-category-badges-in-2024/<h2 id="netdata-featured-with-multiple-best-of-category-badges-in-2024">Netdata Featured with Multiple “Best Of” Category Badges in 2024</h2> <p>As we are close to the end of this year, we are thrilled to announce that <a href="https://www.capterra.com/p/251845/Netdata/?utm_source=vp&utm_medium=blog&utm_campaign=ts-q4-2024" target="_blank"><strong>Netdata</strong></a> has been recognized with multiple “Best of” badges from Gartner Digital Markets brands: <a href="https://www.capterra.com/?utm_source=vp&utm_medium=blog&utm_campaign=ts-q4-2024" target="_blank"><strong>Capterra</strong></a>, <a href="https://www.softwareadvice.com/?utm_source=vp&utm_medium=blog&utm_campaign=ts-q4-2024" target="_blank"><strong>Software Advice</strong></a>, and <a href="https://www.getapp.com/?utm_source=vp&utm_medium=blog&utm_campaign=ts-q4-2024" target="_blank"><strong>GetApp</strong></a>, leading software recommendation search engines.</p> <p>This “Best of” badges program is an independent assessment that evaluates user reviews to help buyers identify the highest-rated software companies in specific categories that offer the most popular solutions.</p>Getting Started With Netdata: Real-Time Monitoringhttps://www.netdata.cloud/blog/getting-started-with-netdata-a-comprehensive-guide-to-real-time-monitoring/Thu, 19 Dec 2024 00:00:00 +0000https://www.netdata.cloud/blog/getting-started-with-netdata-a-comprehensive-guide-to-real-time-monitoring/<p>Now you can start monitoring thousands of metrics in real-time, detecting anomalies throughout your infra, and troubleshooting issues even mid-crisis! Watch this <a href="https://www.youtube.com/watch?v=z5m8JdwMOn8&themeRefresh=1" target="_blank">1-minute video</a> for a quick intro! Get ready to be blown away!</p> <p>To fully utilize Netdata for monitoring your infrastructure, do these:</p> <h2 id="-deploy-netdata"><a href="https://learn.netdata.cloud/docs/deployment-guides/" target="_blank">① Deploy Netdata</a></h2> <p><em>Install Netdata to your systems.</em></p> <p>Netdata runs on <a href="https://www.netdata.cloud/solutions/technologies/linux-monitoring/">Linux</a>, <a href="https://www.netdata.cloud/solutions/technologies/windows-monitoring/">Windows</a>, FreeBSD and MacOS and can be installed on <a href="https://www.netdata.cloud/academy/bare-metal-server/">bare-metal servers</a>, cloud VMs, Kubernetes, even weak <a href="https://www.netdata.cloud/solutions/use-cases/iot-monitoring/">IoT devices</a>. We have carefully optimized it to be the fastest and most advanced monitoring you will ever need, and at the same time be extremely friendly, polite and respectful to your production systems and applications.</p>Real-Time Windows Server Monitoring Best Practiceshttps://www.netdata.cloud/academy/real-time-windows-server-monitoring-from-insights-to-action/Tue, 17 Dec 2024 00:00:00 +0000https://www.netdata.cloud/academy/real-time-windows-server-monitoring-from-insights-to-action/<iframe width="100%" height="450" src="https://www.youtube.com/embed/xc8PaCLdZDA?si=k5wcZHSP2Gyusdg4" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> <p>If you are looking to monitor your Windows Server Machines, this webinar will guide you through the latest strategies for real-time observability, system and infrastructure optimization. Featuring a hands-on live demo and insights from industry experts, this session will be full of actionable techniques to help you gain deeper visibility into your Windows infrastructure, troubleshoot faster, and improve performance with ease.</p>Customize Your Netdata Experience with Favoriteshttps://www.netdata.cloud/blog/customize-your-netdata-experience-with-favorites/Mon, 09 Dec 2024 00:00:00 +0000https://www.netdata.cloud/blog/customize-your-netdata-experience-with-favorites/<h3 id="make-netdata-yours-with-favorites">Make Netdata yours with Favorites</h3> <p>Monitoring is personal. Different systems, workloads, and use-cases mean different charts matter to different users. Netdata now makes it easier than ever to customize your experience by letting you <strong>favorite charts</strong> you care about most.</p> <h3 id="how-it-works">How it works</h3> <p>You&rsquo;ll now see a <strong>heart icon</strong> next to any chart or section of charts. Click it, and it instantly gets added to your <strong>favorites</strong>. favorites appear right above your system overview metrics, so you see what matters most—first.</p>20 Best DevOps, SRE & Observability Conferences 2025https://www.netdata.cloud/blog/20-devops-sre-observability-events-and-conferences-you-should-consider-in-2025/Wed, 04 Dec 2024 00:00:00 +0000https://www.netdata.cloud/blog/20-devops-sre-observability-events-and-conferences-you-should-consider-in-2025/<p>Every year, DevOps, SRE Sysadmin &amp; IT leaders gather at conferences across the world to share not only knowledge but also the latest trends, tools, and strategies for achieving greater insight and control over complex systems. This guide brings you a comprehensive list of DevOps, SRE &amp; observability events that can help you stay ahead in a rapidly evolving field. Whether you&rsquo;re exploring the latest in tools, cloud observability, or AI-driven insights, this guide will lead you to the perfect event to expand your knowledge and network with industry leaders!</p>SolarWinds Migration Program | Netdatahttps://www.netdata.cloud/migrate/solarwinds/Tue, 12 Nov 2024 00:00:00 +0000https://www.netdata.cloud/migrate/solarwinds/KAUST Case Study: System Stability For Academiahttps://www.netdata.cloud/case-studies/education/kaust/Mon, 11 Nov 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/education/kaust/<h2 id="empowering-system-stability-in-a-complex-research-environment">Empowering System Stability in a Complex Research Environment</h2> <p>The Systems Research Group at King Abdullah University of Science and Technology (KAUST) manages a diverse and expansive computing environment essential for advancing scientific research. Given the critical nature of this environment, ensuring uptime and rapid troubleshooting is essential. However, without a robust monitoring solution, pinpointing performance issues or hardware failures was a slow, often reactive process that challenged the team’s ability to maintain a smooth operational flow.</p>Native Windows Agent: Real-Time Windows Monitoringhttps://www.netdata.cloud/blog/netdata-native-windows-agent/Fri, 08 Nov 2024 00:00:00 +0000https://www.netdata.cloud/blog/netdata-native-windows-agent/<p>We are pleased to announce a significant advancement in system monitoring: the launch of <a href="https://www.netdata.cloud/solutions/technologies/windows-monitoring/">Netdata&rsquo;s first-ever Native Windows Agent</a>. This release represents a major step forward in our mission to provide comprehensive and efficient monitoring solutions across all platforms. With the introduction of the native Windows agent, we are extending our robust monitoring capabilities to Windows environments, enabling seamless and unified monitoring across diverse infrastructures. This development is a direct response to the needs of our user community, who have expressed a strong demand for a powerful and intuitive Windows monitoring solution.</p>Accurate Process Monitoring with Netdatahttps://www.netdata.cloud/blog/accurate-process-monitoring-with-netdata/Mon, 04 Nov 2024 00:00:00 +0000https://www.netdata.cloud/blog/accurate-process-monitoring-with-netdata/<p>Understand why tracking cumulative resource consumption is crucial for accurate process monitoring.</p> <!--truncate--> <h2 id="accurate-process-monitoring-with-netdata-why-tracking-cumulative-resource-consumption-matters">Accurate Process Monitoring with Netdata: Why Tracking Cumulative Resource Consumption Matters</h2> <p>Tracking the cumulative resource consumption of processes, including short-lived and exited children, is a rare feature in monitoring tools – and it’s one of the standout capabilities Netdata offers.</p> <p>Most mainstream solutions, like Datadog’s process monitoring and Prometheus’s Node Exporter, focus on active processes and only collect metrics per PID. Even specialized process monitors (<code>top</code>, <code>htop</code>, etc.) face the same limitations. They capture snapshots of currently running processes and often rely on fixed sampling intervals, which are too slow to catch very short-lived tasks. This approach falls short when trying to capture the resource footprint of dynamic applications, shell scripts, and complex process hierarchies.</p>Linux Load Average Myths and Realitieshttps://www.netdata.cloud/blog/linux-load-average-myths-and-realities/Sun, 03 Nov 2024 00:00:00 +0000https://www.netdata.cloud/blog/linux-load-average-myths-and-realities/<p>When it comes to monitoring system <a href="https://www.netdata.cloud/solutions/technologies/linux-monitoring/">performance on Linux</a>, the load average is one of the most referenced metrics. Displayed prominently in tools like <code>top</code>, <code>uptime</code>, and <code>htop</code>, it&rsquo;s often used as a quick gauge of system load and capacity. But how reliable is it? For complex, multi-threaded applications, load average can paint a misleading picture of actual system performance.</p> <p>In this article, we&rsquo;ll dive into the myths and realities of Linux load average, using insights from Netdata’s high-frequency, high-concurrency monitoring setup. Through this journey, we&rsquo;ll uncover why load average spikes can occur even under steady workloads, and why a single metric is rarely enough to capture the true state of a system. Whether you&rsquo;re a system administrator, developer, or performance enthusiast, this exploration of load average will help you interpret it more accurately and understand when it may—or may not—reflect reality.</p>Fix NGINX 500 Internal Server Error: Easy Stepshttps://www.netdata.cloud/academy/how-to-fix-nginx-500-internal-server-error-simple-steps-for-troubleshooting/Thu, 31 Oct 2024 00:00:00 +0000https://www.netdata.cloud/academy/how-to-fix-nginx-500-internal-server-error-simple-steps-for-troubleshooting/<p>When managing a website or web application through NGINX, it&rsquo;s quite likely you&rsquo;ve stumbled upon the feared 500 Internal Server Error at least once. This error often causes a moment of panic as it typically indicates a problem lurking within the server&rsquo;s operations. Regrettably, one finds that the message falls short in offering sufficient context to aid in uncovering the underlying reason.</p> <p>No need to fret! This guide is here to take you step by step through the usual culprits behind a 500 error when using NGINX and, even better, how to solve it. If you&rsquo;re facing a problem like not having the right permissions, a setup mistake, or something different, don&rsquo;t worry—we have all the steps you need to fix it.</p>6 + 1 Effective Strategies to Reduce Unplanned Downtimehttps://www.netdata.cloud/academy/6-+-1-effective-strategies-to-reduce-unplanned-downtime/Wed, 30 Oct 2024 00:00:00 +0000https://www.netdata.cloud/academy/6-+-1-effective-strategies-to-reduce-unplanned-downtime/<p>For DevOps and SRE teams, unplanned downtime may be a nightmare since it can ruin everything, from customer satisfaction to corporate operations. With more and more systems relying on constant availability, any unplanned downtime must be eliminated to ensure reliability of service. In the article below, we will discuss how to utilize <a href="https://www.netdata.cloud/academy/what-is-infrastructure-monitoring-and-why-you-need-it/">infrastructure monitoring</a>, monitoring tools, development and operations best practices in order to <a href="https://www.netdata.cloud/academy/what-is-uptime-monitoring/">minimize unplanned downtime</a>.</p> <h2 id="what-is-unplanned-downtime">What is Unplanned Downtime</h2> <p>Unplanned downtime occurs when an application or system or infrastructure component fails without notice, causing an interruption. These disruptions could be due to a network issue, or a problem in the software or hardware or even human error. The business expenses are often substantial in terms of revenue loss and negative publicity. So, putting a plan in place to reduce downtime is critical.</p>12 Benefits You Get by Scaling with Netdatahttps://www.netdata.cloud/blog/12-benefits-you-get-by-scaling-with-netdata/Wed, 23 Oct 2024 00:00:00 +0000https://www.netdata.cloud/blog/12-benefits-you-get-by-scaling-with-netdata/<p><a href="https://blogs.idc.com/2022/12/09/idc-futurescape-worldwide-future-of-digital-infrastructure-2023-predictions/" target="_blank">80% of decision-makers globally</a> acknowledge that digital infrastructure is essential for reaching business goals. However, IT infrastructure is becoming increasingly distributed and complex. Organizations are managing hundreds—even thousands—of nodes across cloud, on-premise, and edge environments. This predicament makes effective monitoring across all systems more essential than ever. In turn, this drives the demand for valuable real-time insights through scalable <a href="https://www.netdata.cloud/blog/understanding-monitoring-tools/" target="_blank">monitoring solutions</a> like Netdata​.</p> <p>If you’re managing a large infrastructure but haven’t fully embraced Netdata, now is the time to reconsider. Let&rsquo;s take a look at the benefits you’ll get, below.</p>5 Best Datadog Alternatives For Monitoring & Observabilityhttps://www.netdata.cloud/blog/5-datadog-alternatives/Tue, 15 Oct 2024 00:00:00 +0000https://www.netdata.cloud/blog/5-datadog-alternatives/<p>As businesses rely more on <a href="https://www.netdata.cloud/academy/what-is-infrastructure-monitoring-and-why-you-need-it/">infrastructure monitoring</a>, observability tools have become essential for keeping systems secure, responsive, and efficient. In this evolving monitoring landscape, Datadog is known as a leading analytics and monitoring tool, capable of collecting essential performance metrics from servers, databases, applications, and other IT infrastructures. But at what cost?</p> <h2 id="what-is-datadog-is-it-your-only-option">What Is Datadog? Is It Your Only Option?</h2> <p>Datadog is a cloud-based monitoring platform that helps organizations track the performance of their infrastructure, applications, and logs. It provides visibility across systems to ensure efficient operations and identify issues quickly.</p>ilert Integration: Streamline Monitoring & Responsehttps://www.netdata.cloud/blog/netdata-integration-with-ilert-streamlining-monitoring-and-incident-response/Mon, 14 Oct 2024 00:00:00 +0000https://www.netdata.cloud/blog/netdata-integration-with-ilert-streamlining-monitoring-and-incident-response/<p>Netdata now integrates with ilert, a leading incident response platform. With this integration, the incident management features and alerting capabilities of ilert and the real-time systems monitoring provided by Netdata can be leveraged. By combining both systems, users can not only monitor their infrastructure with fine detail as never before, but also assure the responsiveness of critical alerts to the correct teams swiftly.</p> <h2 id="what-is-ilert">What is ilert?</h2> <p><a href="https://www.ilert.com/?utm_campaign=Netdata&utm_source=integration&utm_medium=organic" target="_blank">ilert</a> is an end-to-end platform for alerting, on-call management, and status pages, built for the new-age DevOps and SRE teams. It streamlines the entire incident management process by automating key aspects and providing powerful tools to improve efficiency, such as automated on-call duty, multi-level escalations, alert grouping, postmortem document creation, and much more. ilert integrates with monitoring systems, like Netdata, and sends alerts through multiple channels (SMS, phone, push, Slack, Microsoft Teams, etc.), ensuring that teams can promptly respond to issues before they impact service.</p>What Is Application Performance Monitoring (APM)?https://www.netdata.cloud/academy/what-is-application-performance-monitoring-apm/Thu, 03 Oct 2024 00:00:00 +0000https://www.netdata.cloud/academy/what-is-application-performance-monitoring-apm/<p>Ensuring that applications are functioning as expected is essential in the software-driven world of today. One sub-standard performance and your app can fail to win people over, ultimately drive them away or be the reason for debilitating first impressions. This is where Application Performance Monitoring (APM) comes in and helps developers, DevOps teams, and especially an SRE (Site Reliability Engineer) to monitor their application running live on systems, allowing them to identify the issues faster before they impact users.</p>ChileAtiende Case Study: 25% Less AWS Downtimehttps://www.netdata.cloud/case-studies/government/chileatiende/Tue, 24 Sep 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/government/chileatiende/<h2 id="proactive-infrastructure-management-for-citizen-services">Proactive Infrastructure Management for Citizen Services</h2> <p>ChileAtiende, a government organization dedicated to delivering essential digital services, faced a growing challenge: ensuring the stability and reliability of its complex infrastructure. With an ever-expanding digital presence, the team needed an efficient way to monitor a hybrid environment that included containers, databases, and web services like nginx and Apache.</p> <p>The critical pain point for ChileAtiende was ensuring system reliability through real-time monitoring and quick response capabilities. They sought a solution that would allow them to anticipate potential problems and address them before they impacted the public.</p>TMB Case Study: Barcelona Transport Monitoringhttps://www.netdata.cloud/case-studies/transportation/tmb/Fri, 20 Sep 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/transportation/tmb/<h2 id="monitoring-a-complex-heterogeneous-infrastructure">Monitoring a Complex, Heterogeneous Infrastructure</h2> <p>Transports Metropolitans de Barcelona (TMB), the public transportation provider in Barcelona, manages a vast and varied infrastructure hosted on AWS and on bare metal. Monitoring this infrastructure presents significant challenges due to its heterogeneous nature—spanning Linux, Windows, Kubernetes, cloud, and on-premises environments.</p> <p>One of the main obstacles for TMB was finding a single tool capable of handling the breadth of this environment effectively. As the infrastructure evolved, it became essential to have a holistic view of all systems to avoid operational silos and improve response times to issues.</p>What is Alert Fatigue and How to Prevent Ithttps://www.netdata.cloud/academy/what-is-alert-fatigue-and-how-to-prevent-it/Fri, 20 Sep 2024 00:00:00 +0000https://www.netdata.cloud/academy/what-is-alert-fatigue-and-how-to-prevent-it/<h2 id="what-is-alert-fatigue">What is Alert Fatigue?</h2> <p>This is called alert fatigue where engineers especially <a href="https://www.netdata.cloud/academy/sre-vs-devops-what-are-the-main-differences-between-them/">DevOps SREs</a> and on-call teams become numb to the many notifications from their monitoring tools. Instead of quickly responding to important issues, engineers may start ignoring or missing crucial alerts due to the overwhelming number of notifications they receive. That is no small issue because that causes slower incident response times, possible service outages, and less reliability.</p> <p>Robust monitoring is a must-have in the high-speed world of cloud infrastructure and microservices. However, when every little spike sets off an alarm, it is hard to separate the wheat from the chaff, so to speak. So in the end, alerts lose their meaning and it becomes a society of ignoring alarms, even when they shouldn&rsquo;t be ignored.</p>What Is Observability? Definition, Benefits & How It Workshttps://www.netdata.cloud/academy/what-is-observability/Fri, 20 Sep 2024 00:00:00 +0000https://www.netdata.cloud/academy/what-is-observability/<h2 id="what-is-observability">What Is Observability?</h2> <p>Observability is the process of trying to figure out how a system works on the inside, by looking at what it does on the outside. It has even grown to be a central theme in today&rsquo;s technology stacks where it is used to guarantee system availability and speed, particularly in intricate distributed architectures. But it is not just about the data, it is about the knowledge derived from the data that would help keep the system healthy, diagnose problems, and optimize performance.</p>What Is Uptime Monitoring? All SREs & DevOps Teams Must Knowhttps://www.netdata.cloud/academy/what-is-uptime-monitoring/Thu, 19 Sep 2024 00:00:00 +0000https://www.netdata.cloud/academy/what-is-uptime-monitoring/<h2 id="uptime-monitoring-explained">Uptime Monitoring Explained</h2> <p>Keeping an eye on how well and how often servers, apps, services, and all the parts of your system are up and running is what <a href="https://www.netdata.cloud/blog/server-uptime-monitoring-why-do-we-need-it/">uptime monitoring</a> is all about. For people in <a href="https://www.netdata.cloud/academy/sre-vs-devops-what-are-the-main-differences-between-them/">Site Reliability Engineering (SRE) and DevOps teams</a>, making sure everything works almost all the time is super important. Keeping your services up and running means users run into less trouble and enjoy a more seamless connection without outages. This cuts down on the chance of expensive interruptions in business.</p>Synthetic Checks: Definition, Examples & Benefitshttps://www.netdata.cloud/academy/synthetic-checks-definition-and-everything-else-you-need-to-know/Wed, 18 Sep 2024 00:00:00 +0000https://www.netdata.cloud/academy/synthetic-checks-definition-and-everything-else-you-need-to-know/<h2 id="what-are-synthetic-checks">What Are Synthetic Checks?</h2> <p>Synthetic checks are proactive tests that simulate user interactions or network requests to monitor the availability and performance of services. Rather than waiting for an issue to be reported by a user, <a href="https://www.netdata.cloud/integrations/data-collection/synthetic-testing/">synthetic checks</a> continuously run automated checks to detect problems before they affect real users. This makes them an essential tool for DevOps and Site Reliability Engineers (SREs) who aim to maintain a reliable and responsive infrastructure.</p>Infrastructure Monitoring: Key Benefits, Types & Use Caseshttps://www.netdata.cloud/academy/what-is-infrastructure-monitoring-and-why-you-need-it/Tue, 17 Sep 2024 00:00:00 +0000https://www.netdata.cloud/academy/what-is-infrastructure-monitoring-and-why-you-need-it/<h2 id="what-is-infrastructure-monitoring">What Is Infrastructure Monitoring?</h2> <p><strong>Infrastructure monitoring</strong> is the practice of continuously tracking the performance, availability, and overall health of IT systems such as servers, databases, networks, cloud services and so many more. To put it simply, it&rsquo;s about having clear visibility into how all the components of your applications and your entire infrastructure in general, are behaving. This is why we need and use the so-called monitoring / observability tools.</p>Important Changes to the Netdata Agent Dashboardhttps://www.netdata.cloud/blog/important-changes-to-the-netdata-agent-dashboard/Mon, 12 Aug 2024 00:00:00 +0000https://www.netdata.cloud/blog/important-changes-to-the-netdata-agent-dashboard/<p><em>Important Notice: These changes ONLY impact users of the Netdata Agent Dashboard not connected to Netdata Cloud.</em></p> <p>Dear Netdata Community,</p> <p>We are writing to inform you of upcoming changes to the Netdata Agent Dashboard, which will take effect in the coming weeks. This change impacts users from the soon to be released Netdata v2.0 onwards (and also on the Netdata v1.47 nightly releases). Currently, the Open-Source Netdata Agents allow unauthorized and unlimited Agent dashboard access. From Netdata v2.0 onwards, all Netdata Dashboards (Agent and Cloud) will offer exactly the same functionality under the same policy. Netdata Agent Dashboard will use Netdata Cloud as an SSO provider, ensuring dashboard access is authenticated and validated by Netdata Cloud, users will have the option to proceed with an unauthorized local dashboard but this will no longer be the default.</p>Analyze & Reduce Disk I/O Bottlenecks: Top Techniqueshttps://www.netdata.cloud/academy/reduce-disk-io-bottlenecks/Mon, 01 Jul 2024 00:00:00 +0000https://www.netdata.cloud/academy/reduce-disk-io-bottlenecks/<h2 id="understanding-disk-io-bottlenecks">Understanding Disk I/O Bottlenecks</h2> <p>Disk I/O (Input/Output) bottlenecks can severely impact the performance of your applications and services. These bottlenecks occur when the disk subsystem cannot keep up with the read/write requests from the CPU or memory, leading to slow response times and degraded performance. As a DevOps or SRE professional, understanding how to analyze and reduce these bottlenecks is crucial for maintaining optimal system health.</p> <h2 id="identifying-disk-io-bottlenecks">Identifying Disk I/O Bottlenecks</h2> <p>Before you can tackle disk I/O bottlenecks, you need to identify them accurately. Effective identification involves using a combination of monitoring tools and understanding key metrics.</p>Motohunt Case Study: Automotive Industry Monitoringhttps://www.netdata.cloud/case-studies/automotive/motohunt/Thu, 27 Jun 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/automotive/motohunt/<h2 id="navigating-system-complexity-with-netdata">Navigating System Complexity with Netdata</h2> <p>Motohunt is a big player in the automotive technology sector, delivering innovative products to the moto lovers. The organization&rsquo;s dedication to maintaining a healthy production environment and understanding data evolution across systems underscores its commitment to excellence. Netdata emerged as a key player in addressing Motohunt&rsquo;s primary challenge of monitoring system health.</p> <blockquote> <p>&ldquo;Netdata&rsquo;s out-of-the-box functionality and real-time analytics have been instrumental in maintaining our system&rsquo;s health. Its value efficiency and comprehensive coverage &lsquo;just works,&rsquo; providing us with immediate insights without a hefty price tag.&rdquo;</p>Webinar: Maximize Uptime With Powerful Monitoringhttps://www.netdata.cloud/academy/webinar-maximize-uptime-minimize-stress-powerful-monitoring-solutions/Thu, 27 Jun 2024 00:00:00 +0000https://www.netdata.cloud/academy/webinar-maximize-uptime-minimize-stress-powerful-monitoring-solutions/<iframe width="100%" height="450" src="https://www.youtube.com/embed/xOJwlU_cYAE?si=nidihOQR9VN72jqg" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> <p>Selecting the right observability solution is essential for maintaining the performance and reliability of your IT infrastructure. With countless options available, making an informed decision can be challenging. This webinar will provide you with a comprehensive guide to navigating this complex process.</p> <p>We&rsquo;ll explore the critical factors to consider, such as scalability, ease of use, integration capabilities, and cost-effectiveness. You&rsquo;ll gain insights into best practices for evaluating and implementing monitoring tools that align with your business goals and technical requirements.</p>High CPU Usage Detected How To Fix CPU Overloadhttps://www.netdata.cloud/academy/how-to-fix-cpu-overload/Mon, 10 Jun 2024 00:00:00 +0000https://www.netdata.cloud/academy/how-to-fix-cpu-overload/<p>You get an alert: &ldquo;High CPU usage detected on server-db-01.&rdquo; Your application feels sluggish, users are reporting timeouts, and the system is becoming unresponsive. A maxed-out CPU is a clear sign of trouble, grinding your operations to a halt and putting your service reliability at risk. But what does high CPU usage actually mean, and more importantly, how do you fix it?</p> <p>Sustained high CPU usage, often pegged at 100%, means your server&rsquo;s processor is completely saturated. It&rsquo;s trying to handle more tasks than it&rsquo;s capable of, leading to performance degradation, increased latency, and potential crashes. For DevOps engineers, SREs, and developers, quickly diagnosing and resolving a CPU overload is a critical skill. This guide will walk you through identifying the culprits and restoring your system to optimal health.</p>How To Achieve High Availability In CI/CD With Observabilityhttps://www.netdata.cloud/academy/ci-cd-high-availability/Sun, 09 Jun 2024 00:00:00 +0000https://www.netdata.cloud/academy/ci-cd-high-availability/<p>Your CI/CD pipeline is the backbone of your software delivery process. When it works, code flows smoothly from commit to production. But what happens when it breaks? A failed pipeline means stalled feature releases, delayed bug fixes, and frustrated developers unable to ship their work. To prevent this, you need to treat your CI/CD infrastructure with the same rigor as your production applications, and that starts with making it highly available.</p>Key Observability Metrics | Infrastructure & APM Monitoringhttps://www.netdata.cloud/academy/a-guide-to-the-most-important-observability-metrics/Thu, 06 Jun 2024 00:00:00 +0000https://www.netdata.cloud/academy/a-guide-to-the-most-important-observability-metrics/<h2 id="what-is-observability-the-fundamentals">What Is Observability? The Fundamentals</h2> <p>Noone can argue that observability is crucial for maintaining the health and performance of applications and infrastructure. Observability refers to the ability to measure and understand the state of a system based on the outputs it produces. This is extremely important for identifying, diagnosing, and resolving issues effectively and efficiently.</p> <p>Observability is essential for DevOps and <a href="https://www.ibm.com/think/topics/site-reliability-engineering" target="_blank">SRE</a> teams as it provides a comprehensive, overall view of the infrastructure’s health, enabling proactive maintenance and quicker incident response. It involves collecting and analyzing a variety of data types, including logs, metrics, and traces, to gain insights into system behavior and it can help discover possible anomalies throughout the whole infrastructure.</p>Introducing Netdata's Dynamic Configuration Managerhttps://www.netdata.cloud/blog/netdata-dynamic-configuration-manager/Wed, 05 Jun 2024 00:00:00 +0000https://www.netdata.cloud/blog/netdata-dynamic-configuration-manager/<p>We are thrilled to unveil the latest addition to the Netdata platform: the Dynamic Configuration Manager. This powerful new feature revolutionizes how you manage your monitoring and alerting configurations, making it easier and more efficient than ever before.</p> <!--truncate--> <h2 id="key-features-of-the-dynamic-configuration-manager"><strong>Key Features of the Dynamic Configuration Manager</strong></h2> <ol> <li>Create and Modify Alerts from Every Chart <ul> <li>You can now create and modify alerts directly from any chart on your dashboard or from the dedicated Alerts tab. This streamlined process allows for quick adjustments and ensures your monitoring is always aligned with your current needs.</li> </ul> </li> <li>Configure Collectors from the Integrations Section on the Dashboard <ul> <li>Currently available for go.d collectors, this feature lets you configure collectors straight from the Integrations section. This means you can quickly identify what Netdata can monitor and set up your configurations in one go, without having to dig through multiple settings pages.</li> </ul> </li> <li>Submit Configurations to Multiple Nodes with One Click <ul> <li>Managing configurations across a large infrastructure can be time-consuming. With the Dynamic Configuration Manager, you can now submit configurations to multiple nodes simultaneously, saving you valuable time and effort.</li> </ul> </li> <li>Construct and Copy Configurations for IaC Solutions <ul> <li>For those using Infrastructure as Code (IaC) solutions, this feature allows you to construct and copy configurations easily, integrating them into your IaC workflows. This ensures your configurations are consistent and reproducible across different environments.</li> </ul> </li> </ol> <h2 id="how-to-use-the-dynamic-configuration-manager"><strong>How to Use the Dynamic Configuration Manager</strong></h2> <p>To help you get started with the Dynamic Configuration Manager, we’ve put together a quick guide using the Netdata demo environment.</p>Effective Strategies for Managing PostgreSQL Deadlockshttps://www.netdata.cloud/academy/effective-strategies-for-managing-postgresql-deadlocks/Mon, 03 Jun 2024 00:00:00 +0000https://www.netdata.cloud/academy/effective-strategies-for-managing-postgresql-deadlocks/<p>Managing PostgreSQL deadlocks is critical for maintaining database performance and ensuring smooth application operations. Deadlocks occur when two or more transactions hold locks that the other transactions need, creating a cycle of dependencies with no resolution. This guide explores effective strategies for preventing and resolving deadlocks in PostgreSQL, helping <a href="https://www.netdata.cloud/solutions/built-for/devops/">DevOps</a> and <a href="https://www.netdata.cloud/solutions/built-for/sre/">Site Reliability Engineers (SREs)</a> ensure optimal <a href="https://www.netdata.cloud/academy/what-is-cardinality-in-databases-a-comprehensive-guide/">database performance</a>.</p> <h2 id="understanding-postgresql-deadlocks">Understanding PostgreSQL Deadlocks</h2> <h3 id="what-are-deadlocks">What Are Deadlocks?</h3> <p>A deadlock in PostgreSQL happens when two or more transactions block each other, each waiting for the other to release a lock. This mutual blocking results in a standstill where none of the transactions can proceed. PostgreSQL has mechanisms to detect and resolve deadlocks by aborting one of the transactions, but this can still lead to performance issues and data inconsistencies.</p>How to automate adding nodes to rooms in Netdata?https://www.netdata.cloud/blog/how-can-netdata-agents-be-placed-in-different-rooms-in-an-automated-way/Tue, 28 May 2024 00:00:00 +0000https://www.netdata.cloud/blog/how-can-netdata-agents-be-placed-in-different-rooms-in-an-automated-way/<p>How we organize nodes (and the Netdata agents that are running on those nodes) across different rooms should reflect our architectural decision because the room is a logical container with its own user members and notification rules. So if we are monitoring large infrastructure we should be consistent with these rules and one way to achieve this is to choose automation. <a href="https://registry.terraform.io/providers/netdata/netdata/latest">Netdata Cloud Terraform Provider</a> lets you automate this by provisioning all the cloud resources and giving you the credentials to spin up the Netdata Agents. In this article, we will concentrate on how in practice we can organize and assign nodes across different rooms in two scenarios, in each of them I&rsquo;m using <strong>non-production</strong> installation of the Netdata Agents:</p>How To Fix 504 Gateway Timeout Errors In NGINXhttps://www.netdata.cloud/academy/how-to-diagnose-and-fix-504-gateway-timeout-errors-in-nginx/Mon, 27 May 2024 00:00:00 +0000https://www.netdata.cloud/academy/how-to-diagnose-and-fix-504-gateway-timeout-errors-in-nginx/<p>Encountering a &lsquo;504 Gateway Timeout&rsquo; error in Nginx can be frustrating, especially when it disrupts the availability of your web applications. This error indicates that the server, while acting as a gateway or proxy, did not receive a timely response from the upstream server. This guide will help DevOps and Site Reliability Engineers (SRE) diagnose and fix these errors efficiently.</p> <h2 id="tldr">TL;DR</h2> <ul> <li>A 504 Gateway Timeout means Nginx, acting as a proxy, didn&rsquo;t get a response from the upstream server in time, so the problem sits in the backend, the network, or your timeout settings rather than in Nginx itself.</li> <li>Diagnose before you change anything: check the Nginx and upstream logs, measure backend response time with curl, and test connectivity with ping, traceroute, or mtr.</li> <li>The fastest stopgap is raising Nginx&rsquo;s timeout directives, but the durable fix is making the upstream faster through resource scaling, query optimization, and load balancing.</li> <li>Adding Nginx caching reduces how often requests hit the upstream at all, which keeps a strained backend responsive and cuts down 504s.k.</li> </ul> <h2 id="understanding-the-504-gateway-timeout-error">Understanding The &lsquo;504 Gateway Timeout&rsquo; Error</h2> <p>The &lsquo;504 Gateway Timeout&rsquo; error typically occurs in Nginx when:</p>How to Troubleshoot Slow Queries in MongoDBhttps://www.netdata.cloud/academy/how-to-troubleshoot-slow-queries-in-mongodb/Mon, 27 May 2024 00:00:00 +0000https://www.netdata.cloud/academy/how-to-troubleshoot-slow-queries-in-mongodb/<p>MongoDB is a popular NoSQL database known for its flexibility and scalability. However, as with any database system, you might encounter slow queries that can impact the <a href="https://www.netdata.cloud/academy/what-is-application-performance-monitoring-apm/">performance of your application</a>. In this guide, we’ll walk you through the steps to troubleshoot and optimize slow queries in MongoDB, ensuring your database runs efficiently.</p> <h2 id="understanding-the-basics">Understanding the Basics</h2> <p>Before diving into troubleshooting, it&rsquo;s important to understand some basic concepts in MongoDB:</p> <ul> <li><strong>Collections and Documents:</strong> MongoDB stores data in collections, which are analogous to tables in relational databases. Each collection contains documents, which are JSON-like data structures.</li> <li><strong>Indexes:</strong> Indexes improve query performance by allowing the database to quickly locate the data without scanning every document.</li> <li><strong>Query Plans:</strong> MongoDB evaluates different ways to execute a query and chooses the most efficient plan.</li> </ul> <h3 id="identifying-slow-queries">Identifying Slow Queries</h3> <p>Using the <code>slowms</code> Parameter MongoDB logs operations that take longer than a specified threshold. By default, this threshold (<code>slowms</code>) is set to 100 milliseconds. You can adjust this setting to catch slower operations more effectively:</p>DevOps Best Practices Playbook For Performancehttps://www.netdata.cloud/academy/devops-playbook-best-practices-for-success/Wed, 22 May 2024 00:00:00 +0000https://www.netdata.cloud/academy/devops-playbook-best-practices-for-success/<p>In software development and IT operations, DevOps has become a central practice, facilitating collaboration, increasing efficiency, and ensuring high-quality software delivery. However, the range of DevOps operations can be intimidating for beginners. This playbook aims to simplify DevOps by outlining best practices for developers and teams, enabling more efficient workflows and operational excellence.</p> <h2 id="devops-meaning-bridging-software-development--it-operations">Devops Meaning: Bridging Software Development &amp; IT Operations</h2> <p>DevOps is a cultural and technical shift that bridges the historically isolated worlds of software development and IT operations. The goal is to construct a fully automated pipeline for developing, testing, delivering, and maintaining software. Think of it as running a race where each runner hands off the baton seamlessly, boosting overall speed and efficiency.</p>How To Speed Up Windows 10 & 11: Performance Tipshttps://www.netdata.cloud/academy/how-to-speed-up-windows/Fri, 17 May 2024 00:00:00 +0000https://www.netdata.cloud/academy/how-to-speed-up-windows/<p>Dealing with a slow computer is frustrating. Whether you&rsquo;re compiling code, running <a href="https://www.netdata.cloud/academy/container-vs-vm-which-is-better-for-you/">virtual machines</a>, analyzing data, or just trying to browse documentation, sluggish performance pc issues can significantly hinder your productivity and break your focus. Waiting for applications to load or the system to respond eats up valuable time and can turn simple tasks into chores. Fortunately, there are numerous ways to speed up computer performance on Windows.</p> <p>This guide provides actionable tips to optimize pc responsiveness, ranging from simple maintenance routines and software adjustments to more impactful hardware upgrades. We&rsquo;ll cover how to improve computer performance and get your Windows system running smoothly again.</p>What Is An HPC Cluster - Key Components & How It Workshttps://www.netdata.cloud/academy/what-is-an-hpc-cluster/Wed, 01 May 2024 00:00:00 +0000https://www.netdata.cloud/academy/what-is-an-hpc-cluster/<p>Imagine needing to analyze petabytes of genomic data, simulate the airflow over a new aircraft wing, or predict complex financial market movements. A single computer, no matter how powerful, would struggle or take an impractically long time. This is where High-Performance Computing (HPC) clusters come in. They provide the immense computational power needed to tackle problems far beyond the reach of standard computing. If you&rsquo;re stepping into roles involving large-scale data processing or complex simulations, understanding HPC clusters is essential.</p>Costa Tsaousis Interview: Homelab Show Insightshttps://www.netdata.cloud/blog/interview-recap-with-costa-tsaousis-ceo-of-netdata-insights-from-the-homelab-show/Fri, 26 Apr 2024 00:00:00 +0000https://www.netdata.cloud/blog/interview-recap-with-costa-tsaousis-ceo-of-netdata-insights-from-the-homelab-show/<p>Costa Tsaousis, founder and chief visionary of Netdata, recently shared his expertise on real-time monitoring&rsquo;s pivotal role in modern IT landscapes during an episode of ‘The Homelab Show’ on YouTube. If you missed the live stream, here’s an essential summary of the discussion’s key points.</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/WvXab8MkRS4?si=QkJE_brYT3aZ1FZQ" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> <h2 id="the-necessity-of-real-time-monitoring">The Necessity of Real-Time Monitoring</h2> <p>Nowadays, data flows incessantly and operational demands are continuous, the importance of real-time monitoring cannot be overstated.</p>Decentralized Monitoring Explainedhttps://www.netdata.cloud/blog/decentralized-or-distributed-monitoring-explained/Thu, 11 Apr 2024 00:00:00 +0000https://www.netdata.cloud/blog/decentralized-or-distributed-monitoring-explained/<h2 id="introduction-to-distributed-observability">Introduction to Distributed Observability</h2> <p>Users often find themselves puzzled by the concepts of decentralized or distributed monitoring. This confusion is likely due to many monitoring systems claiming distributed capabilities, making it challenging to discern how Netdata stands out.</p> <p>To grasp the distinction, we must delve into the evolution of monitoring systems.</p> <p>When the first monitoring systems were created, about 20-25 years ago, they were built as SNMP collectors. The monitoring application was installed on a server, configured to discover network devices via SNMP, pulling data once every minute, per device. Simultaneously, the monitoring system was exposing a daemon to collect SNMP traps (key events generated by the network devices, pushed to the monitoring system).</p>Netdata is the only real-time monitoring solution: Justifiedhttps://www.netdata.cloud/blog/netdata-is-the-only-real-time-monitoring-solution-justified/Wed, 10 Apr 2024 00:00:00 +0000https://www.netdata.cloud/blog/netdata-is-the-only-real-time-monitoring-solution-justified/<p>In the digital era, where data flows like a ceaseless river, real-time monitoring stands as a pivotal technology, allowing organizations to not only keep pace but also to deeply understand the intricate dance of their operational ecosystems. This technology is not just about keeping tabs; it&rsquo;s about gaining a profound, almost intuitive sense of the micro-worlds within which systems, containers, services, and applications pulse and thrive.</p> <p>Real-time monitoring is the art and science of tracking system performance, activities, or transactions continuously and automatically, providing the ability to analyze and visualize data the moment it&rsquo;s generated.</p>Understanding Monitoring Toolshttps://www.netdata.cloud/blog/understanding-monitoring-tools/Wed, 10 Apr 2024 00:00:00 +0000https://www.netdata.cloud/blog/understanding-monitoring-tools/<p>If you care about operational excellence when it comes to your IT infrastructure, the role of monitoring systems is pivotal. As we navigate through the myriad of available monitoring tools, it becomes essential to understand the distinct architectures, styles, and focal points of various monitoring solutions, as well as the time-to-value they offer. This blog post aims to demystify the landscape of monitoring systems, providing a comprehensive overview that categorizes these tools into four primary architectural design principles.</p>SafetyDetectives: An Interview-With-Costa-Tsaousishttps://www.netdata.cloud/blog/safetydetectives/Mon, 01 Apr 2024 00:00:00 +0000https://www.netdata.cloud/blog/safetydetectives/<p>In a recent conversation with SafetyDetectives, Costa Tsaousis, CEO and founder of Netdata, shares insights into the inception and evolution of Netdata, a game-changing monitoring solution. With a background in fintech and a passion for real-time data processing, Tsaousis was driven to create Netdata in response to the significant gaps he identified in traditional monitoring tools. Emphasizing the importance of real-time data, comprehensive metrics collection, and the innovative use of machine learning, Tsaousis discusses how Netdata is setting new standards in the monitoring industry. His vision for Netdata not only challenges the status quo but also introduces a novel approach to cybersecurity, making it an essential tool for organizations worldwide.</p>Overcoming Monitoring Challenges in Shared VM Environmentshttps://www.netdata.cloud/case-studies/technology/id5/Thu, 28 Mar 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/technology/id5/<h2 id="optimizing-resource-management-in-complex-vm-ecosystems">Optimizing Resource Management in Complex VM Ecosystems</h2> <p>ID5 Web Solutions, a web solutions provider in Brazil, faced significant challenges in managing its shared VM environment. With a diverse clientele depending on their infrastructure, the need for precise and efficient resource usage identification per user was paramount. The company sought to not only allocate workloads more effectively but also to ensure fair pricing strategies based on actual consumption.</p> <p>The complexity of monitoring several shared VMs and the necessity for detailed user-specific resource usage insights posed substantial hurdles. Additionally, ID5 Web Solutions aimed to incorporate a seamless alerting mechanism via Discord, enhancing their response capabilities to incidents and optimizing service availability.</p>Transforming Server Monitoring across Diverse Hostshttps://www.netdata.cloud/case-studies/fintech/urios/Thu, 28 Mar 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/fintech/urios/<h2 id="mastering-monitoring-complexity">Mastering Monitoring Complexity</h2> <p>URIOS, operating in the financial services sector, faced a significant challenge in monitoring its diverse Linux server environments. Spread across various infrastructures and hosts, the complexity of managing these servers was growing. The organization required a solution that could centralize and unify its monitoring efforts, offering precise and numerous indicators to stay ahead of potential issues.</p> <p>The multitude of infrastructures and hosting providers made it difficult for them to maintain a consistent monitoring approach. They soon realized that they needed a tool that could bring everything together in a cohesive manner.</p>TTIC Case Study: Efficient System Monitoringhttps://www.netdata.cloud/case-studies/education/ttic/Thu, 28 Mar 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/education/ttic/<h2 id="enhancing-system-management-with-scarce-time-resources">Enhancing System Management with Scarce Time Resources</h2> <p>At the Toyota Technological Institute at Chicago, the challenge of system administration is uniquely compounded by the scarcity of time. As a one-man IT department, Adam Bohlander juggles various responsibilities, making efficient time management crucial. The institute&rsquo;s evolving needs demand a monitoring solution that aligns with its mission of leading in computer science and information technology research and education.</p> <blockquote> <p>&ldquo;I find the install quick and easy via ansible (my own playbooks) and defaults to be quite sane. This allows me to use it without investing that much time.&rdquo;</p>Manage Netdata Cloud with Terraformhttps://www.netdata.cloud/blog/netdata-terraform-provider/Wed, 27 Mar 2024 00:00:00 +0000https://www.netdata.cloud/blog/netdata-terraform-provider/<p>We proudly announce the release of the <a href="https://registry.terraform.io/providers/netdata/netdata/latest">Netdata Cloud Terraform Provider</a>.</p> <p>It&rsquo;s a step forward to make our platform more automated and compliant with the modern Infrastructure as Code approach. <a href="https://www.terraform.io/">Terraform</a> is one of the leaders in the IaC tools with a rich ecosystem of providers and modules, now you can put a puzzle with Netdata Cloud to your stack.</p> <p>The initial iteration of the Netdata Cloud Terraform Provider supports the following resources:</p>University of Calgary: Netdata in Academiahttps://www.netdata.cloud/case-studies/education/calgary-university/Tue, 26 Mar 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/education/calgary-university/<h2 id="empowering-academic-research-with-real-time-monitoring">Empowering Academic Research with Real-Time Monitoring</h2> <p>At the <strong>Machine Learning Lab</strong> at the <strong>University of Calgary</strong>, managing a robust infrastructure of servers and workstations is critical for advancing their research in machine learning (ML). Assistant Professor <strong>Yani Ioannou</strong> oversees this infrastructure, ensuring that these essential resources remain operational and are used to their fullest potential. The lab&rsquo;s challenge lies not just in the maintenance of these resources but in minimizing downtime to keep the research moving forward.</p>Enhancing E-Learning Through Proactive Monitoringhttps://www.netdata.cloud/case-studies/elearning/ingenium/Wed, 20 Mar 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/elearning/ingenium/<h2 id="tackling-e-learning-monitoring-challenges">Tackling E-learning Monitoring Challenges</h2> <p>Ingenium Digital Learning, a major player in the e-learning sector, faces unique challenges in delivering high-quality educational services online. One primary concern they had was managing disk space usage and CPU load effectively, as users continuously upload data without a clear view of their capacity limits. Additionally, unexpected spikes in server load, often due to unannounced large-scale events, further complicate resource management.</p> <blockquote> <p>&ldquo;Clients do not warn us of big events, which impacts the load on the servers. Users can upload data to our servers but don&rsquo;t have a view on their total capacity.&rdquo;</p>Dynatrace vs Datadog vs Instana vs Grafana vs Netdata!https://www.netdata.cloud/blog/netdata-vs-datadog-dynatrace-instana-grafana/Sun, 17 Mar 2024 00:00:00 +0000https://www.netdata.cloud/blog/netdata-vs-datadog-dynatrace-instana-grafana/<p>In this post, we delve into the comparative analysis of the commercial offerings of five leading monitoring solutions—Dynatrace, <a href="https://www.netdata.cloud/blog/5-datadog-alternatives/">Datadog</a>, Instana, Grafana, and Netdata. Our objective is to unravel the intrinsic value each of these services offers when applied to a real-world scenario. To accomplish this, we employed trial subscriptions of these services to monitor a set of Ubuntu servers and VMs, each hosting a pair of widely-used applications: NGINX and PostgreSQL, along with a couple of Docker and LXC containers. Additionally, we extended our monitoring to physical servers to evaluate the efficacy of these tools in capturing hardware and sensor data along with VMs monitored from the host.</p>Monitoring Industrial Equipment Manufacturing with Netdatahttps://www.netdata.cloud/case-studies/manufacturing/autonoma/Thu, 14 Mar 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/manufacturing/autonoma/<h2 id="empowering-precision-and-efficiency">Empowering Precision and Efficiency</h2> <p>Autonoma Technologies GmbH, a leader in the industrial equipment manufacturing sector, has been at the forefront of integrating digital solutions to address the complexities of modern industrial challenges. Monitoring many different services without clear insights into critical metrics for each, Autonoma turned to Netdata for a solution. The need for deep knowledge across various services to identify and monitor critical metrics was a significant hurdle.</p> <p>With a primary focus on monitoring vital systems like disk space, RabbitMQ, VerneMQ, NGINX, Redis, Fail2ban, and Kubernetes clusters, Autonoma required a robust and flexible tool to keep its production setup fast and reliable. Netdata became their solution of choice, offering out-of-the-box analysis for specific services that drastically cut down the time and effort needed for creating and adapting dashboards.</p>New Streamlined Plan Structurehttps://www.netdata.cloud/blog/netdata-unified-plans/Wed, 06 Mar 2024 00:00:00 +0000https://www.netdata.cloud/blog/netdata-unified-plans/<blockquote> <p><strong>UPDATE:</strong> Netdata is introducing a streamlined plan structure, sunsetting Early Bird plans on 13-03-2024.</p> </blockquote> <!--truncate--> <p>As the landscape of real-time monitoring evolves, so does the diversity and complexity of use cases that our community brings to Netdata. Our mission has always been to democratize monitoring by making it accessible, powerful, and scalable for everyone. With the rapid growth of our user base and their expanding needs, it&rsquo;s become clear that our plan structure must evolve to maintain this mission sustainably.</p>ACPro Case Study: Effortless Manufacturing Monitoringhttps://www.netdata.cloud/case-studies/manufacturing/acpro/Tue, 27 Feb 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/manufacturing/acpro/<h2 id="unifying-monitoring-across-diverse-environments">Unifying Monitoring Across Diverse Environments</h2> <p>ACPro faced the challenge of overseeing a wide array of in-house applications scattered across numerous servers, all without a monitoring solution in place. This lack of visibility made it difficult to maintain the high uptime and availability standards that are critical in the manufacturing industry. The search for a monitoring tool that was both comprehensive and user-friendly led ACPro to Netdata, which stood out for its intuitive interface and extensive, yet easily digestible, metrics.</p>InRento Case Study: Fintech Cloud Monitoring Winshttps://www.netdata.cloud/case-studies/fintech/inrento/Tue, 27 Feb 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/fintech/inrento/<h2 id="simplifying-complex-cloud-environments">Simplifying Complex Cloud Environments</h2> <p>The migration of Inrento&rsquo;s infrastructure to the cloud introduced a new set of challenges, particularly in monitoring multiple servers with diverse roles. The transition from a single server environment to a distributed application on AWS required a solution that not only automated the monitoring process but also made it accessible and understandable to developers accustomed to a monolithic setup.</p> <blockquote> <p>&ldquo;Netdata enables automated integration of new servers into our architecture. As we experiment with various configurations, we can leverage automated configuration that is prepared beforehand.&rdquo;</p>Reduced Costs & Kubernetes Efficiencyhttps://www.netdata.cloud/case-studies/technology/7-oaks-group/Tue, 27 Feb 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/technology/7-oaks-group/<h2 id="simplifying-complexity-with-netdata">Simplifying Complexity with Netdata</h2> <p>At 7 Oaks Group, our journey with Netdata began out of curiosity and a desire to move away from the frustrations of complex monitoring setups. Our infrastructure, primarily composed of <strong>Kubernetes clusters and a selection of EC2/VM instances</strong>, required a monitoring solution that could provide instant, meaningful insights without the hassle of intricate configuration. The immediate value we discovered in Netdata was nothing short of revolutionary, offering us a level of insight into our systems that was both effortlessly attainable and profoundly impactful.</p>Easy Doc: Revolutionizing IT Operations with Netdatahttps://www.netdata.cloud/case-studies/technology/easydocs/Tue, 13 Feb 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/technology/easydocs/<h2 id="overcoming-it-operational-challenges">Overcoming IT Operational Challenges</h2> <p>At Easy Doc Soluções Integradas, navigating the complexities of docker swarm cluster infrastructure presented significant challenges, particularly in monitoring the health and availability of containers and cluster nodes. The primary pain point was the difficulty in detecting and diagnosing the reasons behind API unavailability, especially since container restarts resulted in the loss of crucial logs. This obstacle hindered our ability to maintain high levels of service availability and performance, directly impacting our operational efficiency and customer satisfaction.</p>Streamlining IT Operations with Netdatahttps://www.netdata.cloud/case-studies/technology/clew/Tue, 13 Feb 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/technology/clew/<h2 id="addressing-monitoring-complexity">Addressing Monitoring Complexity</h2> <p>The main challenge for the organization was ensuring up-to-date, comprehensive monitoring across a diverse infrastructure, complicated by different operating systems, security requirements, and network segmentation. The varied nature of their environment made it difficult to maintain a unified view of system health and performance, often leading to delayed root cause analysis and inefficient troubleshooting processes.</p> <p>Netdata&rsquo;s ease of deployment and out-of-the-box functionality have been game-changers, offering immediate visibility into their systems&rsquo; health with minimal setup. Its comprehensive monitoring capabilities allowed them to quickly identify and address issues, reducing the time and effort previously required for these tasks.</p>Upcoming Homelab Planhttps://www.netdata.cloud/blog/netdata-homelab-plan/Wed, 07 Feb 2024 00:00:00 +0000https://www.netdata.cloud/blog/netdata-homelab-plan/<blockquote> <p><strong>UPDATE:</strong> On the 2024-02-08 A new Netdata Cloud Homelab plan will become available. This is aimed for home users and students.</p> </blockquote> <h2 id="what-you-need-to-know">What you need to know?</h2> <ul> <li> <p>New Plan alert: We&rsquo;re introducing a dedicated plan on Netdata Cloud—the Homelab plan. It&rsquo;s tailored to meet the needs of home users and students, offering unrestricted access to Netdata features without the limitations seen in the Community plan.</p> </li> <li> <p>Exclusively for Personal Use: The Homelab plan is designed for personal, non-commercial use only. To qualify, users will need to self-certify as a home user or student during the sign-up process.</p>Codyas: Global Server Management with Netdatahttps://www.netdata.cloud/case-studies/technology/codyas/Thu, 01 Feb 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/technology/codyas/<h2 id="overcoming-server-management-hurdles">Overcoming Server Management Hurdles</h2> <p><a href="https://www.codyas.com/">Codyas</a> faces the intricate challenge of managing a vast array of servers, equipped with different technologies for various clients around the globe. The primary obstacle has been the allocation of limited time and personnel towards monitoring tasks, which detracted from the organization&rsquo;s core focus on development and customer service.</p> <blockquote> <p>&ldquo;Netdata&rsquo;s ease of installation and configuration has been a game-changer for us, allowing quick setup and efficient monitoring across our diverse server landscape,&rdquo;</p>Enhancing Research Through Advanced Monitoringhttps://www.netdata.cloud/case-studies/education/landcare/Thu, 01 Feb 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/education/landcare/<h2 id="helping-scientists-focus-on-the-science">Helping Scientists focus on the Science</h2> <p>At <a href="https://www.landcareresearch.co.nz/">Manaaki Whenua – Landcare Research</a>, managing multi-user Linux workstations for scientific computing presented a unique challenge. Tasked with overseeing system utilization without a dedicated role in the organization, the need for a solution that was intuitive and efficient became paramount. Netdata&rsquo;s simplicity in setup and the ability to monitor systems remotely via the cloud addressed these challenges head-on, offering a seamless solution for workstation management.</p>From Bottlenecks to Breakthroughshttps://www.netdata.cloud/case-studies/technology/lancom-systems/Thu, 01 Feb 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/technology/lancom-systems/<h2 id="simplifying-it-monitoring-challenges">Simplifying IT Monitoring Challenges</h2> <p>At LANCOM Systems, the transition to a more integrated and efficient IT monitoring system was driven by a desire to streamline operations and overcome the challenges associated with complex system monitoring. The company faced significant hurdles in integrating services within Docker containers and adapting to the programming language Go, despite a strong preference for Python. This challenge was further compounded by the need for a comprehensive monitoring solution that could offer extensive out-of-the-box features without necessitating extensive development work.</p>Leica Biosystems: Advancing Cancer Diagnosticshttps://www.netdata.cloud/case-studies/healthcare/leica/Thu, 01 Feb 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/healthcare/leica/<h2 id="navigating-offline-monitoring-challenges">Navigating Offline Monitoring Challenges</h2> <p><a href="https://www.leicabiosystems.com/">Leica Biosystems</a>, a leader in pathology and cancer diagnostics, faced a unique challenge: monitoring and observability in strictly offline environments. The need for a dashboard providing system insights in an offline capacity was paramount, especially given the constraints of remote access impossibility due to the offline nature of the devices used.</p> <blockquote> <p>&ldquo;Monitoring complexity in offline environments was a significant hurdle. Netdata&rsquo;s ability to export metrics allowed us to achieve the observability we needed without the need for online connectivity.&rdquo;</p>Monitoring on Autopilothttps://www.netdata.cloud/case-studies/hosting/webnestify/Thu, 01 Feb 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/hosting/webnestify/<h2 id="overcoming-scalability-issues">Overcoming Scalability Issues</h2> <p>Simon Gajdosik, the driving force behind <a href="https://webnestify.cloud/">Webnestify</a>, identified scalability and maintainability as primary challenges in their monitoring strategy. The traditional approach with <strong>Grafana and Prometheus, although effective, became untenable at scale</strong>. Netdata Cloud provided the much-needed solution, offering automated monitoring that effortlessly scales with the business, eliminating the complexity of manual configurations.</p> <h2 id="enhancing-operations-with-netdata">Enhancing Operations with Netdata</h2> <p><a href="https://webnestify.cloud/">Webnestify</a>&rsquo;s adoption of Netdata Cloud provided significant <strong>operational enhancements</strong>:</p> <ul> <li><strong>Time Savings:</strong> The automated service discovery and configuration capabilities of Netdata have saved Webnestify at least 10 hours weekly, allowing the team to focus more on business growth rather than infrastructure maintenance.</li> <li><strong>Productivity Improvements:</strong> With the efficiency gains from Netdata, Webnestify has increased its client onboarding capacity, directly contributing to business expansion.</li> <li><strong>Issue Resolution:</strong> The advanced alerting system of Netdata enabled proactive anomaly detection, preventing potential downtimes for critical ecommerce platforms and thereby ensuring uninterrupted service.</li> <li><strong>Cost Reduction:</strong> Shifting from a dedicated Grafana server to Netdata resulted in a 40% reduction in annual monitoring costs, translating to significant financial savings.</li> <li><strong>Enhanced Security:</strong> The ability to whitelist parent node IP addresses and use private IPs for child nodes improved the overall security posture.</li> <li><strong>Improved Troubleshooting and Metrics Accuracy:</strong> The intuitive dashboards and accurate metrics from Netdata have simplified the process of identifying and resolving issues, making troubleshooting 50% easier.</li> <li><strong>Downtime Reduction and SLA Improvements:</strong> With Netdata, Webnestify has seen a 20% reduction in downtime and significantly improved its SLA compliance by resolving issues more efficiently.</li> </ul> <blockquote> <p>&ldquo;A standout moment for us was when Netdata&rsquo;s anomaly detection alerted us to a potential issue, allowing us to avert a crisis on a server hosting over 100 high-traffic ecommerce sites. This instance underscored the indispensable role of Netdata in our operations,&rdquo;</p>Optimizing The FinTech Industryhttps://www.netdata.cloud/case-studies/fintech/yellow-brick-road/Thu, 01 Feb 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/fintech/yellow-brick-road/<h2 id="optimizing-the-fintech-industry-yellow-brick-roads-monitoring-journey-with-netdata">Optimizing The FinTech Industry: Yellow Brick Road&rsquo;s Monitoring Journey with Netdata</h2> <p><strong>Yellow Brick Road</strong>, a leader in the financial services industry, embarked on a mission to fine-tune its system and kernel parameters to minimize network latency crucial for quick trading decisions. The challenge was not just in identifying what to measure but also in how to effectively use the data obtained.</p> <h3 id="the-netdata-solution">The Netdata Solution</h3> <p>Netdata Cloud came to the rescue, offering <strong>comprehensive baseline monitoring</strong> that was both easy to deploy and cost-efficient. The adoption of Netdata, provided the team at Yellow Brick Road with the necessary tools to monitor their Nomad, Consul, bare metal, and systemd applications efficiently.</p>Real-Time Insights for Reliable Web Hostinghttps://www.netdata.cloud/case-studies/hosting/trillium/Thu, 01 Feb 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/hosting/trillium/<h2 id="simplifying-monitoring-for-enhanced-performance">Simplifying Monitoring for Enhanced Performance</h2> <p>Trillium was confronted with the challenge of finding an effective monitoring solution that could be easily integrated with their systems, despite the non-technical background of some team members. The company aimed to uphold its commitment to outstanding service uptime and performance—a critical aspect in the hosting industry. The search for a monitoring tool that could provide comprehensive insights into the health of their infrastructure, particularly RAM and CPU usage, and uptime tracking, led them to Netdata.</p>Streamlining VM Monitoring with Netdatahttps://www.netdata.cloud/case-studies/technology/comtegra/Thu, 01 Feb 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/technology/comtegra/<h2 id="simplifying-virtual-machine-monitoring">Simplifying Virtual Machine Monitoring</h2> <p>Comtegra, a leader in IT solutions for storage and virtualization, faced a significant challenge in managing a dynamic environment of virtual machines (VMs). The frequent deployment and deletion of VMs, often within a single day, created a complex scenario that was both time-consuming and difficult to monitor. This challenge was particularly pronounced for Mariusz Mieszkowski, a storage specialist at Comtegra, who noted the inefficiency of performance testing and overall infrastructure management under these conditions.</p>Transforming Container and Server Health Insightshttps://www.netdata.cloud/case-studies/gaming/nodecraft/Thu, 01 Feb 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/gaming/nodecraft/<h2 id="revolutionizing-infrastructure-monitoring">Revolutionizing Infrastructure Monitoring</h2> <p>Nodecraft faced significant challenges in monitoring its ever-expanding fleet of dedicated servers and containers. The complexity of tracking system health and hardware performance became a bottleneck, impacting its ability to deliver the seamless gaming experiences Nodecraft is known for. With a small development team, the creation and maintenance of a custom solution were out of the question. Nodecraft&rsquo;s journey towards finding a solution led it to Netdata, which has been transformative.</p>Transforming critical software developmenthttps://www.netdata.cloud/case-studies/technology/adastec/Thu, 01 Feb 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/technology/adastec/<h2 id="revolutionizing-vehicle-automation">Revolutionizing Vehicle Automation</h2> <p><a href="https://www.adastec.com/">ADASTEC</a>, a frontrunner in automated driving software for commercial vehicles, utilizes Netdata to ensure the highest standards of reliability and efficiency in their operations. Specializing in SAE Level-4 automation, ADASTEC empowers OEMs to craft modern, automated, and connected vehicles. The challenge of distinguishing crucial alerts within their software stack posed a significant hurdle, as Tayfun Yurdaer, a DevOps specialist at ADASTEC, explains. The essential task was identifying alerts pivotal for the mission-critical applications to respond appropriately, amidst the complexity of their software environment.</p>Empowering Digital Transformationhttps://www.netdata.cloud/case-studies/government/falkland/Tue, 30 Jan 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/government/falkland/<h2 id="maximizing-resources-elevating-services">Maximizing Resources, Elevating Services</h2> <p>The <a href="https://www.falklands.gov.fk/">Falkland Islands Government</a> faced critical challenges in gaining visibility into the resource consumption of its digital assets. This lack of clarity hindered the ability to efficiently manage alerts and optimize resource usage across digital platforms. The integration of better monitoring tools was imperative to overcoming these obstacles and ensuring the seamless provision of government services.</p> <blockquote> <p>&ldquo;Not having a clear picture on the resource consumption of our digital assets was a major challenge. With Netdata agent, I am now able to get a comprehensive set of data about each of my nodes, which has revolutionized how we manage resources and handle alerts.&rdquo;</p>Revolutionizing Device Monitoring at SafeSizehttps://www.netdata.cloud/case-studies/retail/safesize/Tue, 30 Jan 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/retail/safesize/<h2 id="enhancing-efficiency--transparency-in-retail">Enhancing Efficiency &amp; Transparency in Retail</h2> <p><a href="https://www.safesize.com/">SafeSize</a>, a trailblazer in the retail technology sector, leverages innovative 3D foot scanning and shoe recommendation solutions to enhance the shopping experience in both physical and online stores. However, managing and monitoring devices installed in diverse customer environments posed significant challenges. These devices, crucial for delivering SafeSize&rsquo;s cutting-edge service, operate in varied network environments with limited access, necessitating a monitoring solution that is both efficient and resource-light.</p>Revolutionizing Server Monitoring at Tilkalhttps://www.netdata.cloud/case-studies/logistics/tilkal/Tue, 30 Jan 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/logistics/tilkal/<h2 id="tackling-server-monitoring-complexity">Tackling Server Monitoring Complexity</h2> <p>At <a href="https://www.tilkal.com/">Tilkal SAS</a>, the challenge of aggregating infrastructure information from numerous standalone Linux servers into a singular platform was significant. The complexity was further compounded by the need to incorporate custom metrics emitted by proprietary services, alongside standard system statistics. This requirement for a holistic view of both standard and custom data sources necessitated a versatile and powerful monitoring tool.</p> <blockquote> <p>&ldquo;The data we wanted to collect was not only standard monitoring stats but also custom stats emitted by our own services. Netdata&rsquo;s ease of deployment and its cloud app&rsquo;s capability to consolidate server stats in one place were exactly what we needed.&rdquo;</p>Simplifying Complex Monitoring for Educational Institutionshttps://www.netdata.cloud/case-studies/education/funiber/Tue, 30 Jan 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/education/funiber/<h2 id="navigating-a-complex-monitoring-terrain">Navigating a Complex Monitoring Terrain</h2> <p>The Fundación Universitaria Iberoamericana (<a href="https://www.funiber.us/">FUNIBER</a>), with its expansive network of institutions and students across Spain and beyond, faces the unique challenge of managing and configuring monitoring tools across a dynamically evolving IT infrastructure, compounded by the task of integrating data from disparate sources. The organization&rsquo;s IT landscape is characterized by rapid changes, requiring flexible and adaptable monitoring solutions. Compatibility issues with legacy systems and proprietary data formats further complicate the seamless integration of monitoring data, presenting significant obstacles to maintaining a cohesive and efficient monitoring strategy. Jesús Ramos, a seasoned DevOps professional at FUNIBER, found himself at the crux of these challenges.</p>BPF vs eBPF: Key Differences Explained For DevOps & SREshttps://www.netdata.cloud/academy/what-are-the-differences-between-bpf-and-ebpf-an-overview/Mon, 29 Jan 2024 00:00:00 +0000https://www.netdata.cloud/academy/what-are-the-differences-between-bpf-and-ebpf-an-overview/<h2 id="introduction-to-bpf--ebpf">Introduction To BPF &amp; eBPF</h2> <p>For DevOps and Site Reliability Engineers (SREs), understanding and applying the right tools for monitoring and troubleshooting is crucial. Among the various technologies available, BPF (Berkeley Packet Filter) and its extended version, eBPF (extended Berkeley Packet Filter), have emerged as powerful tools. But what exactly are BPF and eBPF, and how do they differ? This article will delve into the basics of both, highlight their differences, and explore their applications in modern DevOps and SRE practices, with a special focus on observability.</p>Enhancing Digital Media Excellence with Netdatahttps://www.netdata.cloud/case-studies/digital-media/shed/Mon, 29 Jan 2024 00:00:00 +0000https://www.netdata.cloud/case-studies/digital-media/shed/<h2 id="navigating-network-complexity">Navigating Network Complexity</h2> <p><a href="https://shedmtl.com/">SHED</a> encountered a critical pain point in swiftly and accurately identifying bandwidth hogs within their network. This was a significant issue, as monitoring these elements was essential to pinpoint devices, applications, or users causing excessive bandwidth consumption. The lack of real-time visibility and comprehensive insights into data transfer rates and traffic patterns was a major hurdle in their ability to proactively manage and optimize network resources. This limitation directly impacted their network performance, leading to potential slowdowns or bottlenecks, affecting the efficiency of their operations. Moreover, this challenge posed risks in resource allocation and maintaining a smooth user experience. Additionally, this issue had implications for security, as unidentified bandwidth hogs could indicate security threats or unauthorized activities. Thus, SHED Montreal&rsquo;s foremost challenge was the effective monitoring of file server and switch activities to swiftly identify and mitigate bandwidth hogs, crucial for ensuring optimal network performance, resource allocation, and maintaining a secure infrastructure.</p>SRE vs DevOps: Key Differences, Synergies & Roles Explainedhttps://www.netdata.cloud/academy/sre-vs-devops-what-are-the-main-differences-between-them/Mon, 29 Jan 2024 00:00:00 +0000https://www.netdata.cloud/academy/sre-vs-devops-what-are-the-main-differences-between-them/<p>If you’re new to IT operations and software development, you&rsquo;ve likely encountered the terms SRE (Site Reliability Engineering) and DevOps. Both play crucial roles in modern tech organizations, but understanding the differences between SRE and DevOps can be confusing. This article aims to clarify these concepts, explain their roles, and show how they work together to enhance software delivery and system reliability.</p> <h2 id="a-brief-history-of-devops--sre">A Brief History Of DevOps &amp; SRE</h2> <p>To better understand the philosophies behind DevOps and Site Reliability Engineering (SRE), it helps to look at how each approach emerged.</p>What Is Cardinality In Databases: A Comprehensive Guidehttps://www.netdata.cloud/academy/what-is-cardinality-in-databases-a-comprehensive-guide/Mon, 29 Jan 2024 00:00:00 +0000https://www.netdata.cloud/academy/what-is-cardinality-in-databases-a-comprehensive-guide/<h2 id="an-introduction-to-cardinality">An Introduction To Cardinality</h2> <p>Cardinality is a fundamental concept in databases that plays a crucial role in designing efficient databases and optimizing query performance. For those new to databases, understanding what is cardinality is essential for effective data management. This comprehensive guide will explain the meaning of cardinality, its types, and its <a href="https://www.netdata.cloud/monitoring-101/mongodb-monitoring/">impact on database performance</a>, making it accessible for both beginners and intermediate users.</p> <h2 id="what-is-cardinality-in-databases">What Is Cardinality In Databases?</h2> <p>Cardinality in databases refers to the uniqueness of data values contained in a column. It essentially measures how many distinct values exist in a column compared to the total number of rows in a table.</p>What Is Cloud Management? Ensure Security & Optimize Costshttps://www.netdata.cloud/academy/what-is-cloud-management-how-to-maximize-efficiency/Mon, 29 Jan 2024 00:00:00 +0000https://www.netdata.cloud/academy/what-is-cloud-management-how-to-maximize-efficiency/<p>Cloud computing has become a cornerstone for businesses of all sizes. As more organizations migrate their workloads to the cloud, understanding cloud management and how to maximize efficiency is crucial. But what is cloud management exactly? This article will explore the concept, dive into the various aspects of cloud management, and provide practical tips on how to enhance efficiency, especially for beginners.</p> <h2 id="what-is-cloud-management">What Is Cloud Management?</h2> <p>Cloud management involves the control, orchestration, and administration of cloud computing resources and services. It encompasses a range of tasks, from deploying and <a href="https://www.netdata.cloud/solutions/technologies/aws-monitoring/">monitoring applications</a> to ensuring security and compliance. Effective cloud management is essential for optimizing performance, controlling costs, and maintaining security across cloud environments.</p>What Is Continuous Profiling & Why It Mattershttps://www.netdata.cloud/academy/what-is-continuous-profiling-why-it-is-important-for-monitoring/Mon, 29 Jan 2024 00:00:00 +0000https://www.netdata.cloud/academy/what-is-continuous-profiling-why-it-is-important-for-monitoring/<h2 id="introduction-to-profiling-a-key-tool-for-developers">Introduction to Profiling: A Key Tool for Developers</h2> <p>Profiling is like a health checkup for your software. Just as doctors use various tests to understand how your body is performing, developers use profiling to understand how their applications are running. This process helps to find out which parts of the application are working well and which parts need improvement.</p> <h2 id="what-is-profiling">What Is Profiling?</h2> <p>Profiling, in simple terms, is the process of measuring how your program uses resources like CPU time and memory. Think of it as a way to see inside your application and understand what&rsquo;s going on.</p>IoT Monitoring Challenges: Key Issues & How To Overcome Themhttps://www.netdata.cloud/blog/iot-monitoring-challenges/Thu, 11 Jan 2024 00:00:00 +0000https://www.netdata.cloud/blog/iot-monitoring-challenges/<p>With the increasing prevalence of IoT devices, which are being used in a wide range of applications, from smart homes and cities to industrial and agricultural systems, monitoring thei performance and health is extremely important. However, it’s essential to remember that monitoring IoT devices involves more than just tracking device-level data. In addition, monitoring data from the IoT platform or application layer is equally important.</p> <p>We’ll explore some of these topics in more detail and explain how Netdata can play an essential role in the monitoring of such devices, including some hints on how it can be set up for maximum performance in such scenarios.</p>Introducing Netdata’s Alerts Configuration Managerhttps://www.netdata.cloud/blog/netdata-alerts-configuration-manager/Thu, 21 Dec 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-alerts-configuration-manager/<p>Netdata introduces its latest feature, the Alerts Configuration Manager, transforming the way users configure and manage alerts in their Netdata environment. This powerful tool integrates directly into the Netdata Dashboard, offering a streamlined and intuitive interface for both novice and experienced users.</p> <!--truncate--> <h2 id="what-is-the-alerts-configuration-manager">What is the Alerts Configuration Manager?</h2> <p>The Alerts Configuration Manager is an innovative feature available to users with Business subscriptions. It allows for the creation and customization of alerts directly from the Netdata Dashboard, employing a user-friendly UI wizard. This tool simplifies alert configuration, making it accessible and straightforward, even for those who are not deeply technical.</p>Cost Transparency: The True Cost Of Monitoringhttps://www.netdata.cloud/blog/netdata-cost-transparency-unveiling-the-true-cost-of-monitoring/Fri, 01 Dec 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-cost-transparency-unveiling-the-true-cost-of-monitoring/<p>Businesses are increasingly reliant on monitoring tools to ensure the seamless performance and reliability of their systems. However, the true cost of implementing and maintaining these tools is often obscured by hidden expenses. Our previous blog delved into the concealed costs associated with various monitoring solutions, such as Prometheus &amp; Grafana (Open Source Monitoring) and commercial platforms like Datadog, Dynatrace, and NewRelic. These costs can manifest in various forms - from complex setups and maintenance to additional charges for advanced features.</p>Understanding the Netdata Methodologyhttps://www.netdata.cloud/blog/netdata-methodology/Sat, 04 Nov 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-methodology/<p>In the dynamic landscape of modern infrastructure and multi cloud environments, observing and understanding system performance requires a new breed of tools—ones that keep pace with the &rsquo;living&rsquo; nature of modern infrastructure. This is the inflection point at which Netdata steps in, and aims to bring a fresh perspective to monitoring.</p> <h2 id="what-does-netdata-do-differently">What does Netdata do differently</h2> <p>There are key “cultural” faults that we believe hold the <a href="https://www.netdata.cloud/blog/monitoring-vs-observability">observability</a> industry back. Let’s take a look through the prism of these faults and understand what Netdata is doing differently to address them.</p>Netdata Best Practiceshttps://www.netdata.cloud/blog/netdata-best-practices/Fri, 03 Nov 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-best-practices/<p>Effective <strong>system monitoring</strong> is non-negotiable in today&rsquo;s complex IT environments. Netdata offers real-time performance and health monitoring with precision and granularity. But the key to harnessing its full potential lies in the optimization of your setup. Let’s ensure you are not just collecting data, but doing it in the most optimal way while gaining actionable insights from it.</p> <p>The starting point for optimization is a robust setup. Netdata is engineered for minimal footprint and can run on a wide range of hardware—from IoT devices to powerful servers. Time for a deep dive into each of these key areas and what the best practices you should follow, if you are serious about monitoring and optimizing your Netdata monitoring setup:</p>System Operators: The Role Of SysOps In IT Infrastructurehttps://www.netdata.cloud/blog/system-operators-unlock-log-management-mastery-with-systemd-journal-and-netdata/Fri, 03 Nov 2023 00:00:00 +0000https://www.netdata.cloud/blog/system-operators-unlock-log-management-mastery-with-systemd-journal-and-netdata/<p>System operators know the drill: as the complexity of systems scales, so does the deluge of logs. Traditionally, taming this relentless tide demands a concoction of costly tools and laborious configurations—until now. The dynamic duo of <code>systemd-journal</code> and Netdata is revolutionizing log management, turning what was once a Herculean task into a streamlined, powerful, and surprisingly straightforward process.</p> <h2 id="efficient-handling-of-volume-and-velocity">Efficient Handling of Volume and Velocity</h2> <p><code>systemd-journal</code> is built to manage the deluge of data that systems generate, <strong>without buckling under the speed and volume of incoming logs</strong>. It captures logs at the source, facilitating direct and immediate processing. By utilizing the journal&rsquo;s native mechanism to send logs to a central server, system operators can bypass the complexities of traditional <strong>log centralization methods</strong>.</p>Upcoming Changes To Netdata Cloud Planshttps://www.netdata.cloud/blog/netdata-plan-changes/Thu, 02 Nov 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-plan-changes/<blockquote> <p><strong>UPDATE</strong>: On the <strong>2023-11-08</strong> Node and Dashboard limits will be applied on the Netdata Cloud <strong>Community plan</strong>, while all current features of the Community plan will remain the same.</p> </blockquote> <h2 id="what-you-need-to-know">What you need to know?</h2> <ul> <li> <p>On Netdata Cloud Free Community plan, the number of <strong>active nodes</strong> that can be concurrently visualized on the Netdata dashboards, as well as the number of <strong>active custom dashboards</strong> for accounts created after 2023-11-07 will be subject to limits.</p>Netdata vs Prometheushttps://www.netdata.cloud/blog/netdata-vs-prometheus-performance-analysis/Sat, 28 Oct 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-vs-prometheus-performance-analysis/<p>In an era dominated by data-driven decision making, monitoring tools play an indispensable role in ensuring that our systems run efficiently and without interruption. When considering tools like <strong>Netdata and Prometheus</strong>, performance isn&rsquo;t just a number; it&rsquo;s about empowering users with <strong>real-time insights</strong> and enabling them to act with agility.</p> <p>There&rsquo;s a genuine need in the community for tools that are not only comprehensive in their offerings but also <strong>swift and scalable</strong>. This desire stems from our evolving digital landscape, where the ability to swiftly detect, diagnose, and <a href="https://www.netdata.cloud/solutions/technologies/kubernetes-monitoring/">rectify anomalies</a> has direct implications on user experiences and business outcomes. Especially as infrastructure grows in complexity and scale, there&rsquo;s an increasing demand for <strong>monitoring tools</strong> to keep up and provide clear, timely insights.</p>Discover The New Netdata!https://www.netdata.cloud/blog/discover-the-new-netdata/Fri, 27 Oct 2023 00:00:00 +0000https://www.netdata.cloud/blog/discover-the-new-netdata/<p>Missed the last <strong>Netdata</strong> updates? Here is what is new:</p> <h2 id="explore-your-systemd-journal-logs-with-netdata">Explore your systemd-journal logs with Netdata</h2> <p><img src="https://github.com/netdata/blog/assets/139226121/7d2779c9-0efb-4491-8fe3-aedce1dc72fb" alt="systemd-journal-logs"></p> <p>Netdata <a href="https://learn.netdata.cloud/docs/logs/systemd-journal/?utm_source=IL&amp;utm_medium=internallinking&amp;utm_campaign=new_netada">got a <code>systemd</code>-journal logs explorer</a> to analyze your <code>systemd</code>-journal logs, directly on their sources. By just installing <strong>Netdata</strong> on any systemd based system, Netdata automatically finds all the <strong>journal sources</strong> and presents a powerful dashboard to explore, search, filter and analyze your <strong>logs</strong>. It works on both individual servers and journal centralization servers.</p>Improve Your Security With systemd-journal & Netdatahttps://www.netdata.cloud/blog/improve-your-security-with-systemd-and-netdata/Tue, 24 Oct 2023 00:00:00 +0000https://www.netdata.cloud/blog/improve-your-security-with-systemd-and-netdata/<p><strong><code>systemd</code> journals</strong> play a crucial role in the Linux system ecosystem, and understanding the importance of the logs contained within is essential for both system administrators and developers.</p> <p>For those unfamiliar, <code>systemd</code> is an init system employed by Linux distributions, initiates the user space and oversees all ensuing processes. One of its key components, <code>systemd</code> journal, assumes a central role in logging system activities and messages, delivering a host of benefits to both system administrators, developers and cyber security engineers. The <code>systemd</code> journal functions as a logging system that gathers, archives, and oversees log messages and event data originating from a diverse array of system components, encompassing the kernel, system services, applications, and user activities.</p>Monitoring vs Observability: Key Differenceshttps://www.netdata.cloud/blog/monitoring-vs-observability/Tue, 24 Oct 2023 00:00:00 +0000https://www.netdata.cloud/blog/monitoring-vs-observability/<p>As systems increasingly shift towards distributed architectures to deliver application services, the roles of monitoring and observability have never been more crucial. Monitoring delivers the situational awareness you need to detect issues, while <a href="https://www.netdata.cloud/academy/what-is-observability/">observability goes a step further</a>, offering the analytical depth to understand the root cause of those issues.</p> <p>Understanding the nuanced differences between monitoring and observability is crucial for anyone responsible for system health and performance. In dissecting these methodologies, we&rsquo;ll explore their unique strengths, dive into practical applications, and illuminate how to strategically employ each to enhance operational outcomes.</p>Exploring systemd journal logs with Netdatahttps://www.netdata.cloud/blog/exploring-systemd-journal-logs/Thu, 12 Oct 2023 00:00:00 +0000https://www.netdata.cloud/blog/exploring-systemd-journal-logs/<p>Today, we released our <code>systemd</code> <strong>journal plugin for Netdata</strong>, allowing you to explore, view, search, filter and analyze <code>systemd</code> journal logs.</p> <p>Like most things about Netdata, this is a <strong>zero-configuration plugin</strong>. You don’t have to do anything apart from <strong>installing Netdata</strong> on your systems.This is key design direction for Netdata, since we want Netdata to be able to help even if you install it mid-crisis, while you have an incident at hand.</p>systemd journal logshttps://www.netdata.cloud/blog/systemd-journal-logs/Mon, 09 Oct 2023 00:00:00 +0000https://www.netdata.cloud/blog/systemd-journal-logs/<p><em>“Why bother with it? I let it run in the background and focus on more important DevOps work.”</em> — a random DevOps Engineer at Reddit r/devops</p> <p>In an era where technology is evolving at breakneck speeds, it&rsquo;s easy to overlook the tools that are right under our noses. One such underutilized powerhouse is the <strong><code>systemd</code> journal</strong>. For many, it&rsquo;s a mere tool to check the status of systemd service units or to tail the most recent events (journalctl -f). Others who do mainly container work, ignore even its existence.</p>Netdata Cloud On Premhttps://www.netdata.cloud/blog/netdata-cloud-on-prem/Tue, 26 Sep 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-cloud-on-prem/<p>We at <strong>Netdata</strong> understand that <a href="https://blog.netdata.cloud/future-of-infrastructure-monitoring/">infrastructure monitoring</a> can be a complex maze—high costs, specialized skill sets, scalability, data silos, and more. That&rsquo;s why we have always aimed to streamline and modernize this critical operation. Today, we&rsquo;re thrilled to announce the launch of <a href="https://www.netdata.cloud/contact-us/?subject=on-prem">Netdata Cloud On Prem</a>, a ground-breaking solution designed for robust <strong>on-prem infrastructure monitoring</strong> - it comes with all the <strong>Netdata Cloud</strong> features you love but fully on prem.</p> <h2 id="netdata-cloud-on-prem"><strong>Netdata Cloud On-Prem</strong></h2> <p>While <a href="https://www.netdata.cloud/">Netdata Cloud</a> never stores any of your metric data on the cloud and just streams it ephemerally while you view a chart, the demand for on premise infrastructure monitoring has never been more pressing. Many large enterprises, governmental organizations, research institutes and critical infrastructures require a level of data privacy, security, and customization that only an on-prem solution can offer.</p>Netdata QoS Classes monitoringhttps://www.netdata.cloud/blog/netdata-qos-monitoring/Tue, 26 Sep 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-qos-monitoring/<p>Netdata monitors <code>tc</code> QoS classes for all interfaces.</p> <p>If you also use <a href="http://firehol.org/tutorial/fireqos-new-user/">FireQOS</a> it will collect interface and class names.</p> <p>There is a <a href="https://raw.githubusercontent.com/netdata/netdata/master/src/collectors/tc.plugin/tc-qos-helper.sh.in">shell helper</a> for this (all parsing is done by the plugin in <code>C</code> code - this shell script is just a configuration for the command to run to get <code>tc</code> output).</p> <p>The source of the tc plugin is <a href="https://raw.githubusercontent.com/netdata/netdata/master/src/collectors/tc.plugin/plugin_tc.c">here</a>. It is somewhat complex, because a state machine was needed to keep track of all the <code>tc</code> classes, including the pseudo classes tc dynamically creates.</p>Netdata, Prometheus, Grafana Stackhttps://www.netdata.cloud/blog/netdata-prometheus-grafana-stack/Tue, 26 Sep 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-prometheus-grafana-stack/<p>In this blog, we will walk you through the basics of getting Netdata, Prometheus and Grafana all working together and <a href="https://www.netdata.cloud/blog/web-servers-and-their-performance/">monitoring your application servers</a>. This article will be using docker on your local workstation. We will be working with docker in an ad-hoc way, launching containers that run <code>/bin/bash</code> and attaching a TTY to them. We use docker here in a purely academic fashion and do not condone running Netdata in a container. We pick this method so individuals without <a href="https://www.netdata.cloud/academy/what-is-cloud-management-how-to-maximize-efficiency/">cloud accounts</a> or access to VMs can try this out and for it&rsquo;s speed of deployment.</p>Process Monitoring vs Console Tools: A Comparisonhttps://www.netdata.cloud/blog/netdata-processes-monitoring-comparison-with-console-tools/Tue, 26 Sep 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-processes-monitoring-comparison-with-console-tools/<p>Netdata reads <code>/proc/&lt;pid&gt;/stat</code> for all processes, once per second and extracts <code>utime</code> and <code>stime</code> (user and system cpu utilization), much like all the console tools do.</p> <p>But it also extracts <code>cutime</code> and <code>cstime</code> that account the user and system time of the exit children of each process. By keeping a map in memory of the whole process tree, it is capable of assigning the right time to every process, taking into account all its exited children.</p>Our first ML based anomaly alerthttps://www.netdata.cloud/blog/our-first-ml-based-anomaly-alert/Wed, 13 Sep 2023 00:00:00 +0000https://www.netdata.cloud/blog/our-first-ml-based-anomaly-alert/<p>Over the last few years we have slowly and methodically been building out the <a href="https://learn.netdata.cloud/docs/ml-and-troubleshooting/">ML based capabilities</a> of the Netdata agent, dogfooding and iterating as we go. To date, these features have mostly been somewhat reactive and tools to aid once you are already troubleshooting.</p> <p>Now we feel we are ready to take a first gentle step into some more proactive use cases, starting with a <a href="https://github.com/netdata/netdata/pull/14687">simple node level anomaly rate alert</a>.</p>Anomaly Rate By Typehttps://www.netdata.cloud/blog/anomaly-rate-by-type/Wed, 30 Aug 2023 00:00:00 +0000https://www.netdata.cloud/blog/anomaly-rate-by-type/<p>We have <a href="https://github.com/netdata/netdata/pull/15856">recently added</a> a more detailed anomaly rate chart to Netdata that breaks out the overall <a href="https://learn.netdata.cloud/docs/netdata-ai/anomaly-detection#node-level-anomaly-detection">node anomaly rate</a> by type, this lets you more easily see what parts of your infrastructure might be experiencing an uptick in anomalies when you see the overall node anomaly rate increase.</p> <h2 id="what-is-type">What is <code>type</code>?</h2> <p><code>type</code> is generally the prefix of the chart id in Netdata and controls where charts live within the menu on the overview page, for example the <code>mem.available</code> chart has a type of <code>mem</code> which in part controls why it lives under the &ldquo;Memory&rdquo; section of the menu.</p>Release 1.41: Brand-New UI For Agents & Parentshttps://www.netdata.cloud/blog/netdata-version-1.41/Thu, 20 Jul 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-version-1.41/<p>Netdata Agents and Parents now have a new UI!</p> <p>Checkout the release meetup video or read on to learn more about the new UI and other features in this release.</p> <div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;"> <iframe allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share; fullscreen" loading="eager" referrerpolicy="strict-origin-when-cross-origin" src="https://www.youtube.com/embed/WCUn4-LneCw?autoplay=0&amp;controls=1&amp;end=0&amp;loop=0&amp;mute=0&amp;start=0" style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;" title="YouTube video"></iframe> </div> <ul> <li><a href="#v1410-netdata-open-source-growth">Netdata Growth </a></li> <li><a href="#v1410-release-highlights">Release Highlights</a> <ul> <li><strong><a href="#v1410-one-dashboard">New Agent Dashboard!</a></strong></li> <li><a href="#v1410-netdata-assistant">Netdata Assistant</a></li> <li><a href="#v1410-netdata-freeipmi">New FreeIPMI collector for monitoring enterprise hardware</a></li> <li><a href="#v1410-netdata-apps">Netdata Detects FDs Leaking</a></li> </ul> </li> <li><a href="#v1410-acknowledgements">Acknowledgements </a></li> <li><a href="#v1410-contributions">Contributions</a></li> <li><a href="#v1410-contributions-collectors">Collectors</a></li> <li><a href="#v1410-contributions-documentation">Documentation </a></li> <li><a href="#v1410-contributions-packaging">Packaging/Installation</a></li> <li><a href="#v1410-contributions-health">Health</a></li> <li><a href="#v1410-contributions-exporting">Exporting</a></li> <li><a href="#v1410-contributions-other">Other Notable Changes</a></li> <li><a href="#v1410-deprecation-notice">Deprecation notice</a> <ul> <li><a href="#v1410-deprected-in-this-release">Deprecated in this release</a></li> </ul> </li> <li><a href="#v1410-netdata-release-meetup">Netdata Release Meetup</a></li> <li><a href="#v1410-support-options">Support options</a></li> </ul> <p>Steady to our schedule, this is another great Netdata release!</p>Netdata Assistant: Your AI-Powered Troubleshooting Sidekickhttps://www.netdata.cloud/blog/netdata-assistant/Fri, 14 Jul 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-assistant/<p>Hey there! We&rsquo;re excited to share a new troubleshooting feature we have added to Netdata, the Netdata Assistant. We&rsquo;ve built this tool to help you troubleshoot more effectively and with less stress. Let&rsquo;s dive in.</p> <!--truncate--> <h2 id="whats-the-netdata-assistant">What&rsquo;s the Netdata Assistant?</h2> <p>The Netdata Assistant is an AI tool that uses large language models and our community&rsquo;s knowledge to guide you during troubleshooting.</p> <p>Here&rsquo;s a scenario. It&rsquo;s 3 am and you get an alert. Instead of scrambling to Google what&rsquo;s going on, you can just click on the assistant button. The Netdata Assistant will give you the lowdown on the alert, why it&rsquo;s happening, and why you should care. It&rsquo;ll also guide you on how to troubleshoot it and even offer some handy web links for more info, if you&rsquo;re interested.</p>Hidden Costs Of Monitoring: Uncovering Expenses & Solutionshttps://www.netdata.cloud/blog/hidden-costs-of-monitoring/Fri, 07 Jul 2023 00:00:00 +0000https://www.netdata.cloud/blog/hidden-costs-of-monitoring/<p>When it comes to monitoring IT infrastructure, the <a href="https://www.netdata.cloud/pricing/">costs you see on the price tag</a> of the tool are often just the tip of the iceberg. Below the waterline, a mass of hidden costs can lurk, which can significantly affect the total cost of ownership.</p> <!--truncate--> <p>In this blogpost we will cover the analysis of two traditional monitoring domains, <a href="https://www.netdata.cloud/open-source/">Open Source observability</a> and Commercial Centralized observability solutions, focusing the direct and indirect impacts when implementing these solution. In summary:</p>Netdata & Ansible example: ML demo roomhttps://www.netdata.cloud/blog/ml-demo-ansible-configuration-management/Fri, 07 Jul 2023 00:00:00 +0000https://www.netdata.cloud/blog/ml-demo-ansible-configuration-management/<p>We are always trying to lower the barrier to entry when it comes to monitoring and observability and one place we have consistently witnessed some pain from users is around adopting and approaching <a href="https://www.atlassian.com/microservices/microservices-architecture/configuration-management">configuration management</a> tools and practices as your infrastructure grows and becomes more complex.</p> <p>To that end, we have begun recently publishing our own <a href="https://github.com/netdata/community/tree/main/configuration-management/ansible-ml-demo">little example ansible project</a> used to maintain and manage the servers used in our public <a href="https://app.netdata.cloud/spaces/netdata-demo/rooms/machine-learning/overview">Machine Learning Demo room</a>.</p>Netdata Parents (Streaming and Replication)https://www.netdata.cloud/blog/netdata-parents-streaming-replication/Fri, 30 Jun 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-parents-streaming-replication/<h2 id="what-are-they-and-why-do-we-need-them">What are they and why do we need them?</h2> <p>A “Parent” is a Netdata Agent, like the ones we install on all our systems, but is configured as a central node that receives, stores and processes metrics data from other Netdata “Child” nodes in our infrastructure.</p> <p>Netdata Parents are flexible. You can have one big active-active cluster of Netdata Parents, or you can spread a lot of independent Parents across the infrastructure.</p>Release 1.40: Summary Tiles, Silencing & ML Tweakshttps://www.netdata.cloud/blog/netdata-version-1.40/Wed, 14 Jun 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-version-1.40/<p>Another release of the Netdata Monitoring solution is here!</p> <div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;"> <iframe allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share; fullscreen" loading="eager" referrerpolicy="strict-origin-when-cross-origin" src="https://www.youtube.com/embed/2VkWIZB8S30?autoplay=0&amp;controls=1&amp;end=0&amp;loop=0&amp;mute=0&amp;start=0" style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;" title="YouTube video"></iframe> </div> <!--truncate--> <ul> <li><a href="#v1400-netdata-open-source-growth">Netdata Growth</a></li> <li><a href="#v1400-release-highlights">Release Highlights</a> <ul> <li><strong><a href="#v1400-visualization-summary-dashboards">Dashboard Sections&rsquo; Summary Tiles</a></strong><br/> Added summary tiles to most sections of the fully-automated dashboards, to provide an instant view of the most important metrics for each section.</li> <li><strong><a href="#v1400-alert-notification-silencing">Silencing of Cloud Alert Notifications</a></strong><br/> Maintenance window coming up? Active issue being checked? Use the Alert notification silencing engine to mute your notifications.</li> <li><strong><a href="#v1400-ml-extended-training">Machine Learning - Extended Training to 24 Hours</a></strong><br/> Netdata now trains multiple models per metric, to learn the behavior of each metric for the last 24 hours. Trained models are persisted on disk and are loaded back on Netdata restart.</li> <li><strong><a href="#v1400-streaming">Rewritten SSL Support for the Agent</a></strong><br/> Netdata Agent now features a new SSL layer that allows it to reliably use SSL on all its features, including the API and Streaming.</li> </ul> </li> <li><a href="#v1400-alerts">Alerts and Notifications</a></li> <li><a href="#v1400-visualizations">Visualizations / Charts and Dashboards</a></li> <li><a href="#v1400-packaging-split">Preliminary steps to split native packages</a></li> <li><a href="#v1400-acknowledgements">Acknowledgements</a></li> <li><a href="#v1400-contributions">Contributions</a> <ul> <li><a href="#v1400-contributions-collectors">Collectors</a></li> <li><a href="#v1400-contributions-documentation">Documentation</a></li> <li><a href="#v1400-contributions-packaging">Packaging / Installation</a></li> <li><a href="#v1400-contributions-streaming">Streaming</a></li> <li><a href="#v1400-contributions-health">Health</a></li> <li><a href="#v1400-contributions-exporting">Exporting</a></li> <li><a href="#v1400-contributions-ml">ML</a></li> <li><a href="#v1400-contributions-other">Other notable changes</a></li> </ul> </li> <li><a href="#v1400-deprecation-notice">Deprecation notice</a></li> <li><a href="#v1400-cloud-recommended-version">Cloud recommended version</a></li> <li><a href="#v1400-release-meetup">Release meetup</a></li> <li><a href="#v1400-support-options">Support options</a></li> <li><a href="#v1400-running-survey">Running survey</a></li> </ul> <h2 id="netdata-growth">Netdata Growth <a id="v1400-netdata-open-source-growth"></a></h2> <p>🚀 Our community growth is increasing steadily. ❤️ Thank you! Your love and acceptance give us the energy and passion to work harder to simplify and make monitoring easier, more effective and more fun to use.</p>How Netdata's ML-based Anomaly Detection Workshttps://www.netdata.cloud/blog/how-netdatas-ml-based-anomaly-detection-works/Tue, 23 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/how-netdatas-ml-based-anomaly-detection-works/<p><img src="../2023-05-23-how-netdatas-ml-based-anomaly-detection-works/img/img.png" alt="title image"></p> <p>How does Netdata&rsquo;s <a href="https://learn.netdata.cloud/docs/netdata-ai/anomaly-detection">machine learning (ML) based anomaly detection</a> actually work? Read on to find out!</p> <!--truncate--> <h2 id="design-considerations">Design considerations</h2> <p>Lets first start with some of the key design considerations and principles of Netdata&rsquo;s anomaly detection (<em>and some comments in parenthesis along the way</em>):</p> <ol> <li>We don&rsquo;t have any labels or examples of previous anomalies. This means we are in an <a href="https://en.wikipedia.org/wiki/Unsupervised_learning">unsupervised setting</a> (<em>best we can try to do is learn what &ldquo;normal&rdquo; data looks like assuming the collected data is &ldquo;mostly&rdquo; normal</em>).</li> <li>Needs to be lightweight and run on the agent (<em>or a parent</em>). <ul> <li>Need to be very careful of impact on CPU overhead when training and scoring (<em>lots of cheap models are better than a few expensive and heavy ones</em>).</li> <li>Models themselves need to be small so as to not drastically increase the agents memory footprint (<em>model objects need to be small for storage</em>).</li> <li>This has implications for the ML formulation (<em>sorry - no deep learning models yet) and its implementation (we need to be surgical and optimized</em>).</li> </ul> </li> <li>Needs to scale for thousands of metrics and score in realtime every second as metrics are collected. <ul> <li>Typical Netdata nodes have thousands of metrics and we want to be able to score every metric every second with minimal latency overhead (<em>we need to use sensible approaches to training like spreading the training cost over a wide training window</em>).</li> </ul> </li> <li>Needs to be able to handle a wide variety of metrics. <ul> <li>There is no single perfect model or approach for all types of metrics so we need a good all rounder that can work well enough across any and all different types of time seres metrics (<em>for any given metric of course you could handcraft a better model but thats not feasible here, we need something like a &ldquo;weak learners&rdquo; approach of lots of generally useful models adding up to &ldquo;more than the sum of their parts&rdquo;</em>).</li> </ul> </li> <li>Needs to be written in C or C++ as that is the language of the Netdata agent (<em>We are using <a href="https://github.com/davisking/dlib">dlib</a> for the current implementation</em>).</li> <li>We Need to be very careful about taking big or complex dependencies if using third party libraries. <ul> <li>We want to be able to easily build and deploy Netdata on any Linux system without having to worry about installing or managing complex dependencies (<em>we need to be careful of more complex algorithms that would have larger dependencies and potentially limit where Netdata can run</em>).</li> </ul> </li> </ol> <p>The above considerations are important and useful to keep in mind as we explore the system in more detail.</p>Revolutionizing Ops Centers With Real-Time Monitoringhttps://www.netdata.cloud/blog/revolutionizing-operations-centers-real-time-monitoring-solution/Fri, 19 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/revolutionizing-operations-centers-real-time-monitoring-solution/<p><img src="../2023-05-19-revolutionizing-operations-centers-real-time-monitoring-solution/img/stacked-netdata.png" alt="stacked-netdata"></p> <p>In today&rsquo;s fast-paced digital landscape, 24-hour operations centers play a crucial role in managing and monitoring large-scale infrastructures. These centers must be equipped with an effective monitoring solution that addresses their unique needs, enabling them to respond quickly to incidents and maintain optimal system performance. Netdata, a comprehensive monitoring solution, has been designed to meet these critical requirements with its advanced capabilities and recent enhancements.</p> <p>In this article, we will explore how Netdata&rsquo;s powerful features can transform the way 24-hour operations centers monitor and manage their complex environments, leading to improved incident detection, faster troubleshooting, and better overall system performance.</p>The Future Of Infrastructure Monitoring: Scalability & AIhttps://www.netdata.cloud/blog/future-of-infrastructure-monitoring/Fri, 19 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/future-of-infrastructure-monitoring/<p>In this blog post, we will explore the importance of scalability, automation, and AI in the evolving landscape of <a href="https://www.netdata.cloud/academy/what-is-infrastructure-monitoring-and-why-you-need-it/">infrastructure monitoring</a>. We will examine how Netdata&rsquo;s innovative solution aligns with these emerging trends, and how it can empower organizations to effectively manage their modern IT infrastructure.</p> <!--truncate--> <p>In today&rsquo;s increasingly complex IT landscape, the need for efficient and reliable infrastructure monitoring has never been more critical. With the <a href="https://medium.com/capital-one-tech/the-microservices-paradox-e55d5af2fda5">proliferation of microservices</a>, distributed systems, and cloud-native applications, managing and monitoring the performance of these rapidly evolving environments has become a significant challenge. As a result, infrastructure monitoring solutions must adapt to keep pace with these changes and deliver the insights necessary to maintain optimal performance.</p>Monitoring Multi-Cloud & Hybrid-Cloud Infrastructureshttps://www.netdata.cloud/blog/monitoring-multi-cloud-hybrid-cloud/Tue, 16 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/monitoring-multi-cloud-hybrid-cloud/<p>The advent of multi-cloud and hybrid-cloud architectures has created new opportunities for organizations to leverage best-in-class features from various cloud service providers. However, these complex environments present their own unique challenges, especially when it comes to monitoring and managing performance.</p> <!--truncate--> <h2 id="visibility">Visibility</h2> <p>The visibility challenge in multi-cloud and hybrid-cloud environments often stems from the use of disparate monitoring tools that are native to each cloud provider. While these native tools (like Amazon CloudWatch, Google Cloud Monitoring, and Azure Monitor) are excellent within their respective ecosystems, they don&rsquo;t necessarily play well together when it comes to consolidating data and providing a comprehensive, unified view of your entire infrastructure.</p>Cloud Optimization: Cost, Performance & Resource Strategieshttps://www.netdata.cloud/blog/mastering-cloud-optimization/Sun, 14 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/mastering-cloud-optimization/<p>Cloud optimization is the ongoing process of analyzing, configuring, and refining cloud environments to improve performance, reduce costs, and align resource usage with business needs. As cloud adoption grows, organizations must move beyond cost-cutting alone and treat optimization as a strategic practice.</p> <h2 id="cloud-optimization-strategies-to-achieve-business-goals">Cloud Optimization Strategies To Achieve Business Goals</h2> <p>Cloud optimization strategies generally focus on cost control, performance enhancement, and efficient resource utilization. These strategies range from selecting the right cloud service model (IaaS, PaaS, or SaaS), right-sizing your resources, adopting a <a href="https://www.netdata.cloud/academy/what-is-cloud-management-how-to-maximize-efficiency/">multi-cloud approach</a>, automating processes, and investing in robust monitoring tools that can reliably reveal resources utilization and help you ensure that services are tailored to meet business objectives.</p>Migrating To Cloud: Key Challenges & Best Practiceshttps://www.netdata.cloud/blog/migrating-to-cloud-key-challenges-best-practices/Sun, 14 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/migrating-to-cloud-key-challenges-best-practices/<p>Embarking on a cloud migration journey? Grasp the obstacles and arm yourself with best practices for a smooth transition. Success lies in understanding, planning, and adapting.</p> <!--truncate--> <p>As we continue to advance further into the 21st century, businesses of all sizes are finding themselves in the midst of a digital revolution. At the heart of this transformation lies cloud migration, a process that has become a critical strategic decision for organizations aiming to remain competitive, innovative, and responsive to fluctuating market dynamics.</p>Transform Monitoring With A Machine Learning Approachhttps://www.netdata.cloud/blog/transform-monitoring-ml-first-approach/Thu, 11 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/transform-monitoring-ml-first-approach/<p>Unlocking the full potential of monitoring through ML integration, anomaly detection, and innovative scoring engines.</p> <!--truncate--> <p>Machine Learning has been making waves in various industries, but its adoption in the monitoring and observability space has been slower than expected. Many “ML” features remain gimmicky and do not provide actual real world value to users that encourages their further use.</p> <p>At Netdata, we firmly believe that ML is crucial for monitoring, and we&rsquo;ve taken an ML-first approach to provide users with powerful tools and insights. In this blog post, we&rsquo;ll discuss the reasons behind our belief in ML, how we&rsquo;ve integrated ML into our charts and visualizations, our query engines, the scoring engine we&rsquo;ve built, and how these innovations enable metrics correlations and anomaly advisor.</p>The Future of Monitoring is Automated and Opinionatedhttps://www.netdata.cloud/blog/the-future-of-monitoring-is-automated-and-opinionated/Tue, 09 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/the-future-of-monitoring-is-automated-and-opinionated/<p>So, you think you monitor your infra?</p> <!-- truncate --> <p>As humanity increasingly relies on technology, <a href="https://www.netdata.cloud/blog/future-of-infrastructure-monitoring/">the need for reliable and efficient infrastructure monitoring solutions has never been greater</a>.</p> <p>However, most businesses don&rsquo;t take this seriously. They make poor choices that soon trap their best talent, the people who should be propelling them ahead of their competition.</p> <p>Consider this: most of the world believes that each company needs to dedicate time, talent, and money to configure and set up the monitoring of their web servers and database servers from scratch!</p>Release 1.39.0: A new era for monitoring charts.https://www.netdata.cloud/blog/netdata-version-1.39/Mon, 08 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-version-1.39/<p>Another release of the Netdata Monitoring solution is here!</p> <div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;"> <iframe allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share; fullscreen" loading="eager" referrerpolicy="strict-origin-when-cross-origin" src="https://www.youtube.com/embed/dU4GJjpeb3I?autoplay=0&amp;controls=1&amp;end=0&amp;loop=0&amp;mute=0&amp;start=0" style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;" title="YouTube video"></iframe> </div> <ul> <li><a href="#netdata-open-source-growth">Netdata open-source growth</a></li> <li><a href="#release-highlights">Release highlights</a> <ul> <li><strong><a href="#netdata-charts-v30">Netdata Charts v3.0</a></strong> A new era for monitoring charts. Powerful, fast, easy to use. Instantly understand the dataset behind any chart. Slice, dice, filter and pivot the data in any way possible!</li> <li><strong><a href="#windows-support">Windows support</a></strong> Windows hosts are now first-class citizens. You can now enjoy out-of-the-box monitoring of over 200 metrics from your Windows systems and the services that run on them.</li> <li><a href="#virtual-nodes-and-custom-labels">Virtual nodes and custom labels</a> You now have access to more monitoring superpowers for managing medium to large infrastructures. With custom labels and virtual hosts, you can easily organize your infrastructure and ensure that troubleshooting is more efficient.</li> <li><a href="#major-upcoming-changes">Major upcoming changes</a> Separate packages for data collection plugins, mandatory <code>zlib</code>, no upgrades of existing installs from versions prior to v1.11.</li> <li><a href="#bar-charts-for-functions">Bar charts for functions</a></li> <li><a href="#opsgenie-notifications-for-business-plan-users">Opsgenie notifications for Business Plan users</a> Business plan users can now seamlessly integrate Netdata with their Atlassian Opsgenie alerting and on call management system.</li> </ul> </li> <li><a href="#data-collection">Data Collection</a> <ul> <li><a href="#containers-and-vms-cgroups">Containers and VMs CGROUPS</a></li> <li><a href="#docker">Docker</a></li> <li><a href="#kubernetes">Kubernetes</a></li> <li><a href="#kernel-tracesmetrics-ebpf">Kernel traces/metrics eBPF</a></li> <li><a href="#disk-space-monitoring">Disk Space Monitoring</a></li> <li><a href="#os-provided-metrics-procplugin">OS Provided Metrics proc.plugin</a></li> <li><a href="#postgresql">PostgreSQL</a></li> <li><a href="#dns-query">DNS Query</a></li> <li><a href="#http-endpoint-check">HTTP endpoint check</a></li> <li><a href="#elasticsearch-and-opensearch">Elasticsearch and OpenSearch</a></li> <li><a href="#dnsmasq-dns-forwarder">Dnsmasq DNS Forwarder</a></li> <li><a href="#envoy">Envoy</a></li> <li><a href="#files-and-directories">Files and directories</a></li> <li><a href="#rabbitmq">RabbitMQ</a></li> <li><a href="#chartsdplugin">charts.d.plugin</a></li> <li><a href="#anomalies">Anomalies</a></li> <li><a href="#generic-structured-data-pandas">Generic structured data with Pandas</a></li> <li><a href="#generic-prometheus-collector">Generic Prometheus collector</a></li> </ul> </li> <li><a href="#alerts-and-notifications">Alerts and Notifications</a> <ul> <li><a href="#notifications">Notifications</a> <ul> <li><a href="#improved-email-alert-notifications">Improved email alert notifications</a></li> <li><a href="#receive-only-notifications-for-unreachable-nodes">Receive only notifications for unreachable nodes</a></li> <li><a href="#ntfy-agent-alert-notifications">ntfy agent alert notifications</a></li> </ul> </li> <li><a href="#enhanced-real-time-alert-synchronization-on-netdata-cloud">Enhanced Real-Time Alert Synchronization on Netdata Cloud</a></li> </ul> </li> <li><a href="#visualizations--charts-and-dashboards">Visualizations / Charts and Dashboards</a> <ul> <li><a href="#events-feed">Events Feed</a></li> </ul> </li> <li><a href="#machine-learning">Machine Learning</a></li> <li><a href="#installation-and-packaging">Installation and Packaging</a> <ul> <li><a href="#improved-linux-compatibility">Improved Linux compatibility</a></li> </ul> </li> <li><a href="#administration">Administration</a> <ul> <li><a href="#new-way-to-retrieve-netdataconf">New way to retrieve netdata.conf</a></li> </ul> </li> <li><a href="#documentation-and-demos">Documentation and Demos</a></li> <li><a href="#deprecation-notice">Deprecation notice</a> <ul> <li><a href="#deprecated-in-this-release">Deprecated in this release</a></li> </ul> </li> <li><a href="#netdata-release-meetup">Netdata Agent Release Meetup</a></li> <li><a href="#support-options">Support options</a></li> <li><a href="#running-survey">Running survey</a></li> <li><a href="#acknowledgements">Acknowledgements</a></li> </ul> <h2 id="netdata-open-source-growth">Netdata open-source growth</h2> <!-- Retrieve most of these stats from netdata/netdata/README.md badges --> <ul> <li>Over 62,000 GitHub Stars</li> <li>Over 1.5 million online nodes</li> <li>Almost 92 million sessions served</li> <li>Over 600 thousand total nodes in Netdata Cloud</li> </ul> <h2 id="release-highlights">Release highlights</h2> <h3 id="netdata-charts-v30">Netdata Charts v3.0</h3> <p>We are excited to announce Netdata Charts v3.0 and the NIDL framework. These are currently available at Netdata Cloud. At the next Netdata release, the agent dashboard will be replaced to also use the same charts.</p>Infinite Scalability: Monitoring Without Limitshttps://www.netdata.cloud/blog/netdata-inifinite-scalability/Thu, 04 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-inifinite-scalability/<p>Scalability is crucial for monitoring systems as it ensures that they can accommodate growth, maintain performance, provide flexibility, optimize costs, enhance fault tolerance, and support informed decision-making, all of which are critical for effective infrastructure management.</p> <!--truncate--> <p>Most monitoring solutions struggle with scalability, mainly because of:</p> <ol> <li><strong>High data volume and velocity</strong>: Monitoring systems generate vast amounts of data and as the infrastructure grows, so does the volume and velocity of these data.</li> <li><strong>Resource constraints</strong>: Scalability requires efficient resource utilization, leading to bottlenecks and performance issues as the monitored environment grows.</li> <li><strong>Architectural limitations</strong>: Monitoring systems are usually designed with certain architectural constraints that limit their scalability. Most open source solutions rely on monolithic or centralized architectures that can become overwhelmed at scale.</li> </ol> <p>For open source solutions scalability has always been a challenge, increasing their complexity significantly (check for example the scalability issues of Prometheus), while for commercial solutions it usually results in increased data collection to visualization latency and cost.</p>Monitoring Disks: Workload, Latency & Saturationhttps://www.netdata.cloud/blog/monitoring-disks-understanding-workload-performance-utilisation-saturation-latency/Thu, 04 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/monitoring-disks-understanding-workload-performance-utilisation-saturation-latency/<p><img src="../2023-05-04-monitoring-disks-understanding-workload-performance-utilisation-saturation-latency/img/stacked-netdata.png" alt="stacked-netdata"></p> <p>Netdata provides a comprehensive set of charts that can help you understand the workload, performance, utilization, saturation, latency, responsiveness, and maintenance activities of your disks. In this blog we will focus on monitoring disks as block devices, not as filesystems or mount points.</p> <!-- truncate --> <p>The <code>Disks</code> section in the <code>Overview</code> tab contains all the charts that are mentioned in this blog post. <img src="../2023-05-04-monitoring-disks-understanding-workload-performance-utilisation-saturation-latency/img/disks-overview.png" alt="Disks-Overview"></p> <h2 id="disk-workload-and-performance">Disk Workload and Performance</h2> <p>Netdata charts for monitoring the workload and the throughput of your disks:</p>Understanding Huge Pageshttps://www.netdata.cloud/blog/understanding-huge-pages/Thu, 04 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/understanding-huge-pages/<p>Memory-intensive applications can benefit from <a href="https://www.netdata.cloud/academy/what-is-application-performance-monitoring-apm/">improved performance</a> by using huge pages, as they can reduce TLB pressure and memory fragmentation, and lower the memory management overhead overall. Developers should consider using HugeTLBfs in their mmap() and shmget() calls to take advantage of huge pages.</p> <p>Transparent Huge Pages (THP) is a Linux kernel feature that provides some of the benefits of huge pages without requiring any development effort. However, THP can cause latency in many applications. Although kernel developers are actively working to address these issues, many system administrators prefer to disable THP altogether.</p>Unlock the Secrets of Kernel Memory Usagehttps://www.netdata.cloud/blog/unlock-the-secrets-of-kernel-memory-usage/Thu, 04 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/unlock-the-secrets-of-kernel-memory-usage/<p><img src="../2023-05-04-unlock-the-secrets-of-kernel-memory-usage/img/stacked-netdata.png" alt="stacked-netdata"></p> <p>The <code>mem.kernel</code> chart in Netdata provides insight into the memory usage of <a href="https://www.netdata.cloud/academy/what-are-the-differences-between-bpf-and-ebpf-an-overview/">various kernel subsystems</a> and mechanisms. By understanding these dimensions and their technical details, you can monitor your system&rsquo;s kernel memory usage and identify potential issues or inefficiencies. Monitoring these dimensions can help you ensure that your system is running efficiently and provide valuable insights into the performance of your kernel and memory subsystem.</p> <p><img src="../2023-05-04-unlock-the-secrets-of-kernel-memory-usage/img/mem-kernel.png" alt="mem-kernel"></p> <!-- truncate --> <h2 id="slab">Slab</h2> <p>The <a href="https://en.wikipedia.org/wiki/Slab_allocation">slab allocator</a> is a memory management mechanism introduced by Jeff Bonwick in 1994 to manage <a href="https://www.netdata.cloud/monitoring-101/vsphere-monitoring/">memory allocation</a> for kernel objects. The main purpose of the slab allocator is to reduce memory fragmentation and improve the speed of memory allocation/deallocation. The slab allocator groups objects of the same size into &ldquo;slabs&rdquo; and caches the objects to speed up future allocations.</p>Entropy In Cryptography: Key To Security & Randomnesshttps://www.netdata.cloud/blog/understanding-entropy-the-key-to-secure-cryptography-and-randomness/Wed, 03 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/understanding-entropy-the-key-to-secure-cryptography-and-randomness/<p><img src="../2023-05-03-understanding-entropy-the-key-to-secure-cryptography-and-randomness/img/stacked-netdata.png" alt="stacked-netdata"></p> <p><a href="https://en.wikipedia.org/wiki/Entropy_(computing)">Entropy</a> is a measure of the randomness or unpredictability of data. In the context of cryptography, entropy is used to generate random numbers or keys that are essential for secure communication and encryption. Without a good source of entropy, cryptographic protocols can become vulnerable to attacks that exploit the predictability of the generated keys.</p> <!-- truncate --> <h2 id="what-is-entropy">What is Entropy?</h2> <p>In most operating systems, entropy is generated by collecting random events from various sources, such as hardware interrupts, mouse movements, keyboard presses, and disk activity. These events are fed into a pool of entropy, which is then used to generate random numbers when needed.</p>Context Switching & Its Impact On System Performancehttps://www.netdata.cloud/blog/understanding-context-switching-and-its-impact-on-system-performance/Tue, 02 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/understanding-context-switching-and-its-impact-on-system-performance/<p><img src="../2023-05-02-understanding-context-switching-and-its-impact-on-system-performance/img/stacked-netdata.png" alt="stacked-netdata"></p> <p>Context switching is the process of switching the CPU from one process, task or thread to another. In a multitasking operating system, such as Linux, the CPU has to switch between multiple processes or threads in order to keep the system running smoothly. This is necessary because each CPU core without hyperthreading can only execute one process or thread at a time. If there are many processes or threads running simultaneously, and very few CPU cores available to handle them, the system is forced to make more context switches to balance the CPU resources among them.</p>Linux CPU Consumption, Load & Pressure Explainedhttps://www.netdata.cloud/blog/understanding-linux-cpu-consumption-load-and-pressure-for-performance-optimisation/Tue, 02 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/understanding-linux-cpu-consumption-load-and-pressure-for-performance-optimisation/<p><img src="../2023-05-02-understanding-linux-cpu-consumption-load-and-pressure-for-performance-optimisation/img/stacked-netdata.png" alt="stacked-netdata"></p> <p>As a system administrator, understanding how your Linux system&rsquo;s CPU is being utilized is crucial for identifying bottlenecks and <a href="https://www.netdata.cloud/academy/what-is-cardinality-in-databases-a-comprehensive-guide/">optimizing performance</a>. In this blog post, we&rsquo;ll dive deep into the world of Linux CPU consumption, load, and pressure, and discuss how to use these metrics effectively to identify issues and improve your system&rsquo;s performance.</p> <!-- truncate --> <h2 id="cpu-consumption-and-utilization">CPU Consumption and Utilization</h2> <p>CPU consumption refers to the amount of processing power being used by applications running on your system. The <code>system.cpu</code> chart in Netdata represents the Total CPU utilization of your Linux system, broken down into different dimensions. Each dimension provides insight into how the CPU is being used by various tasks and processes. Here&rsquo;s a brief explanation of each dimension:</p>Server Uptime Monitoring: Core Benefits For High Performancehttps://www.netdata.cloud/blog/server-uptime-monitoring-why-do-we-need-it/Tue, 02 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/server-uptime-monitoring-why-do-we-need-it/<p><img src="../2023-05-02-server-uptime-monitoring-why-do-we-need-it/img/stacked-netdata.png" alt="Server Uptime Monitoring: Core Benefits For High Performance"></p> <p>Server uptime monitoring tracks the availability and reliability of servers within your infrastructure.</p> <!-- truncate --> <h2 id="what-is-server-uptime-monitoring">What Is Server Uptime Monitoring?</h2> <p>Server uptime monitoring is the process of continuously tracking the operational status of your servers to ensure optimal performance and availability for users.</p> <p>With Netdata, you gain access to real-time, high-resolution monitoring that goes beyond basic checks, providing a detailed overview of your entire infrastructure.</p>Swap Memory: When & How To Use It On Production VMshttps://www.netdata.cloud/blog/swap-memory-when-and-how-to-use-it-on-your-production-systems-or-cloud-provided-vms/Tue, 02 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/swap-memory-when-and-how-to-use-it-on-your-production-systems-or-cloud-provided-vms/<p><img src="../2023-05-02-swap-memory-when-to-use-in-production-systems/img/stacked-netdata.png" alt="Swap Memory: Its Use On Production Systems &amp; Cloud-Provided VMs"></p> <p>Swap memory, also known as virtual memory, is a space on a hard disk that is used to supplement the physical memory (RAM) of a computer. The swap space is used when the system runs out of physical memory, and it moves less frequently accessed data from RAM to the hard disk, freeing up space in RAM for more frequently accessed data. But should swap memory be enabled on production systems and <a href="https://www.netdata.cloud/monitoring-101/vsphere-monitoring/">cloud-provided virtual machines</a> (VMs)? Let&rsquo;s explore the pros and cons.</p>Understanding Interrupts, Softirqs, and Softnet in Linuxhttps://www.netdata.cloud/blog/understanding-interrupts-softirqs-and-softnet-in-linux/Tue, 02 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/understanding-interrupts-softirqs-and-softnet-in-linux/<p><img src="../2023-05-02-understanding-interrupts-softirqs-and-softnet-in-linux/img/stacked-netdata.png" alt="stacked-netdata"></p> <p>Interrupts, softirqs, and softnet are all critical parts of the Linux kernel that can impact system performance. In this blog post, we&rsquo;ll explore their usefulness, and discuss how to monitor them using Netdata for both bare-metal servers and VMs.</p> <!-- truncate --> <h2 id="what-are-interrupts">What are Interrupts?</h2> <p>Interrupts are signals generated by hardware devices to indicate that they require attention from the CPU. Hardware devices can generate interrupts for a variety of reasons, including data transmission or reception, input/output operations, and other activities. When an interrupt is generated, the CPU stops what it is doing and handles the interrupt. Interrupts can have a significant impact on system performance, especially if there are a high number of interrupts occurring.</p>Understanding System Processes Stateshttps://www.netdata.cloud/blog/understanding-system-processes-states/Tue, 02 May 2023 00:00:00 +0000https://www.netdata.cloud/blog/understanding-system-processes-states/<p><img src="../2023-05-02-understanding-system-processes-states/img/stacked-netdata.png" alt="stacked-netdata"></p> <p>The different states of system processes are essential to understanding how a computer system works. Each state represents a specific point in a process&rsquo;s life cycle and can impact system performance and stability.</p> <!-- truncate --> <h2 id="process-states">Process States</h2> <p>Netdata&rsquo;s <code>system.processes_state</code> chart provides a view of these states, allowing users to monitor system performance in real-time:</p> <p><img src="../2023-05-02-understanding-system-processes-states/img/system-processes.png" alt="system-processes"></p> <ol> <li> <p><strong>Running:</strong> A process is in the Running state when it is actively using the CPU and executing instructions. This state is resource-intensive and can lead to performance issues if there are too many Running processes, causing CPU contention and system slowdowns. Processes in the Running state are prioritized using scheduling algorithms to improve system performance.</p>Why Scalable Monitoring Matters For Modern Systemshttps://www.netdata.cloud/blog/why-scalable-monitoring-is-essential-for-modern-distributed-systems/Wed, 26 Apr 2023 00:00:00 +0000https://www.netdata.cloud/blog/why-scalable-monitoring-is-essential-for-modern-distributed-systems/<p><img src="../2023-04-26-why-scalable-monitoring-is-essential/img/stacked-netdata.png" alt="stacked-netdata"></p> <p>It&rsquo;s becoming increasingly common to discuss the importance of scalability in monitoring solutions and how it can impact the performance and reliability of distributed systems.</p> <!-- truncate --> <p>In today&rsquo;s rapidly evolving technological landscape, organizations are increasingly relying on distributed systems to power their operations. These systems consist of multiple interconnected components that work together to deliver a cohesive experience. They can span across different geographic locations, and often involve a combination of <a href="https://www.netdata.cloud/product/cloud-on-premises/">on-premises, cloud</a>, and <a href="https://www.netdata.cloud/solutions/technologies/docker-monitoring/">container-based environments</a>. As such, effectively managing these complex systems is critical to ensuring optimal performance, reliability, and security.</p>Netdata's AI Insights & Rapid Diagnosticshttps://www.netdata.cloud/blog/netdata-ai-insights-rapid-diagnostics/Wed, 19 Apr 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-ai-insights-rapid-diagnostics/<p>Introduction to Netdata&rsquo;s new visualisation providing AI Insights, supporting Rapid Diagnostics. <img src="https://user-images.githubusercontent.com/96257330/233125254-f93c9520-0a3f-4844-8d43-1f3202a5e411.png" alt="logo"></p> <!--truncate--> <h2 id="a-new-era-in-monitoring-systems-dashboards">A New Era in Monitoring Systems Dashboards</h2> <p>We&rsquo;re thrilled to share an important upgrade to Netdata: <strong>AI Insights &amp; Rapid Diagnostics</strong>, a technology aiming to redefine what we expect from a monitoring system.</p> <h2 id="challenges-with-traditional-monitoring-dashboards">Challenges with Traditional Monitoring Dashboards</h2> <p>Traditional monitoring systems rely on a query language to help engineers create dashboards and alerts. While these languages offer power and flexibility, they come with several challenges that make monitoring and troubleshooting more complex and time-consuming:</p>Remote UNIX System Monitoring Using Net-SNMPhttps://www.netdata.cloud/blog/remote-unix-monitoring-with-net-snmp/Wed, 12 Apr 2023 00:00:00 +0000https://www.netdata.cloud/blog/remote-unix-monitoring-with-net-snmp/<p><img src="../2023-04-12-remote-unix-monitoring-with-net-snmp/img/img.jpg" alt="img"></p> <p>Need to monitor a UNIX-like system, but can’t install Netdata on it? With our SNMP collector and Net-SNMP, you can get basic system information with just a bit of relatively quick and easy configuration.</p> <!-- truncate --> <h2 id="what-is-snmp">What is SNMP?</h2> <p>The Simple Network Management Protocol, commonly known as SNMP, is a relatively lightweight protocol designed for monitoring and configuration management for network appliances like switches, routers or gateways. However, it can also be used for those purposes on almost any UNIX-like system thanks to the <a href="http://www.net-snmp.org/">Net-SNMP project</a>.</p>Anomaly Rates in the Menu!https://www.netdata.cloud/blog/anomaly-rates-in-the-menu/Wed, 29 Mar 2023 00:00:00 +0000https://www.netdata.cloud/blog/anomaly-rates-in-the-menu/<p>The menu (on the <a href="https://learn.netdata.cloud/docs/dashboards-and-charts">overview or single node tab</a>) now has an <a href="https://learn.netdata.cloud/docs/netdata-ai/anomaly-detection#anomaly-rate-calculations">anomaly rate</a> button built into it that, for the entire visible window or a highlighted time range, shows the maximum chart anomaly rate within each section.</p> <p>Read on to learn more about this new feature!</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/PgVh_MFHMb0?si=F2Mq6wIxHJWaHykZ" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> <h2 id="wait-what-is-an-anomaly-rate">Wait, what is an anomaly rate?</h2> <p>Netdata is the only monitoring agent that natively (for every metric, with zero config and sane defaults) produces anomaly rates in addition to just collecting raw metrics.</p>Introducing the Netdata demo spacehttps://www.netdata.cloud/blog/netdata-demo/Fri, 24 Mar 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-demo/<p><img src="https://user-images.githubusercontent.com/24860547/201481889-0cf8e192-683f-4a80-9b96-4f69dd85490f.png" alt="image"></p> <p>Introducing Netdata&rsquo;s Demo Space, a quick and easy way to experience monitoring environments before you set them up yourself.</p> <!--truncate--> <p>At Netdata, we are always striving to provide the best monitoring experience for our users. We understand that adopting a new monitoring solution can sometimes be challenging, especially when you&rsquo;re unsure of how it will fit your specific environment. That&rsquo;s why we&rsquo;re excited to announce the Netdata Demo Space!</p>Upcoming Changes to Plugins in Native Packageshttps://www.netdata.cloud/blog/split-plugin-packages/Wed, 15 Mar 2023 00:00:00 +0000https://www.netdata.cloud/blog/split-plugin-packages/<p>At Netdata, we’re committed to trying to make Netdata work as well as possible for our users. Sometimes though, that means changing things in ways that aren’t exactly seamless. Such a change is coming soon for users of our native DEB and RPM packages, and this blog post will explain what’s happening, why we’re doing it, and what it means for our users.</p> <!-- truncate --> <h2 id="whats-changing">What’s changing?</h2> <p>Starting shortly after the v1.39.0 release of the Netdata Agent, we will be splitting most of our external data collection plugins out to their own individual packages instead of bundling them all in the main <code>netdata</code> package. We already have this type of split for our CUPS and FreeIPMI plugins, and this new change will extend that to also provide separate packages for the following plugins:</p>Windows Server Monitoring Improvementshttps://www.netdata.cloud/blog/windows-monitoring-improvements/Mon, 13 Mar 2023 00:00:00 +0000https://www.netdata.cloud/blog/windows-monitoring-improvements/<p><a href="https://www.netdata.cloud/blog/web-servers-and-their-performance/">Monitor your Windows server and applications</a> running on it with Netdata - simple, powerful and free.</p> <!--truncate--> <p>Hey Netdata community,</p> <p>We have some exciting news for you: we’re launching our new and updated <a href="https://learn.netdata.cloud/docs/data-collection/monitor-anything/System%20Metrics/Windows-machines">Windows collectors</a> with the goal of making the <a href="https://www.netdata.cloud/solutions/technologies/windows-monitoring/">Windows monitoring experience</a> as seamless as possible 🎉</p> <p>We know that Windows monitoring has been a long time ask from many of you, and we’ve been working hard to make it easier than ever to monitor your Windows metrics with Netdata.</p>Anomaly detection on Prometheus metricshttps://www.netdata.cloud/blog/anomaly-detection-on-prometheus-metrics/Wed, 01 Mar 2023 00:00:00 +0000https://www.netdata.cloud/blog/anomaly-detection-on-prometheus-metrics/<p><img src="../2023-03-01-anomaly-detection-on-prometheus-metrics/img/img.png" alt="img"></p> <p>We have recently extended the native machine learning (ML) based anomaly detection <a href="https://learn.netdata.cloud/guides/monitor/anomaly-detection">capabilities</a> of Netdata to <a href="https://github.com/netdata/netdata/issues/14218">support all metrics</a>, regardless on their collection frequency (<code>update every</code>).</p> <p>Previously only metrics collected every second were supported, but now Netdata can run anomaly detection out of the box with zero config on metrics with any collection frequency.</p> <p>This post will illustrate an example of what this means using <a href="https://prometheus.io/">Prometheus</a> metrics (via the <a href="https://learn.netdata.cloud/docs/collecting-metrics/collectors/applications/prometheus-endpoint">Netdata Prometheus collector</a>) since they typically have a default collection frequency of 10 seconds.</p>Monitor any SQL metrics with Netdata (and Pandas ❤️)https://www.netdata.cloud/blog/monitor-any-sql-metrics-with-netdata/Wed, 22 Feb 2023 00:00:00 +0000https://www.netdata.cloud/blog/monitor-any-sql-metrics-with-netdata/<p><img src="../2023-02-22-monitor-any-sql-metrics-with-netdata/img/img.png" alt="img"></p> <p>We recently got this great feedback from a dear user in our <a href="https://discord.com/channels/847502280503590932/1075370683393118278/1075723915265069106">Discord</a>:</p> <blockquote> <p>I would really like to use Netdata to monitor custom internal metrics that come from SQL, not a fan of having 10 diff systems doing essentially the same thing as is, Netdata is pretty much all there in that regard, just needs a few extra features.</p> </blockquote> <p>This is great and exactly what we want, a clear problem or improvement we could make to help make that users monitoring life a little easier.</p>Introducing Netdata Functions (↑ Top)https://www.netdata.cloud/blog/netdata-functions/Wed, 15 Feb 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-functions/<p>Netdata is committed to making it simpler and easier for everyone to monitor and troubleshoot their infrastructure. With that goal in mind, we&rsquo;re excited to announce the launch of our new &ldquo;Functions&rdquo; feature (↑ Top), which allows Netdata Agent collectors to expose &ldquo;functions&rdquo; that can be executed in run-time and on-demand.</p> <!--truncate--> <h3 id="what-are-netdata-functions">What are Netdata functions?</h3> <p>Netdata has always been synonymous with real time monitoring and automated dashboards, with the recent introduction of &ldquo;functions&rdquo;, there&rsquo;s now a new way for users to troubleshoot their infrastructure. <strong>A function, in the context of Netdata, is a routine or script that can be invoked to run on a node and retrieve useful information, which is then displayed in the Netdata cloud dashboard.</strong></p>Introducing Netdata Paid Subscriptionshttps://www.netdata.cloud/blog/introducing-netdata-paid-subscriptions/Fri, 10 Feb 2023 00:00:00 +0000https://www.netdata.cloud/blog/introducing-netdata-paid-subscriptions/<p>All Netdata functionality is and will be available for free forever in the Community Plan. Paid tiers include features targeted for businesses and users who would need to customise their monitoring solution with different levels of user access, extra notification mechanisms, customer support and more.</p> <!--truncate--> <p><strong>Hello Netdata community</strong>,</p> <p>We are excited to announce that we are introducing new <strong>Paid Subscriptions</strong> to Netdata as of Wednesday, 22nd of February 2023.</p>Release 1.38: Dramatic Performance & Stability Gainshttps://www.netdata.cloud/blog/netdata-version-1.38/Mon, 06 Feb 2023 00:00:00 +0000https://www.netdata.cloud/blog/netdata-version-1.38/<p>Another release of the Netdata Monitoring solution is here!</p> <div style="position: relative; padding-bottom: 56.25%; height: 0; overflow: hidden;"> <iframe allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share; fullscreen" loading="eager" referrerpolicy="strict-origin-when-cross-origin" src="https://www.youtube.com/embed/2EjKicsRYxw?autoplay=0&amp;controls=1&amp;end=0&amp;loop=0&amp;mute=0&amp;start=0" style="position: absolute; top: 0; left: 0; width: 100%; height: 100%; border:0;" title="YouTube video"></iframe> </div> <ul> <li><a href="#v1380-release-highlights">Release Highlights</a> <ul> <li> <p><strong><a href="#v1380-dbenginev2">DBENGINE v2</a></strong> The new open-source database engine for Netdata Agents, offering huge performance, scalability and stability improvements, with a fraction of memory footprint!</p> </li> <li> <p><strong><a href="#v1380-functions">FUNCTION: Processes</a></strong> Netdata beyond metrics! We added the ability for <strong>runtime functions</strong>, that can be implemented by any data collection plugin, to offer unlimited visibility to anything, even not-metrics, that can be valuable while troubleshooting.</p>Extending Netdata's anomaly detection training windowhttps://www.netdata.cloud/blog/extending-anomaly-detection-training-window/Thu, 02 Feb 2023 00:00:00 +0000https://www.netdata.cloud/blog/extending-anomaly-detection-training-window/<p>We have been busy at work under the hood of the Netdata agent to introduce new capabilities that let you extend the &ldquo;training window&rdquo; used by Netdata&rsquo;s <a href="https://learn.netdata.cloud/docs/netdata-ai/anomaly-detection/ml-configuration">native anomaly detection capabilities</a>.</p> <p>This blog post will discuss one of these improvements to help you reduce &ldquo;<a href="https://en.wikipedia.org/wiki/False_positives_and_false_negatives#False_positive_error">false positives</a>&rdquo; by essentially extending the training window by using the new (beautifully named) <code>number of models per dimension</code> configuration parameter.</p> <h2 id="background">Background</h2> <p>One of the most important considerations of our native anomaly detection capabilities is the overhead of running the training and scoring computations required to train thousands of models (one per metric) and produce <a href="https://learn.netdata.cloud/docs/netdata-ai/anomaly-detection#the-anomaly-bit">anomaly bits</a> every second based on those trained models.</p>Release 1.37.1: Patch Release For Security Issueshttps://www.netdata.cloud/blog/netdata-version-1.37.1/Mon, 05 Dec 2022 00:00:00 +0000https://www.netdata.cloud/blog/netdata-version-1.37.1/<p>Netdata v1.37.1 is a patch release to address issues discovered since v1.37.0. Refer to the <a href="https://github.com/netdata/netdata/releases/tag/v1.37.0">v.1.37.0 release notes</a> for the full scope of that release.</p> <!--truncate--> <h2 id="release-v1371">Release v1.37.1</h2> <p>Netdata v1.37.1 is a patch release to address issues discovered since v1.37.0. Refer to the <a href="https://github.com/netdata/netdata/releases/tag/v1.37.0">v.1.37.0 release notes</a> for the full scope of that release.</p> <p>The v1.37.1 patch release fixes the following issues:</p> <ul> <li>Parent agent crash when many children instances (re)connect at the same time, causing simultaneous SSL re-initialization (<a href="https://github.com/netdata/netdata/pull/14076">PR #14076</a>).</li> <li>Agent crash during dbengine database file rotation while a page is being read while being deleted (<a href="https://github.com/netdata/netdata/pull/14081">PR #14081</a>).</li> <li>Agent crash on metrics page alignment when metrics were stopped being collected for a long time and then started again (<a href="https://github.com/netdata/netdata/pull/14086">PR #14086</a>).</li> <li>Broken Fedora native packages (<a href="https://github.com/netdata/netdata/pull/14082">PR #14082</a>).</li> <li>Fix dbengine backfilling statistics (<a href="https://github.com/netdata/netdata/pull/14074">PR #14074</a>).</li> </ul> <p>In addition, the release contains the following optimizations and improvements:</p>Release 1.37: Infinite Scalability & Database Tieringhttps://www.netdata.cloud/blog/netdata-version-1.37/Wed, 30 Nov 2022 00:00:00 +0000https://www.netdata.cloud/blog/netdata-version-1.37/<p>Another release of the Netdata Monitoring solution is here!</p> <p>We focused on these key areas:</p> <p>Infinite scalability of the Netdata Ecosystem</p> <p>Default Database Tiering, offering months of data retention for typical Netdata Agent installations with default settings and years of data retention for dedicated Netdata Parents.</p> <p>Overview Dashboards at Netdata Cloud got a ton of improvements to allow slicing and dicing of data directly on the UI and overcome the limitations of the web technology when thousands of charts are presented on one page.</p>Monitor & Troubleshoot ISP Performance With Netdatahttps://www.netdata.cloud/blog/speedtest-monitoring/Mon, 28 Nov 2022 00:00:00 +0000https://www.netdata.cloud/blog/speedtest-monitoring/<p>Find out how to monitor your Internet speed and quality and how well your ISP is performing.</p> <p><img src="https://user-images.githubusercontent.com/24860547/204470316-4682e442-6df1-4c77-b1e4-fdd96dd404f0.jpg" alt="logo"></p> <!--truncate--> <h2 id="what-factors-affect-my-internet-speed">What Factors Affect My Internet Speed?</h2> <p>Several factors can influence your internet speed, ranging from your ISP&rsquo;s infrastructure to your home setup. Here&rsquo;s a breakdown:</p> <h3 id="1-isp-plan--bandwidth">1. ISP Plan &amp; Bandwidth</h3> <p>The speed you experience depends on the plan you choose from your ISP. Higher-tier plans offer more bandwidth, which means faster speeds for downloading, streaming, and gaming.</p>How to monitor node reboots?https://www.netdata.cloud/blog/monitoring-node-reboots/Thu, 17 Nov 2022 00:00:00 +0000https://www.netdata.cloud/blog/monitoring-node-reboots/<p>Monitoring the health and status of nodes and servers is a critical part of effective infrastructure monitoring.</p> <p><img src="https://user-images.githubusercontent.com/96257330/202475049-22838a0b-73b1-485b-8416-5fd49d6ccb53.png" alt="logo"></p> <!--truncate--> <h2 id="how-to-monitor-node-reboots">How to monitor node reboots?</h2> <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 &ldquo;Hardware manager&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.</p>How To Mute Alerts During Maintenance Windowshttps://www.netdata.cloud/blog/mute-alerts/Thu, 03 Nov 2022 00:00:00 +0000https://www.netdata.cloud/blog/mute-alerts/<p>The health management APIs in Netdata allows teams to eliminate unnecessary alerting during scheduled maintenance, testing, auto scaling events, and instance reboots.</p> <!--truncate--> <p>For all SREs, it is absolutely crucial to filter out expected events during maintenance windows and quickly pinpoint critical issues in your infrastructure. Every minute is crucial while dealing with troubleshooting issues and any distractions that may hijack the troubleshooting process should be subdued. The health <a href="https://www.netdata.cloud/blog/iot-monitoring-challenges/">management APIs</a> in Netdata allows teams to eliminate unnecessary alerting during scheduled maintenance, testing, <a href="https://www.netdata.cloud/blog/server-uptime-monitoring-why-do-we-need-it/">auto scaling events</a>, and instance reboots.</p>Monitor indoor air quality with Airthings and Netdatahttps://www.netdata.cloud/blog/airquality/Wed, 02 Nov 2022 00:00:00 +0000https://www.netdata.cloud/blog/airquality/<p>Monitoring indoor air quality with <a href="https://www.airthings.com/">Airthings</a> and Netdata. Understanding and measuring common contaminants and pollutants reduces your risk of air quality health concerns.</p> <!--truncate--> <h2 id="indoor-air-quality-and-what-to-monitor">Indoor air quality and what to monitor</h2> <p>Indoor air quality can be a crucial influence on your health, wellbeing and productivity.</p> <p>Understanding and measuring common contaminants and pollutants is the first step towards reducing your risk of air quality health concerns.</p> <p>Airthings is a company that makes great air quality sensors that measure a wide variety of different variables including:</p>Monitor KSM performance with Netdatahttps://www.netdata.cloud/blog/ksm/Tue, 01 Nov 2022 00:00:00 +0000https://www.netdata.cloud/blog/ksm/<p>Monitoring KSM (Kernel Same-page Merging) performance at deduping memory shared across VMs.</p> <!--truncate--> <h2 id="kernel-same-page-merging-ksm">Kernel Same-page Merging (KSM)</h2> <p>Linux kernels store memory in <strong>pages</strong> which are moved in and out of memory as a single block. On most Linux architectures pages are 4096 bytes. <strong>KSM</strong> (Kernel Same-page Merging) is a kernel feature that scans memory looking for pages with identical content, and then de-duplicates them. The most common use-case where such duplicate pages occur is on hosts running multiple virtual machines (VMs).</p>Monitoring & troubleshooting Cassandra with Netdatahttps://www.netdata.cloud/blog/cassandra-monitoring-part2/Sat, 29 Oct 2022 00:00:00 +0000https://www.netdata.cloud/blog/cassandra-monitoring-part2/<p>How to monitor and troubleshoot Cassandra with Netdata.</p> <p><img src="https://user-images.githubusercontent.com/24860547/198524087-37dda416-a9a9-4c55-b379-0f46e990f83f.png" alt="logo"></p> <!--truncate--> <p><em><strong>Note</strong>: This post is the second part of a Cassandra monitoring series. Be sure to read our first entry <a href="https://blog.netdata.cloud/cassandra-monitoring-part1">here</a>.</em></p> <h2 id="monitoring-cassandra-with-netdata">Monitoring Cassandra with Netdata</h2> <p>Netdata’s <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/cassandra">Cassandra collector documentation</a> explains how to set it up to collect metrics automatically.</p> <p>Once you have followed the instructions in the docs and have installed and configured Netdata on the Cassandra cluster you are ready to start monitoring and troubleshooting. Check out the <a href="https://app.netdata.cloud/spaces/netdata-demo/rooms/cassandra/overview">Cassandra demo room</a> to interact with the charts, metrics and other functionality described here.</p>How to monitor and fix Database bloats in PostgreSQL?https://www.netdata.cloud/blog/postgresql-database-bloat/Fri, 28 Oct 2022 00:00:00 +0000https://www.netdata.cloud/blog/postgresql-database-bloat/<p>Database bloat is disk space that was used by a table or index and is available for reuse by the database but has not been reclaimed. Bloat is created when deleting or updating tables and indexes. Here&rsquo;s how to deal with it!</p> <!--truncate--> <h2 id="what-is-database-bloat">What is Database bloat?</h2> <p>Database bloat is disk space that was used by a table or index and is available for reuse by the database but has not been reclaimed. Bloat is created when deleting or updating tables and indexes.</p>Cassandra Monitoring: Key Metrics & Best Practiceshttps://www.netdata.cloud/blog/cassandra-monitoring-part1/Thu, 27 Oct 2022 00:00:00 +0000https://www.netdata.cloud/blog/cassandra-monitoring-part1/<p>What are the important Cassandra metrics to monitor and how to monitor them.</p> <!--truncate--> <h2 id="what-is-cassandra--why-use-it">What Is Cassandra &amp; Why Use It</h2> <p>Cassandra is an open-source, distributed, wide-column NoSQL database management system written in Java. Cassandra was originally developed by <a href="https://twitter.com/hedvigeng">Avinash Lakshmanan</a> and <a href="https://twitter.com/pmalik">Prashant Malik</a> at Facebook and then released as open source, eventually becoming part of the <a href="https://www.netdata.cloud/monitoring-101/apache-monitoring/">Apache</a> project.</p> <p><a href="https://www.netdata.cloud/integrations/data-collection/databases/cassandra/">Cassandra is a NoSQL database</a> - NoSQL (also known as &ldquo;not only SQL&rdquo;) databases do not require data to be stored in tabular format. They provide flexible schemas and scale easily with large amounts of data and high user loads.</p>How to find out which application is causing server loadhttps://www.netdata.cloud/blog/server-load/Wed, 26 Oct 2022 00:00:00 +0000https://www.netdata.cloud/blog/server-load/<p>We often hear the term load used to describe the state of a server or a device, but we&rsquo;re here to tell you what it means, precisely, and how to monitor it.</p> <!--truncate--> <h2 id="what-is-server-load">What is server load?</h2> <p>We often hear the term &ldquo;load&rdquo; used to describe the state of a server or a <a href="https://www.netdata.cloud/blog/iot-monitoring-challenges/">device</a>. But what does it really mean?</p> <p>System load is a measure of the amount of computational work that a system performs. An overloaded system, by definition, isn&rsquo;t able to complete all its tasks per schedule - this affects the performance and productivity of the system. And while &ldquo;load&rdquo; often gets conflated with CPU usage there&rsquo;s a lot more to it.</p>How to monitor the disk usage on your infrastructurehttps://www.netdata.cloud/blog/disk-usage/Tue, 25 Oct 2022 00:00:00 +0000https://www.netdata.cloud/blog/disk-usage/<p>The most important part of disk usage monitoring is to check the utilization of each filesystem and each mount point which can reveal existing or impending issues with the storage space on your infrastructure.</p> <!--truncate--> <h2 id="what-does-disk-usage-du-mean">What Does Disk Usage (DU) Mean?</h2> <p>Disk usage (DU) refers to the portion or percentage of computer storage that is currently in use. It contrasts with disk space or <a href="https://www.netdata.cloud/blog/server-uptime-monitoring-why-do-we-need-it/">capacity</a>, which is the total amount of space that a given disk is capable of storing. Disk usage is a crucial metric to any computing system, as it gives the user the information needed not only for storage, but also software requirements and overall operation. Although it usually refers to a computer’s hard disk, it may also refer to external storage, such as a USB drive or compact disc (CD).</p>7 types of Redis latency and how to fix ithttps://www.netdata.cloud/blog/7-types-of-redis-latency/Mon, 24 Oct 2022 00:00:00 +0000https://www.netdata.cloud/blog/7-types-of-redis-latency/<p>Redis is designed to be fast. In most cases, it is. However, there are times when Redis may be slow, due to network issues, disk latency, or other factors. When this happens, it is important to be able to <a href="https://www.netdata.cloud/blog/server-uptime-monitoring-why-do-we-need-it/">detect the slow down</a> and investigate the cause of Redis latency.</p> <!--truncate--> <h2 id="redis--latency">Redis &amp; latency</h2> <p>Latency is the maximum delay between the time a client issues a command and the time the reply to the command is received by the client. Redis has strict requirements on average and worst case latency.</p>How to monitor systemd service livenesshttps://www.netdata.cloud/blog/systemd-service-liveness/Fri, 21 Oct 2022 00:00:00 +0000https://www.netdata.cloud/blog/systemd-service-liveness/<p>The life of a sysadmin or SRE is often difficult, but occasionally very simple things can make a huge difference. Basic monitoring of your systemd services is one of those simple things, which we sometimes overlook. The simplest question one would want to know is if the thing that’s supposed to be running is actually running at all. If you use systemd services, you can guarantee an answer to that question within minutes using Netdata.</p>Web Servers Monitoring: Key Metrics & Strategieshttps://www.netdata.cloud/blog/web-servers-and-their-performance/Thu, 20 Oct 2022 00:00:00 +0000https://www.netdata.cloud/blog/web-servers-and-their-performance/<!--truncate--> <h2 id="the-importance-of-monitoring-web-servers">The Importance Of Monitoring Web Servers</h2> <p>Web servers are among the most important components in modern <a href="https://www.netdata.cloud/blog/future-of-infrastructure-monitoring/">IT infrastructures</a>. They host the websites, web services, and <a href="https://www.netdata.cloud/monitoring-101/dotnet-monitoring/">web applications</a> that we use on a daily basis. Social networking, media streaming, software as a service (SaaS), and other activities wouldn’t be possible without the use of web servers. And with the advent of cloud computing and the movement of more services online, <a href="https://www.netdata.cloud/blog/server-uptime-monitoring-why-do-we-need-it/">web servers and their monitoring are only becoming more important</a>. Given the extensive usage of Web servers, Sysadmins and SREs should monitor web servers as a key aspect for performance. </p>Using Pandas In Python: Data Analysis & Performance Insightshttps://www.netdata.cloud/blog/pandas-python/Wed, 19 Oct 2022 00:00:00 +0000https://www.netdata.cloud/blog/pandas-python/<p>Netdata just got a <a href="https://learn.netdata.cloud/docs/agent/collectors/python.d.plugin/pandas" target="_blank" rel="noopener">Pandas collector</a>.</p> <!--truncate--> <p>Pandas is a de-facto standard in reading and processing most types of structured data in Python so if you have some csv/json/xml data, either locally or via some HTTP endpoint, containing metrics you&rsquo;d like to monitor, chances are you can now easily do this by leveraging the Pandas collector without having to develop your own custom collector as you might have in the past.</p>How to monitor HTTP endpointshttps://www.netdata.cloud/blog/http-endpoints/Mon, 17 Oct 2022 00:00:00 +0000https://www.netdata.cloud/blog/http-endpoints/<p>The <a href="https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol">HTTP protocol</a> has become the de facto standard application layer protocol of the internet. From publicly available web sites and APIs to “inter-process” communications in REST based microservice architectures or large <a href="https://en.wikipedia.org/wiki/Service-oriented_architecture">Service Oriented Architectures</a> based on <a href="https://en.wikipedia.org/wiki/SOAP">SOAP</a>, you find HTTP being used again and again, due to its simplicity and our familiarity with it. How many protocols can you name that have <a href="https://imgur.com/gallery/4KqWq">memes</a> for their status codes? Of course, such a popular protocol has endless pages written about how to properly monitor the services that rely on it, with many options specific to every use case.<!--truncate--> What you will learn here is how to get your basics done in monitoring HTTP endpoints, so you can be up and running in a few minutes, monitoring all HTTP services in your <a href="https://www.netdata.cloud/blog/future-of-infrastructure-monitoring/">entire infrastructure</a>. </p>How to monitor DNS query response timehttps://www.netdata.cloud/blog/dns-query-response-time/Wed, 12 Oct 2022 00:00:00 +0000https://www.netdata.cloud/blog/dns-query-response-time/<p>DNS (Domain Name System) servers translate standard language web addresses to their actual IP addresses for network access.</p> <p><a href="https://xiaolishen.medium.com/the-dns-lookup-journey-240e9a5d345c"><strong>DNS Lookup Journey</strong></a> <img src="../wp-archive/uploads/2022/10/DNS-1.png" alt=""></p> <!--truncate--> <p>DNS response time is the time it takes a Domain Name Server to receive the request for a domain name’s IP address, process it, and return the IP address to the browser or application requesting it. When it comes to DNS response times, the lower the better, and generally values less than 100ms are considered to be in the acceptable range (depending on the application).</p>Why is data replication important?https://www.netdata.cloud/blog/why-is-data-replication-important/Wed, 12 Oct 2022 00:00:00 +0000https://www.netdata.cloud/blog/why-is-data-replication-important/<p>High availability. This is what every monitoring tool needs to ensure that you never compromise on IT infrastructure visibility.<!--truncate--> On top of high availability, do you really want to enable all available features on your production system? It is important for the monitoring tool to have a low footprint on your CPU consumption and memory usage. Let’s dive deeper into the recommended way of configuring Netdata to ensure high availability and a low resource footprint through data replication.</p>How to monitor host reachabilityhttps://www.netdata.cloud/blog/how-to-monitor-host-reachability/Mon, 10 Oct 2022 00:00:00 +0000https://www.netdata.cloud/blog/how-to-monitor-host-reachability/<p>Most sysadmins and developers have at some point used a few of the popular <a href="https://www.tecmint.com/linux-networking-commands" target="_blank" rel="noopener">Linux networking commands</a> or their Windows equivalents to answer the common questions of <a href="https://www.netdata.cloud/blog/web-servers-and-their-performance/">host reachability</a> - that is, whether a host or service is reachable and how fast it responds.</p> <!--truncate--> <h2 id="common-approaches-to-reachability">Common approaches to reachability</h2> <p>One of the simplest, common checks, is to simply <code>ping</code> a host to verify that it’s reachable from where you issue the command, and to see the total time it takes for the host to receive your request.</p>Introducing the Netdata Source Plugin for Grafanahttps://www.netdata.cloud/blog/introducing-netdata-source-plugin-for-grafana/Fri, 07 Oct 2022 00:00:00 +0000https://www.netdata.cloud/blog/introducing-netdata-source-plugin-for-grafana/<p><img src="../wp-archive/uploads/2022/09/postgresql_dash-600x354.png" alt="sample-dashboard"></p> <p>The open-source community is about to benefit greatly from Netdata&rsquo;s new Grafana data source plugin, which makes use of a powerful data collection engine.</p> <!--truncate--> <p>This new plugin maximizes the troubleshooting capabilities of Netdata in Grafana, making them more widely available. Some of the key capabilities provided to you with this plugin include the following:</p> <ul> <li>Real-time monitoring with single-second granularity.</li> <li>Installation and out-of-the-box integrations available in seconds from one line of code.</li> <li>2,000+ metrics from across your whole Infrastructure, with insightful metadata associated with them.</li> <li>Access to our fresh ML metrics (anomaly rates) - exposing our ML capabilities at the edge!</li> </ul> <h2 id="why-did-we-decide-to-do-it">Why did we decide to do it?</h2> <p>We are huge fans of Open-Source culture. Open-source is deeply rooted in Netdata&rsquo;s DNA. Because of this, at Netdata, we don’t really buy into the “single pane of glass” or “observability platform” buzzwords. The reality is that things are just more complicated than that in real life.</p>How to filter metrics by label?https://www.netdata.cloud/blog/how-to-filter-metrics-by-label/Thu, 06 Oct 2022 00:00:00 +0000https://www.netdata.cloud/blog/how-to-filter-metrics-by-label/<p>It is sometimes easy to get lost in the mountain of metrics and infinite number of dimensions when working with an infrastructure monitoring tool. Being able to filter metrics by label and visualize only what is relevant to the current scope of monitoring &amp;troubleshooting, becomes absolutely crucial to the success of SREs, Sysadmins and DevOps professionals.</p> <!--truncate--> <p>The Netdata <a href="https://learn.netdata.cloud/docs/dashboards-and-charts/charts#labels-dropdown">chart label filtering feature</a> supports grouping by and filtering each chart based on labels (key/value pairs) applicable to the context and provides fine-grain capability on slicing the data / metrics.</p>Missing indexes in PostgreSQL? How to quickly identify ithttps://www.netdata.cloud/blog/missing-indexes-in-postgresql/Wed, 05 Oct 2022 00:00:00 +0000https://www.netdata.cloud/blog/missing-indexes-in-postgresql/<p>While working on improving the <a href="https://www.netdata.cloud/monitoring-101/postgresql-monitoring/">Netdata PostgreSQL collector</a>, we were monitoring our production PostgreSQL instance and something caught our attention immediately. The rows fetched ratio seemed really, really low for one particular database&hellip; there were missing indexes in PostgreSQL!</p> <!--truncate--> <p><b>Rows fetched ratio</b> is the percentage of rows that contain data needed to execute the query (rows fetched), out of the total number of rows scanned (rows returned). A low value indicates that the database is performing extra work by scanning a large number of rows that aren’t required to process the query.</p>Data Collection Strategies For Infrastructurehttps://www.netdata.cloud/blog/data-collection-strategies/Tue, 06 Sep 2022 00:00:00 +0000https://www.netdata.cloud/blog/data-collection-strategies/<!--truncate--> <p>Monitoring and troubleshooting; unfortunately, these terms are still used interchangeably, which can lead to misunderstandings about data collection strategies.</p> <p>In this article we aim to clarify some important definitions, processes, and common data collection strategies for monitoring solutions. We will specify the limitations of the described strategies, as well as key benefits which can potentially be also used for troubleshooting needs.</p> <p><strong>IT infrastructure monitoring</strong> is a business process of collecting and analyzing data over a period of time to improve business results.</p>How Netdata’s Machine Learning workshttps://www.netdata.cloud/blog/how-netdatas-machine-learning-works/Thu, 01 Sep 2022 00:00:00 +0000https://www.netdata.cloud/blog/how-netdatas-machine-learning-works/<p>Following on from the <a href="https://www.netdata.cloud/blog/introducing-anomaly-advisor-unsupervised-anomaly-detection-in-netdata" target="_blank" rel="noopener">recent launch</a> of our <a href="https://learn.netdata.cloud/docs/cloud/insights/anomaly-advisor" target="_blank" rel="noopener">Anomaly Advisor</a> feature, and in keeping with <a href="https://www.netdata.cloud/blog/our-approach-to-machine-learning/" target="_blank" rel="noopener">our approach to machine learning</a>, <a href="https://github.com/netdata/netdata/blob/master/src/ml/notebooks/netdata_anomaly_detection_deepdive.ipynb" target="_blank" rel="noopener">here</a> is a detailed Python notebook outlining exactly how the machine learning powering the Anomaly Advisor actually works under the hood.</p> <!--truncate--> <p>Or if you&rsquo;d rather watch a video walkthrough of the notebook then check out below.</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/L1xleckyuDQ?si=rptYzWE-eLlhSL9x" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> <p>Try it for yourself, <a href="https://learn.netdata.cloud/docs/cloud/get-started" target="_blank" rel="noopener">get started</a> by <a href="https://app.netdata.cloud/?utm_source=blog&amp;utm_content=how_netdata_ml_works" target="_blank" rel="noopener">signing in to Netdata</a> and connecting a node. Once initial models have been trained (usually after the agent has about one hour of data, zero configuration needed), you&rsquo;ll be able to start exploring in the <a href="https://learn.netdata.cloud/docs/cloud/insights/anomaly-advisor" target="_blank" rel="noopener">Anomaly Advisor</a> tab of Netdata.</p>Anomaly rate in every charthttps://www.netdata.cloud/blog/anomaly-rate-in-every-chart/Thu, 23 Jun 2022 00:00:00 +0000https://www.netdata.cloud/blog/anomaly-rate-in-every-chart/<p>A month ago, we introduced unsupervised ML &amp; Anomaly Detection in Netdata, the <a href="https://www.netdata.cloud/blog/introducing-anomaly-advisor-unsupervised-anomaly-detection-in-netdata/">Anomaly Advisor</a>. Today, we’re happy to announce that we’re bringing anomaly rates to every chart in Netdata Cloud. Anomaly information is no longer limited to the Anomalies tab and will be accessible to you from the Overview and Single Node View tabs as well. This will make your troubleshooting journey easier, as you will have the anomaly rates for any metric available with a single click. Whichever metric or chart you&rsquo;re exploring will be instant.</p>Metric Correlations on the Agenthttps://www.netdata.cloud/blog/metric-correlations-on-the-agent/Wed, 15 Jun 2022 00:00:00 +0000https://www.netdata.cloud/blog/metric-correlations-on-the-agent/<p>As of <a href="https://github.com/netdata/netdata/releases/tag/v1.35.0" target="_blank" rel="noopener"><code>v1.35.0</code></a> the Netdata Agent can now run <a href="https://learn.netdata.cloud/docs/cloud/insights/metric-correlations" target="_blank" rel="noopener">Metric Correlations</a> (MC) itself. This means that, for nodes with MC enabled, the Metric Correlations feature just got a whole lot faster!</p> <!--truncate--> <p>The Netdata Metric Correlations feature uses a <a href="https://en.wikipedia.org/wiki/Kolmogorov%E2%80%93Smirnov_test#Two-sample_Kolmogorov%E2%80%93Smirnov_test" target="_blank" rel="noopener">Two Sample Kolmogorov-Smirnov test</a> to look for which metrics have a significant distributional change around a highlighted window of interest. This can be useful when you are interested in short term &ldquo;<a href="https://en.wikipedia.org/wiki/Change_detection" target="_blank" rel="noopener">change detection</a>&rdquo; and want to try answer the question &ldquo;what else changed around this time?&rdquo;.</p>Anomaly Advisor: Unsupervised Anomaly Detectionhttps://www.netdata.cloud/blog/introducing-anomaly-advisor-unsupervised-anomaly-detection-in-netdata/Thu, 26 May 2022 00:00:00 +0000https://www.netdata.cloud/blog/introducing-anomaly-advisor-unsupervised-anomaly-detection-in-netdata/<p>Today we are excited to launch one of our flagship ML assisted troubleshooting features in Netdata – the Anomaly Advisor.</p> <p>The Anomaly Advisor builds on earlier work to introduce unsupervised <a href="https://github.com/netdata/netdata/blob/master/src/ml/README.md">anomaly detection</a> capabilities into the <a href="https://www.netdata.cloud/open-source">Netdata Agent</a> from <a href="https://github.com/netdata/netdata/releases/tag/v1.32.0">v1.32.0</a> onwards.</p> <h2 id="getting-started">Getting Started</h2> <p>Once you <a href="https://learn.netdata.cloud/docs/netdata-ai/anomaly-detection/ml-configuration">enable ML</a> on your nodes, each node will begin producing an &ldquo;<a href="https://learn.netdata.cloud/docs/netdata-ai/anomaly-detection#the-anomaly-bit">Anomaly Bit</a>&rdquo; every second in addition to raw metric values. This anomaly bit will be 1 when the trained ML models consider recent raw data for a metric to look anomalous or 0 when things look &rsquo;normal&rsquo;. The Anomaly Advisor leverages this information to enable seamless space or room level anomaly detection out of the box with minimal configuration.</p>Monitoring without Cooperation: Kuberneteshttps://www.netdata.cloud/blog/monitoring-without-cooperation-kubernetes/Fri, 20 May 2022 00:00:00 +0000https://www.netdata.cloud/blog/monitoring-without-cooperation-kubernetes/<!--truncate--> <iframe width="560" height="315" src="https://www.youtube.com/embed/J2kdSTRJzV4?si=Rqv4gpqz_wZKusaZ" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> <p>Imagine this: You are an engineer at a startup. You are responsible for keeping all the applications running smoothly and safely in production. At first, you have things under control, but soon enough things start getting more complex. The system has grown by hundreds of new server nodes, new services and containers are showing up seemingly every day, and you hear there’s a project to transition everything to Kubernetes (you’ve heard the term “cloud native” so often that the phrase shows up in your dreams).</p>Kubernetes Throttling Doesn’t Have To Suck. Let Us Help!https://www.netdata.cloud/blog/kubernetes-throttling-doesnt-have-to-suck-let-us-help/Tue, 03 May 2022 00:00:00 +0000https://www.netdata.cloud/blog/kubernetes-throttling-doesnt-have-to-suck-let-us-help/<p>CPU limits are probably the most misunderstood concept in Kubernetes CPU resources allocation and management.</p> <!--truncate--> <p>A lot of engineers advise the use of CPU limits on every container as Kubernetes best practice. Unfortunately, as we will prove below, they are wrong: CPU limits should rarely be used, if used at all!</p> <p>But why? What are the reasons that even senior DevOps engineers with vast experience in the field advise the use of CPU limits?</p>Troubleshooting Alerts the Right Way: As a Teamhttps://www.netdata.cloud/blog/troubleshooting-alerts/Thu, 28 Apr 2022 00:00:00 +0000https://www.netdata.cloud/blog/troubleshooting-alerts/<!--truncate--> <p>At Netdata, we love two things more than anything else: </p> <ol> <li> Troubleshooting and,</li> <li> Making things easier for you! </li> </ol> Our goal is to make troubleshooting and monitoring as seamless as possible with the open-source Agent. This includes giving you pre-configured alerts so that you get notified immediately when a disruption occurs. <p>The Netdata Agent comes with over 250 pre-configured and optimized alerts. But we want you to be the master of your infrastructure monitoring by:</p>CNCF Live: Machine Learning Anomaly Detectionhttps://www.netdata.cloud/blog/cncf-live-power-up-your-machine-learning-automated-anomaly-detection/Wed, 27 Apr 2022 00:00:00 +0000https://www.netdata.cloud/blog/cncf-live-power-up-your-machine-learning-automated-anomaly-detection/<h2 id="join-us-live-to-talk-ml">Join Us Live to Talk ML</h2> <p>Join ML Lead Andrew Maguire and Product Manager Shyam Sreevalsan on the 23rd of June at 5pm UTC for the Netdata Machine Learning Meetup, which will be livestreamed on Youtube. In this session, we will demo and preview new and future features, along with a Q&amp;A, and discuss the following topics:</p> <ul> <li>The role of Machine Learning in DevOps Infrastructure Monitoring &amp; Troubleshooting</li> <li>The Netdata way of approaching Machine Learning</li> <li>Challenges of building Macvhine learning solutions that are useful and user friendly.</li> </ul> Feel free to ask questions or share ideas on <a href="https://discord.gg/ZyeDHQTdaW">our Community Discord</a>. <h2 id="cncf-live-power-up-your-machine-learning---automated-anomaly-detection">CNCF Live: Power up your machine learning - Automated anomaly detection</h2> <p>Our Analytics &amp; ML lead Andrew Maguire recently had a chance to share our new <a href="https://community.netdata.cloud/t/anomaly-advisor-beta-launch/2717">Anomaly Advisor</a> feature with the wider CNCF community. In his demonstration he did some light chaos engineering (using <a href="https://www.gremlin.com/">Gremlin</a> and <a href="https://wiki.ubuntu.com/Kernel/Reference/stress-ng">stress-ng</a>) to generate some real anomalies on his infrastructure and watch how it all played out in the Anomaly Advisor in Netdata Cloud.</p>The Netdata Way of Troubleshootinghttps://www.netdata.cloud/blog/the-netdata-way-of-troubleshooting/Mon, 04 Apr 2022 00:00:00 +0000https://www.netdata.cloud/blog/the-netdata-way-of-troubleshooting/<p>Together with you, our fabulous community, Netdata is changing the way the world thinks of high fidelity monitoring - and we are gaining momentum.</p> <p>Our chief troublemaker and CEO, Costa Tsaousis,  is the pioneer and architect of this revolution that’s brewing in the monitoring and troubleshooting space.</p> <p>Watch him explain the <strong>Netdata way of troubleshooting</strong>:</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/ExjwwrgXvPg?si=IrsEp9PqbFFWiegM" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe> <h2 id="why-did-the-world-need-a-new-infrastructure-monitoring-tool-0018">Why did the world need a new infrastructure monitoring tool? (00:18)</h2> <p>Every great hero needs an origin story. In this section, Costa explains the frustrating conditions in the infrastructure and monitoring space that lead to the conception, development, and subsequent success of the Netdata open-source Agent and Netdata Cloud.</p>Our Approach to Machine Learninghttps://www.netdata.cloud/blog/our-approach-to-machine-learning/Fri, 25 Mar 2022 00:00:00 +0000https://www.netdata.cloud/blog/our-approach-to-machine-learning/<p>There is a lot of buzz in the world of machine learning (ML) and as a layperson it can be hard to keep up with it all. Therefore, we decided to write down some of our thoughts and musings on how <b>we</b> are approaching ML at Netdata.</p> <!--truncate--> <h2 id="our-approach-to-machine-learning-ml">Our Approach to Machine Learning (ML)</h2> <p>We’ll touch on the current state of applied ML in industry in general, and zoom in on ML in the monitoring industry. We’ll discuss how we can leverage “good honest ML” to punch above our weight and add some useful and novel features for our users over the next few years.</p>Engineering Team Best Practices For Cloud Monitoringhttps://www.netdata.cloud/blog/netdata-troubleshooting-show-engineering-team-best-practices-in-working-with-cloud/Wed, 02 Mar 2022 00:00:00 +0000https://www.netdata.cloud/blog/netdata-troubleshooting-show-engineering-team-best-practices-in-working-with-cloud/<!--truncate--> <figure class="wp-block-image size-large"><img src="../wp-archive/uploads/2022/03/group_promo-1200x675.png" alt="" class="wp-image-16147"/></figure> <h2 id="panel-engineering-team-best-practices-in-working-with-cloud">Panel: Engineering Team Best Practices in Working with Cloud</h2> <p><a href="https://youtube.com/playlist?list=PL-P-gAHfL2KMN-LHSmQFjpEwl31rQYvam" target="_blank"><strong>The Netdata Troubleshooting Show</strong></a>| Season 1: Episode 2 | Thursday, March 3rd at 9 am PST (UTC/GMT -8)</p> <p><strong>[<a href="https://youtu.be/zY3DiRJ_DYc" target="_blank">Join Live</a>]</strong>For engineering teams, working in the cloud has never been easier, but also more complex. Enter a new world of remote working with distributed global teams, new tech challenges, new business realities, security, monitoring, and more.</p> <p>Join our dynamic panel of experts live<strong>(</strong><a href="https://youtu.be/zY3DiRJ_DYc" target="_blank"><strong>watch here</strong></a><strong>)</strong>as they talk about engineering team best practices for those working in the cloud in 2022.</p>Netdata Meetup | Install & Monitor From Scratch | Guidehttps://www.netdata.cloud/blog/netdata-meetup-real-world-scenario-on-how-to-install-and-monitor-from-scratch/Wed, 02 Mar 2022 00:00:00 +0000https://www.netdata.cloud/blog/netdata-meetup-real-world-scenario-on-how-to-install-and-monitor-from-scratch/<!--truncate--> <p><img src="../wp-archive/uploads/2022/03/netdata-meetup-1-1200x676.png" alt=""></p> <p>Announcing Netdata Meetups: Virtual How-to Live Show – Join us Friday, March 4th</p> <p><a href="https://youtu.be/lBd0-TFJGAY">Join us live this Friday!</a> We are launching the brand new Netdata Meetups! Join us to learn more about Netdata. This how-to virtual series will help you go deeper with Netdata and as a bonus we will add in tips and tricks for monitoring and troubleshooting. We can’t wait to see you on Friday, March 4th at 9 am PST (GMT -8).</p>Netdata Cloud’s New Architecturehttps://www.netdata.cloud/blog/netdata-clouds-new-architecture/Thu, 10 Feb 2022 00:00:00 +0000https://www.netdata.cloud/blog/netdata-clouds-new-architecture/<!--truncate--> <figure class="wp-block-image size-full"><img class="wp-image-16154" src="../wp-archive/uploads/2022/03/New_arch_notification.jpeg" alt="" /></figure> <p>In version v1.32 of Netdata, we announced a remarkable new update that we are extremely proud of; Netdata Cloud now runs on the most reliable and stable backend that we’ve ever built. </p> <h2 id="migration-to-the-new-netdata-cloud-architecture">Migration to the new Netdata Cloud architecture</h2> <p>To give you the best experience of Netdata Cloud, we started migrating nodes running on the old architecture to the new one. Most users don’t have to take any action on their part. If you need to take action, you will see the pop-up window above in Netdata Cloud.  </p>Meet The Netdata Community: eBPF Hero Thiagohttps://www.netdata.cloud/blog/meet-the-netdata-community-every-company-needs-an-ebpf-superhero-like-thiago/Fri, 04 Feb 2022 00:00:00 +0000https://www.netdata.cloud/blog/meet-the-netdata-community-every-company-needs-an-ebpf-superhero-like-thiago/<!--truncate--> <p><img src="../wp-archive/uploads/2022/03/thiago-2.png" alt=""></p> <p>Our ongoing Meet the community series focuses on global Netdata community members. In this installment, learn about Netdata staff member and Software Engineer Thiago Marques, who is hard at work building an eBPF.plugin.</p> <h3 id="introduce-yourself-what-you-do-and-your-current-job-role-at-netdata">Introduce yourself, what you do, and your current job role at Netdata.</h3> <p>I am Thiago Marques, a C developer who works with the data collector team. My primary responsibility in the company is to develop eBPF.plugin.</p>Meet The Netdata Community: Rupok Chowdhury Protikhttps://www.netdata.cloud/blog/meet-the-netdata-community-rupok-chowdhury-protik-takes-software-engineering-photography-to-new-heights/Tue, 07 Dec 2021 00:00:00 +0000https://www.netdata.cloud/blog/meet-the-netdata-community-rupok-chowdhury-protik-takes-software-engineering-photography-to-new-heights/<!--truncate--> <figure class="wp-block-image size-full"><img src="../wp-archive/uploads/2022/03/Meet-the-community.png" alt="" class="wp-image-16164"/></figure> <p>In our ongoing Meet the community series, we focus on global Netdata community members. In this installment, learn about Software Engineer and photographer Rupok Chowdhury Protik, including how they use Netdata.</p> <p><strong>Introduce yourself, what you do, and your current job role.</strong></p> <p>Hi, I’m Rupok Chowdhury Protik. I’m a PHP Developer with a Master’s degree in Software Engineering. My stack is mainly LAMP/LEMP. I used to work as the Senior Web Application Developer in a multinational company and then later joined Incsub LLC, a WordPress-focused company with people from more than 50 countries. I am currently working in Incsub LLC as a DevOps Support Engineer.</p>Netdata Cloud Show: The Observability Panelhttps://www.netdata.cloud/blog/netdata-cloud-show-the-observability-panel/Tue, 07 Dec 2021 00:00:00 +0000https://www.netdata.cloud/blog/netdata-cloud-show-the-observability-panel/<!--truncate--> <figure class="wp-block-image size-large"><img class="wp-image-16169" src="../wp-archive/uploads/2022/03/Netdata-Cloud-Panel-1200x674.png" alt="" /></figure> <h2 id="in-2022-60-of-security-incidents-will-involve-third-parties-forrester">“In 2022, 60% of security incidents will involve third parties.”<strong>– Forrester</strong></h2> <figure class="wp-block-embed is-type-rich is-provider-embed-handler wp-block-embed-embed-handler wp-embed-aspect-16-9 wp-has-aspect-ratio"> <div class="wp-block-embed__wrapper">https://www.youtube.com/embed/kILpPCRlVD0</div> </figure> <p><strong>This Thursday, December 9th at 1 PM EST (UTC-5)</strong>Join us live this Thursday for the first-ever Netdata Cloud Show, where our all-star panel will be discussing the latest trends around observability. </p> <p>This will be broadcast live on Netdata <a href="https://youtu.be/kILpPCRlVD0">YouTube</a>, <a href="https://twitter.com/linuxnetdata">Twitter</a>, <a href="https://www.facebook.com/linuxnetdata/">Facebook</a>, and <a href="https://discord.gg/kUk3nCmbtx">Discord</a>.</p> <p><strong>Observability Panel:</strong></p> <ul> <li><strong>Boris Zaikin</strong>, Senior Software and Cloud Architect at Nordcloud. <a href="https://twitter.com/boriszzn">@boriszzn</a></li> <li><strong>Samir Behara</strong>, Platform Architect at EBSCO Industries, Inc. <a href="https://twitter.com/samirbehara">@samirbehara</a></li> <li><strong>Ralph Meijer</strong>, VP of Technology at Netdata. <a href="https://twitter.com/ralphm">@ralphm</a></li> </ul> <p><strong>Topics Covered Include:</strong></p>All-new Netdata Cloud Charts 2.0https://www.netdata.cloud/blog/all-new-netdata-cloud-charts-2-0/Tue, 30 Nov 2021 00:00:00 +0000https://www.netdata.cloud/blog/all-new-netdata-cloud-charts-2-0/<!--truncate--> <figure class="wp-block-image size-large"><img src="../wp-archive/uploads/2022/03/Netdata-Charts-2.0-1200x704.png" alt="" class="wp-image-16212"/></figure> <p>Netdata excels in collecting, storing, and organizing metrics in out-of-the-box dashboards for powerful troubleshooting. We are now doubling down on this by transforming data into even more effective visualizations, helping you make the most sense out of all your metrics for increased observability.</p> <p>The new Netdata Charts provide a ton of useful information and we invite you to further explore our new charts from a design and development perspective. As always, it’s our goal to be as open and transparent as possible with our users on all things Netdata, including the ins and outs of how Netdata is built, why we make certain design decisions (driven by you of course!), and where we are heading as we continue to grow.</p>Meet The Netdata Community | Bastien, SysAdmin & Dog Loverhttps://www.netdata.cloud/blog/meet-the-netdata-community-learn-about-bastien-a-system-and-network-admin-who-loves-dogs/Tue, 30 Nov 2021 00:00:00 +0000https://www.netdata.cloud/blog/meet-the-netdata-community-learn-about-bastien-a-system-and-network-admin-who-loves-dogs/<!--truncate--> <figure class="wp-block-image size-full"><img src="../wp-archive/uploads/2022/03/Screen-Shot-2021-11-30-at-3.10.06-PM.png" alt="" class="wp-image-16223"/></figure> <p><strong>Tell people about yourself and what you do.</strong></p> <p>My name is Bastien. I’m 28, a System and Network Admin, currently SRE in a team of two for my company. We’re working with AWS and Kubernetes to host our web apps.</p> <p><strong>How are you using Netdata and what do you like so far?</strong></p> <p>I’m currently in the process of moving to Netdata to monitor our nine Kubernetes clusters and some standalone VMs. What I particularly love about Netdata is the simplicity of installation and configuration and the number of perfect default metrics and graphs.</p>How to extend the Geth collectorhttps://www.netdata.cloud/blog/how-to-extend-the-geth-collector/Mon, 13 Sep 2021 00:00:00 +0000https://www.netdata.cloud/blog/how-to-extend-the-geth-collector/<!--truncate--> <figure class="wp-block-image size-large"><img src="../wp-archive/uploads/2022/03/Geth-collector-diagram-1-1200x796.png" alt="" class="wp-image-16282"/></figure> <p>This is the the last of a 2-part blog post series regarding Netdata and Geth. If you missed the first, be sure to check it out <a href="https://hackmd.io/J1x1WA-bR0a8gQeAmVdLFw" target="_blank" rel="noreferrer noopener">here</a>.</p> <p>Geth is short for Go-Ethereum and is the official implementation of the Ethereum Client in Go. Currently it’s one of the most widely used implementations and a core piece of infrastructure for the Ethereum ecosystem.</p> <p>With this proof of concept I wanted to showcase how easy it really is to gather data from any Prometheus endpoint and visualize them in Netdata. This has the added benefit of leveraging all the other features of Netdata, namely it’s per-second data collection, automatic deployment and configuration and superb system monitoring.</p>How to monitor the Geth node in under 5 minuteshttps://www.netdata.cloud/blog/how-to-monitor-the-geth-node-in-under-5-minutes/Mon, 13 Sep 2021 00:00:00 +0000https://www.netdata.cloud/blog/how-to-monitor-the-geth-node-in-under-5-minutes/<!--truncate--> <figure class="wp-block-image size-large"><img src="../wp-archive/uploads/2022/03/How-Geth-affect-the-CPU-charts-1200x629.png" alt="" class="wp-image-16229"/></figure> <p>This piece is a blog post version of a workshop I gave at <a href="https://ethcc.io/" target="_blank" rel="noreferrer noopener">EthCC</a> about monitoring an Ethereum Node using Netdata.</p> <p><strong>Disclaimer:</strong> Although we use Netdata, this guide is generic. We talk about metrics that can be surfaced by many other tools, such as Prometheus/Grafana or Datadog.</p> <p>The contents are as follows:</p> <ul><li class="">Introduction to Ethereum Nodes</li><li class="">What is Netdata</li><li class="">How to monitor a system that runs go-ethereum (Geth)</li><li class="">How to monitor go-ethereum (Geth)</li></ul> <h2 id="ethereum-nodes">Ethereum Nodes</h2> <p>Running a node is no small feat, as it requires increasingly more and more resources to store the state of the blockchain and quickly process new transactions.</p>Root cause analysis using Metric Correlationshttps://www.netdata.cloud/blog/root-cause-analysis-using-metric-correlations/Fri, 03 Sep 2021 00:00:00 +0000https://www.netdata.cloud/blog/root-cause-analysis-using-metric-correlations/<!--truncate--> <figure class="wp-block-image size-large"><img src="../wp-archive/uploads/2022/03/Screen-Shot-2021-09-03-at-1.43.32-PM-1-1200x608.png" alt="" class="wp-image-16297"/></figure> <p>As complexity of systems and applications continue to evolve and change, the number of metrics that need to be monitored grows in parallel. Whether you’re on a DevOps team, an SRE, or a developer building the code yourself, many of these components may be fragmented across your infrastructure, making it increasingly difficult to identify the root cause when experiencing downtime or abnormal behavior. To help solve this challenge, we built the <a href="https://learn.netdata.cloud/docs/cloud/insights/metric-correlations">Metric Correlations</a> feature – an automated analysis tool that evaluates all your metrics to identify which have changed the most within a given period of interest.</p>How To Monitor Disks & Filesystems With eBPFhttps://www.netdata.cloud/blog/how-to-monitor-your-disks-and-filesystems-now-also-with-ebpf/Mon, 16 Aug 2021 00:00:00 +0000https://www.netdata.cloud/blog/how-to-monitor-your-disks-and-filesystems-now-also-with-ebpf/<!--truncate--> <div class="et_pb_module et_pb_text et_pb_text_0 et_pb_text_align_left et_pb_bg_layout_light"> <div class="et_pb_text_inner"> <img class="alignnone size-medium wp-image-16371" src="../wp-archive/uploads/2021/08/eBPF-monitoring-1536x932-1-600x364.png" alt="" width="600" height="364" /> <h2 id="introduction-to-ebpf">Introduction to eBPF</h2> </div> </div> <div class="et_pb_module et_pb_text et_pb_text_1 et_pb_text_align_left et_pb_bg_layout_light"> <div class="et_pb_text_inner"> <p>Current IT monitoring software lacks the necessary metrics for minimizing downtime for systems and applications. Most provide system and application metrics but there is much more than this required for properly monitoring your infrastructure. With <a title="eBPF" href="https://ebpf.io/" target="_blank" rel="noopener">eBPF</a> there is a technological advancement that allows monitoring software to provide rich information from the Linux kernel and present it. eBPF monitoring, specifically, provides a better understanding of what exactly is occurring on internal systems, which helps to identify where performance improvements can be made.</p>Netdata Is Launching Its Discord Serverhttps://www.netdata.cloud/blog/netdata-is-launching-its-discord-server/Tue, 22 Jun 2021 00:00:00 +0000https://www.netdata.cloud/blog/netdata-is-launching-its-discord-server/<!--truncate--> <p>It’s been a long time since our last community update, rest assured that we have been hard at work here at Netdata.</p> <p>Community building is hard, especially when you have such a venerable community like the one here at Netdata, where hundreds of contributors have contributed to creating one of the best monitoring solutions that exist.</p> <p>Last year we started to concentrate working on consolidating the community by integrating the various platforms where people come together to talk about Netdata. In that effort, we restarted our community forums in November, reworking the categories and creating a support channel, where community members help each other.</p>Netdata v1.31.0https://www.netdata.cloud/blog/netdata-v1-31/Wed, 19 May 2021 00:00:00 +0000https://www.netdata.cloud/blog/netdata-v1-31/<!--truncate--> <img class="alignnone size-medium wp-image-16402" src="../wp-archive/uploads/2021/05/v1.31.01-1-600x375.png" alt="" width="600" height="375" /> <p>Give a warm welcome to Netdata v1.31.0, which features:</p> <ul> <li aria-level="1"><strong>Re-packaged and redesigned dashboard</strong>: A more informational and feature-rich “frame” for your monitoring and troubleshooting sessions.</li> <li aria-level="1"><strong>eBPF expands into the directory cache</strong>: Monitor whether your services or applications are properly using Linux’s memory management for the best performance and minimal disk I/O.</li> <li aria-level="1"><strong>Machine learning-powered collectors</strong>: Detect anomalies using only your own data and minimal resource utilization on your monitored nodes.</li> <li aria-level="1"><strong>An improved Netdata learning experience</strong>: A timeline of new content, refreshed visuals, and a newly-open sourced repository.</li> </ul> <h2 id="h_1876248811621353710666">Re-packaged and redesigned dashboard</h2> We re-packaged and redesigned portions of the dashboard to improve the overall experience. Part of this effort is better handling of dashboard code during installation—anyone using third-party packages (such as the Netdata Homebrew formula) will start seeing new features and the new designs starting today. <p>For those who aren’t using third-party packages (thank you!), your installation process will still get a little bit faster.</p>Kubernetes monitoring and troubleshooting made simplehttps://www.netdata.cloud/blog/kubernetes-monitoring-troubleshooting/Wed, 05 May 2021 00:00:00 +0000https://www.netdata.cloud/blog/kubernetes-monitoring-troubleshooting/<!--truncate--> <img class="alignnone wp-image-16419 size-large" src="../wp-archive/uploads/2022/03/kubernetes-monitoring-troubleshooting-1200x828.png" alt="" width="1200" height="828" /> <p>Infrastructure monitoring was difficult enough when entire businesses ran off a few <a href="https://www.netdata.cloud/academy/bare-metal-server/">bare metal servers</a> in a dusty, forgotten closet. Other IT infrastructure monitoring tools fell short, unable to provide complete and granular-enough metrics in real time, even when we were only dealing with a handful of systems responsible for running every part of the application stack. They were hard to configure, especially for the non-gurus out there, and didn’t provide the high-resolution metrics the gurus needed to make data-driven troubleshooting decisions.</p>Netdata 1.30.0https://www.netdata.cloud/blog/netdata-1-30-0/Thu, 01 Apr 2021 00:00:00 +0000https://www.netdata.cloud/blog/netdata-1-30-0/<!--truncate--> <img class="alignnone size-medium wp-image-16427" src="../wp-archive/uploads/2022/03/v1.30.0-600x338.png" alt="" width="600" height="338" /> <p>We’re excited to introduce Netdata 1.30.0, which features:</p> <ul> <li><a href="https://staging-www.netdata.cloud/blog/release-1-30-0/#h_13754275791617303933429" target="_blank" rel="noopener"><strong>ACLK-NG</strong></a>: A new custom library for streaming metrics data on demand, written entirely in-house, that’s 4x faster than libmosquitto/libwebsockets.</li> <li><a href="https://staging-www.netdata.cloud/blog/release-1-30-0/#h_51169176821617303905806"><strong>Opt-in product telemetry with PostHog</strong></a><strong>:</strong> Goodbye, Google Analytics. Hello, self-hosted instance of PostHog.</li> <li><strong><a href="https://staging-www.netdata.cloud/blog/release-1-30-0/#h_612104678161617303939018">Deeper Linux kernel monitoring with eBPF</a></strong>: Expanding our reach into the Linux kernel with page cache and synchronization syscall monitoring.</li> <li><strong><a href="https://staging-www.netdata.cloud/blog/release-1-30-0/#h_327502801221617303950492">Smarter preconfigured alarms</a></strong>: Better (and less noisy) defaults, better information.</li> <li><strong><a href="https://staging-www.netdata.cloud/blog/release-1-30-0/#h_282794194271617303959644">Developer environment</a></strong>: Contribute to Netdata via a Docker image and VSCode integration.</li> <li><strong><a href="https://staging-www.netdata.cloud/blog/release-1-30-0/#h_740997254311617303965795">Documentation improvements &amp; tutorials</a></strong>: Better standards for editing files and restarting Netdata, plus brand-new tutorials.</li> </ul> <h2 id="h_13754275791617303933429">ACLK-NG</h2> The ACLK-NG is a new, faster method of securely connecting a node running Netdata to Netdata Cloud. In our internal testing, it’s 4x faster than our previous implementation, which uses <a href="https://github.com/netdata/mosquitto" target="_blank" rel="noopener">libmosquitto</a> and <a href="https://github.com/warmcat/libwebsockets" target="_blank" rel="noopener">libwebsockets</a>. <table id="tablepress-10" class="tablepress tablepress-id-10 tablepress-responsive" > <thead> <tr class="row-1 odd"> <th class="column-2" colspan="2">ACLK-NG</th> <th class="column-4" colspan="2">ACLK Legacy</th> </tr> </thead> <tbody class="row-hover"> <tr class="row-2 even"> <td class="column-1"></td> <td class="column-2">time (s)</td> <td class="column-3">MB/s</td> <td class="column-4">time (s)</td> <td class="column-5">MB/s</td> </tr> <tr class="row-3 odd"> <td class="column-1">Run 1</td> <td class="column-2">1.30</td> <td class="column-3">76.92</td> <td class="column-4">5.30</td> <td class="column-5">18.87</td> </tr> <tr class="row-4 even"> <td class="column-1">Run 2</td> <td class="column-2">1.31</td> <td class="column-3">76.34</td> <td class="column-4">5.29</td> <td class="column-5">18.90</td> </tr> <tr class="row-5 odd"> <td class="column-1">Run 3</td> <td class="column-2">1.38</td> <td class="column-3">72.46</td> <td class="column-4">5.27</td> <td class="column-5">18.98</td> </tr> <tr class="row-6 even"> <td class="column-1">Run 4</td> <td class="column-2">1.27</td> <td class="column-3">78.74</td> <td class="column-4">5.40</td> <td class="column-5">18.52</td> </tr> <tr class="row-7 odd"> <td class="column-1">Run 5</td> <td class="column-2">1.24</td> <td class="column-3">80.65</td> <td class="column-4">5.46</td> <td class="column-5">18.32</td> </tr> <tr class="row-8 even"> <td class="column-1"></td> <td class="column-2"><strong>1.30</strong></td> <td class="column-3"><strong>77.02</strong></td> <td class="column-4"><strong>5.34</strong></td> <td class="column-5"><strong>18.72</strong></td> </tr> </tbody> </table> With ACLK-NG enabled, you’ll get a snappier experience in Netdata Cloud, as there will be far less latency between requests for metrics and the subsequent response from individual nodes. <p>To enable ACLK-NG right now, update your nodes with the <code>&ndash;aclk-ng</code> option:</p>Container deployment showdown: Docker or Kubernetes?https://www.netdata.cloud/blog/container-deployment-showdown-docker-or-kubernetes/Wed, 24 Mar 2021 00:00:00 +0000https://www.netdata.cloud/blog/container-deployment-showdown-docker-or-kubernetes/<!--truncate--> <div class="et_pb_module et_pb_text et_pb_text_0 et_pb_text_align_left et_pb_bg_layout_light"> <div class="et_pb_text_inner"> <img class="alignnone wp-image-16433 size-large" src="../wp-archive/uploads/2022/03/Kubernetes_vs_Docker-1200x828.png" alt="" width="1200" height="828" /> <p>Monitoring the current state and performance of applications is critical for IT Ops and DevOps teams alike. Understanding the health of an application is one of the most effective ways of anticipating potential bottlenecks or slowdowns, yet it’s one of the largest challenges faced by many organizations that build and deploy software. This is largely due to applications’ distributed and diversified nature. A single outage has the potential to interrupt entire processes that, at times, can interfere with business as a whole and result in a negative effect on the bottom line.</p>5 DevOps best practices to reinforce with monitoring toolshttps://www.netdata.cloud/blog/devops-best-practices-monitoring-tools/Thu, 18 Feb 2021 00:00:00 +0000https://www.netdata.cloud/blog/devops-best-practices-monitoring-tools/<!--truncate--> <img class="alignnone size-medium wp-image-16441" src="../wp-archive/uploads/2022/03/devops-best-practices-monitoring-tools-v2-600x414.png" alt="" width="600" height="414" /> <p>As part of a modern software development team, you’re asked to do a lot. You’re supposed to build faster, release more frequently, crush bugs, and integrate testing suites along the way. You’re supposed to implement and practice a strong DevOps culture, <a href="https://github.com/upgundecha/howtheysre" target="_blank" rel="noopener noreferrer">read entire novels</a> about SRE best practices, go <a href="https://en.wikipedia.org/wiki/Agile_software_development" target="_blank" rel="noopener noreferrer">agile</a>, or add a bunch of Scrum ceremonies to everyone’s calendar. Every week, the industry recommends that you “<a href="https://devops.com/devops-shift-left-avoid-failure/" target="_blank" rel="noopener noreferrer">shift-left</a>” another part of the <a href="https://staging-www.netdata.cloud/blog/agile-static-analysis/" target="_blank" rel="noopener noreferrer">DevOps pipeline</a>, to the point where you’re supposed to handle everything from unit testing to production deployment optimization from day one.</p>Introduction to StatsDhttps://www.netdata.cloud/blog/introduction-to-statsd/Wed, 03 Feb 2021 00:00:00 +0000https://www.netdata.cloud/blog/introduction-to-statsd/<!--truncate--> <img class="alignnone size-medium wp-image-16449" src="../wp-archive/uploads/2022/03/StatsD-600x414.png" alt="" width="600" height="414" /> <p>StatsD is an industry-standard technology stack for monitoring applications and instrumenting any piece of software to deliver custom metrics. The StatsD architecture is based on delivering the metrics via UDP packets from any application to a central statsD server. Although the original StatsD server was written in Node.js, there are many implementations today, with Netdata being one of them.</p> <p>StatsD makes it easier for you to instrument your applications, delivering value around three main pillars: open-source, control, and modularity. That’s a real windfall for full-stack developers who need to code quickly, troubleshoot application issues on the fly, and often don’t have the necessary background knowledge to use complex monitoring platforms.</p>Actionable Alerts With Fewer False Positiveshttps://www.netdata.cloud/blog/actionable-intelligent-alerts/Thu, 21 Jan 2021 00:00:00 +0000https://www.netdata.cloud/blog/actionable-intelligent-alerts/<!--truncate--> <img class="alignnone size-medium wp-image-16460" src="../wp-archive/uploads/2022/03/intelligent-alarms-600x413.png" alt="" width="600" height="413" /> <p>Think about any sport or competitive activity, whether that’s football or a spelling bee. They always feature at least one person who acts as a moderator, referee, or judge. With their domain expertise, this person watches everyone’s behavior and constantly compares that against a set of rules. If someone crosses that threshold, they blow a whistle or throw up a flag. They are, in effect, saying that things have gone from <strong>OK</strong> to <strong>not OK</strong>.</p>Four key metrics for responding to IT incidents and failureshttps://www.netdata.cloud/blog/four-key-metrics-for-responding-to-it-incidents-and-failures/Thu, 07 Jan 2021 00:00:00 +0000https://www.netdata.cloud/blog/four-key-metrics-for-responding-to-it-incidents-and-failures/<!--truncate--> <img class="alignnone wp-image-16474 size-large" src="../wp-archive/uploads/2021/01/DevOps-Metrics-1200x862.png" alt="" width="1200" height="862" /> <div class="et_pb_module et_pb_text et_pb_text_0 et_pb_text_align_left et_pb_bg_layout_light"> <div class="et_pb_text_inner"> <p>If you’re a veteran in this space, you probably understand the many incident response metrics and concepts, along with the many (at times exasperating) acronyms. For those new to the space, or even those with years of experience, the <a title="terminology" href="https://en.wikipedia.org/wiki/List_of_computing_and_IT_abbreviations" target="_blank" rel="noopener noreferrer">terminology</a> is often overwhelming.</p> <p>If you’re one of those people who’s struggling to navigate through the world of DevOps metrics, we’ve created this article for you. In this post, we’ll cover four main incident response metrics: MTTA, MTTR, MTBF, and MTTF. Learn what these acronyms mean, how you can use them, and how you can tie these KPIs into your Netdata experience.</p>Netdata Year in Review 2020https://www.netdata.cloud/blog/netdata-year-in-review-2020/Fri, 18 Dec 2020 00:00:00 +0000https://www.netdata.cloud/blog/netdata-year-in-review-2020/<!--truncate--> <img class="alignnone size-medium wp-image-16482" src="../wp-archive/uploads/2022/03/Roadmap-Header-600x322.png" alt="" width="600" height="322" /> <p>Looking back at the unprecedented challenges we faced together in 2020, we’d like to extend our thanks to the community of people who have continued to work towards Netdata’s mission of simplifying monitoring and troubleshooting for everyone. Let’s review some of this year’s highlights.</p> <table> <tbody> <tr> <td width="50%"> <table> <tbody> <tr> <td> <h3>Community</h3> </td> <td>More than <a title="https://github.com/netdata/netdata/graphs/contributors" href="https://github.com/netdata/netdata/graphs/contributors" target="_blank" rel="noopener noreferrer">400 contributors</a> have helped us grow.</td> </tr> <tr> <td>Nearly 50,000 GitHub <a title="stargazers" href="https://github.com/netdata/netdata" target="_blank" rel="noopener noreferrer">stargazers</a> follow our progress.</td> <td>Our community on <a title="GitHub" href="https://github.com/netdata/netdata/" target="_blank" rel="noopener noreferrer">GitHub</a> and our <a title="forums" href="https://community.netdata.cloud/" target="_blank" rel="noopener noreferrer">forums</a> has grown to 4,000 strong.</td> </tr> </tbody> </table> </td> <td width="50%"><img class="wp-image-16480 aligncenter" src="../wp-archive/uploads/2022/03/community.png" alt="" width="227" height="225" /></td> </tr> </tbody> </table> &nbsp; <table> <tbody> <tr> <td width="50%"><img class="size-full wp-image-16492 aligncenter" src="../wp-archive/uploads/2020/12/stargazers.png" alt="" width="225" height="226" /></td> <td width="50%"> <table> <tbody> <tr> <td> <h3>Netdata Cloud</h3> </td> <td>Launched in May, now with more than 25,000 users <a title="registered" href="https://app.netdata.cloud/" target="_blank" rel="noopener noreferrer">registered</a>.</td> </tr> <tr> <td>Continuous delivery of new features included custom dashboards, Metric Correlations, overview page, and centralized alarm notifications.</td> </tr> </tbody> </table> </td> </tr> </tbody> </table> <table> <tbody> <tr> <td width="50%"> <table> <tbody> <tr> <td> <h3>Netdata Agent</h3> </td> <td>9 dot <a title="releases" href="https://github.com/netdata/netdata/releases" target="_blank" rel="noopener noreferrer">releases</a>, with support for eBPF, Prometheus metrics, &amp; k8s service discovery.</td> </tr> <tr> <td>More than 300 bug fixes, nearly 1,500 closed <a title="issues" href="https://github.com/netdata/netdata/issues" target="_blank" rel="noopener noreferrer">issues</a>, and almost 3,200 commits.</td> <td>Nearly 400 new features or <a title="improvements" href="https://github.com/netdata/netdata/" target="_blank" rel="noopener noreferrer">improvements</a>.</td> </tr> </tbody> </table> </td> <td width="50%"><img class="wp-image-16499 size-full aligncenter" src="../wp-archive/uploads/2020/12/Github-1.png" alt="" width="256" height="256" /></td> </tr> </tbody> </table> &nbsp; <table> <tbody> <tr> <td width="50%"><img class="wp-image-16501 size-full aligncenter" src="../wp-archive/uploads/2020/12/funding-2.png" alt="" width="225" height="225" /></td> <td width="50%"> <table> <tbody> <tr> <td> <h3>Company</h3> </td> <td><a title="Raised" href="https://staging-www.netdata.cloud/news/netdata-extends-series-a-funding/">Raised</a> $14.2M, extending the total raised to $31M.</td> </tr> <tr> <td>Recognized in <a title="Forbes Cloud 100 Rising Stars 2020" href="https://staging-www.netdata.cloud/blog/forbes-cloud-100-rising-stars-2020/">Forbes Cloud 100 Rising Stars 2020</a>, <a title="2020 Stratus Awards" href="https://staging-www.netdata.cloud/news/">2020 Stratus Awards</a> as Cloud Disruptor.</td> </tr> </tbody> </table> </td> </tr> </tbody> </table> &nbsp; <p> </p>Centralize Infrastructure With Alarm Notificationshttps://www.netdata.cloud/blog/cloud-alarm-notifications/Thu, 17 Dec 2020 00:00:00 +0000https://www.netdata.cloud/blog/cloud-alarm-notifications/<!--truncate--> <div class="et_pb_module et_pb_text et_pb_text_0 et_pb_text_align_left et_pb_bg_layout_light"> <div class="et_pb_text_inner"> <img class="alignnone wp-image-16509 size-large" src="../wp-archive/uploads/2020/12/Central-Alarm-Notifications-1200x828.png" alt="" width="1200" height="828" /> <p>Netdata is architected on every level, across both the open-source Netdata Agent and Netdata Cloud, to help you own every layer of your monitoring experience. With this design, all metrics data collected by the Netdata Agent stays distributed on your node, but you also leverage Netdata Cloud’s dashboards and multi-node visualizations to view the health and performance of an entire infrastructure from a single application.</p>Community Update: Discourse, Community Effortshttps://www.netdata.cloud/blog/community-update-discourse/Wed, 02 Dec 2020 00:00:00 +0000https://www.netdata.cloud/blog/community-update-discourse/<!--truncate--> <img class="alignnone wp-image-16522 size-full" src="../wp-archive/uploads/2022/03/Community-update_-Discourse-community-efforts.png" alt="" width="681" height="470" /> <p>Open source and community have always been in the DNA of Netdata, with the Agent starting as a very popular open-source project. Since then, a lot has changed, with Netdata maturing into a company, and the Netdata Agent finding its place as an open-source project in a wider offering that redesigns the monitoring experience from the ground up.</p> <p>While we had a very active <a href="https://github.com/netdata/netdata/" target="_blank" rel="noopener noreferrer">GitHub repository</a>, with the majority of the Netdata Agent’s original team actively moderating the discussions and talking with users, we started a more concentrated initiative to manage our community in spring 2020. We launched our first forum using <a href="https://nodebb.org/" target="_blank" rel="noopener noreferrer">NodeBB</a>, a great open-source project, and the community grew substantially, outgrowing the forum software. At the same time, we were able to identify areas of friction in the community journey. Removing that friction became a centerpiece of our strategy during Q3 2020.</p>StackPulse: Automated Incident Remediation Workflowhttps://www.netdata.cloud/blog/netdata-stackpulse-remediation/Wed, 02 Dec 2020 00:00:00 +0000https://www.netdata.cloud/blog/netdata-stackpulse-remediation/<!--truncate--> <blockquote> <p><strong>Historical note:</strong> StackPulse later became Torq. <a href="https://torq.io/">Torq</a> now provides a security-operations platform, not the reliability product described in this 2020 article.</p> </blockquote> <img class="alignnone size-large wp-image-16535" src="../wp-archive/uploads/2022/03/netdata-stackpulse-1200x826.png" alt="" width="1200" height="826" /> <p>Teams of all types use Netdata to monitor the health of their nodes with preconfigured alarms and real-time interactive visualizations, and when incidents happen, they troubleshoot issues with thousands of per-second metrics on <a href="https://staging-www.netdata.cloud/cloud/" target="_blank" rel="noopener noreferrer">Netdata Cloud</a>. But based on the complexity of the team and the infrastructure they monitor, some parts of their <a href="https://staging-www.netdata.cloud/incident-management/" target="_blank" rel="noopener noreferrer">incident management</a>, such as pre-planned communication and escalation processes, or even automated remediation, need to happen outside of the Netdata ecosystem.</p>What is DevOps?https://www.netdata.cloud/blog/what-is-devops/Thu, 19 Nov 2020 00:00:00 +0000https://www.netdata.cloud/blog/what-is-devops/<!--truncate--> <img class="alignnone size-full wp-image-16550" src="../wp-archive/uploads/2022/03/what-is-devops.png" alt="" width="1024" height="600" /> <p>In software development, it’s important to have a team dedicated to ensuring all systems and applications maintain maximum performance and uptime. Establishing processes that limit system and application slowdowns and outages while expediting the product release process is often done through a developer operations team, also known as <em>dev ops</em> or <em>DevOps</em>.</p> <p>DevOps teams are responsible for improving communication and collaboration across engineering teams to increase an organization’s ability to efficiently deliver products and services that serve the end-user. In this post, we’ll describe the different elements of DevOps, including what DevOps is, how it works, and how Netdata helps DevOps teams succeed.</p>Community Repository: Consul, Ansible & ML Recipeshttps://www.netdata.cloud/blog/welcome-to-netdatas-community-repository-consul-ansible-ml/Wed, 11 Nov 2020 00:00:00 +0000https://www.netdata.cloud/blog/welcome-to-netdatas-community-repository-consul-ansible-ml/<!--truncate--> <img class="alignnone size-large wp-image-16555" src="../wp-archive/uploads/2022/03/netdata-community-repository-1200x825.png" alt="" width="1200" height="825" /> <p>On our journey to democratize monitoring, we are proud to have open source at the core of both our products and our company values. What started as a project out of frustration for lack of existing alternatives (see <a href="https://www.rexfeng.com/blog/2016/01/anger-driven-development/" target="_blank" rel="noopener noreferrer">anger-driven development</a>), quickly became one of the most starred open-source projects on all of GitHub.</p> <p>Fast-forward a couple of years later, and the Netdata Agent, our open-source monitoring agent, is maturing as the best single-node monitoring experience, offering unparalleled efficiency and thousands of metrics, per-second. At the same time, we have gathered a considerable community on our GitHub repository and new forums.</p>How Netdata gets you from 0 to monitoring in minuteshttps://www.netdata.cloud/blog/how-netdata-gets-you-from-0-to-monitoring-in-minutes/Wed, 11 Nov 2020 00:00:00 +0000https://www.netdata.cloud/blog/how-netdata-gets-you-from-0-to-monitoring-in-minutes/<!--truncate--> <img class="alignnone size-large wp-image-16562" src="../wp-archive/uploads/2022/03/0conf-1200x826.png" alt="" width="1200" height="826" /> <p>Netdata is zero-configuration monitoring. It’s a principle that we’ve stood behind since the project’s beginning, when it was only our CEO Costa trying to solve a <a href="https://staging-www.netdata.cloud/blog/why-netdata-is-free/">“painful, real-world problem,”</a> and it’s one we stand by today. Our insistence on zero-configuration guides every product decision we make, every grooming process, and every React component our frontend teams design.</p> <p>In fact, zero-configuration is the exact reason why Netdata’s dashboard is <a href="https://staging-www.netdata.cloud/blog/netdata-agent-dashboard/">open and accessible by default</a>. It’s how Netdata gets you from 0 monitoring to thousands of metrics, collected every second and visualized in real time, in a matter of minutes.</p>Netdata’s dashboard: open by default and secure by designhttps://www.netdata.cloud/blog/netdata-agent-dashboard/Wed, 28 Oct 2020 00:00:00 +0000https://www.netdata.cloud/blog/netdata-agent-dashboard/<!--truncate--> <img class="alignnone size-large wp-image-16569" src="../wp-archive/uploads/2022/03/netdata-dashboard-open-secure-min-1200x826.png" alt="" width="1200" height="826" /> <p>Let’s talk through a scenario: You have a Linux-based VM running on DigitalOcean (aka a Droplet), and you install Netdata on it using our <a href="https://learn.netdata.cloud/docs/netdata-agent/installation" target="_blank" rel="noopener noreferrer">recommended kickstart script</a>. As the installation process winds down, the Droplet starts up the Netdata Agent’s web server and serves the local Agent web dashboard on port 19999. You navigate to the dashboard using your browser of choice, check out per-second metrics updating in real time in a few of the hundreds of preconfigured visualizations, then realize…</p>Real-Time Infrastructure Monitoring Now In Netdata Cloudhttps://www.netdata.cloud/blog/bringing-rich-and-real-time-infrastructure-monitoring-to-netdata-cloud/Thu, 22 Oct 2020 00:00:00 +0000https://www.netdata.cloud/blog/bringing-rich-and-real-time-infrastructure-monitoring-to-netdata-cloud/<!--truncate--> <img class="alignnone size-large wp-image-16578" src="../wp-archive/uploads/2022/03/Correlation_charts-1200x830.png" alt="" width="1200" height="830" /> <p>The Netdata Agent is well-equipped to solve monitoring and troubleshooting challenges for single nodes. We love that the Agent is so valuable to our users, but Netdata Cloud is designed for infrastructure monitoring. That’s why we’re working so hard to offer even more capabilities and help users monitor and troubleshoot infrastructures of all sizes, entirely for free!</p> <p>With the new Cloud Overview, you get every real-time chart and metric you need to understand the status of your infrastructure, explore, and troubleshoot, in a single view. We designed the Overview on one existing and beloved feature and another entirely new one that we’re very excited to launch for the first time.</p>The reality of Netdata’s long-term metrics storage databasehttps://www.netdata.cloud/blog/the-reality-of-netdatas-long-term-metrics-storage-database/Mon, 12 Oct 2020 00:00:00 +0000https://www.netdata.cloud/blog/the-reality-of-netdatas-long-term-metrics-storage-database/<!--truncate--> <p>The perception that Netdata is only capable of short-term metrics storage is a myth. It’s a pervasive myth we still see in blog posts and through community engagement, despite it being false for more than a year.</p> <p> </p> <p>However, like all myths, this one on metrics storage began with a kernel of truth. When Netdata first flourished as an <a title="open-source project" href="https://github.com/netdata/netdata" target="_blank" rel="noopener noreferrer">open-source project</a> in 2017 and 2018, the default metrics database was RAM-only. You could configure this database’s size, but for many users, that size was limited by the amount of RAM they were willing to allocate for metrics storage. We also kept the default value low to ensure Netdata worked efficiently on all hardware and a variety of operating systems.</p>Software Extensibility Is Key To Adoptionhttps://www.netdata.cloud/blog/software-extensibility-is-key-to-adoption/Fri, 25 Sep 2020 00:00:00 +0000https://www.netdata.cloud/blog/software-extensibility-is-key-to-adoption/<!--truncate--> <img class="alignnone size-full wp-image-16613" src="../wp-archive/uploads/2022/03/Software-Extensibility-Blog-Post.png" alt="" width="969" height="638" /> <p>As with most commercial products, software today is mass produced for reasons of simple economics. But making the same software work for as many people as possible while also meeting the unique requirements different people and organizations have is a challenging task.</p> <p>The strategies used today to provide extensibility at cost and at the level required by various enterprises are very similar to the ones used in the 80s and 90s, when PCs first took off and captured an enormous amount of the home computing market, and when open source software started gaining popularity.</p>Investing in Netdata: a growth storyhttps://www.netdata.cloud/blog/investing-in-netdata-a-growth-story/Tue, 22 Sep 2020 00:00:00 +0000https://www.netdata.cloud/blog/investing-in-netdata-a-growth-story/<!--truncate--> <img class="alignnone size-large wp-image-16618" src="../wp-archive/uploads/2022/03/Series-A-funding-extension-1200x571.png" alt="" width="1200" height="571" /> <p>I’m excited to announce an <a title="extension to Netdata’s series A funding" href="https://staging-www.netdata.cloud/news/netdata-extends-series-a-funding/" target="_blank" rel="noopener noreferrer">extension to Netdata’s series A funding </a>in the amount of $14.2M, bringing the total amount of funding to $31M. We’re thrilled to share the news; the additional funding will help us continue building the future of health monitoring and performance troubleshooting. In case you missed it, our mission is to <a title="redefine infrastructure monitoring" href="https://staging-www.netdata.cloud/blog/redefining-monitoring-netdata/" target="_blank" rel="noopener noreferrer">redefine infrastructure monitoring</a>. Our unique approach to building the right solution with and for the community is no easy task.</p>Metric Correlations: Detect Patterns & Anomalieshttps://www.netdata.cloud/blog/netdata-cloud-metric-correlations/Wed, 16 Sep 2020 00:00:00 +0000https://www.netdata.cloud/blog/netdata-cloud-metric-correlations/<!--truncate--> <img class="alignnone size-large wp-image-16623" src="../wp-archive/uploads/2022/03/Cloud-Correlations@2x-1200x826.png" alt="" width="1200" height="826" /> <p>Today, we are excited to launch our first Netdata Cloud Insights feature, Metric Correlations, developed for discovering underlying issues more quickly and identifying the root cause more efficiently. Read on to learn more about our approach to developing this new feature, how it works, and the many benefits you’ll find incorporating this into your team’s troubleshooting workflow.</p> <h2>Some background</h2> Let’s start with a bit of a disclaimer. It seems machine learning (ML) (or “Artificial Intelligence,” if you are looking for more LinkedIn likes) has gone mainstream in the last few years, and we are probably by now somewhere near the “Peak of Inflated Expectations” on the <a title="hype cycle" href="https://en.wikipedia.org/wiki/Hype_cycle" target="_blank" rel="noopener noreferrer">hype cycle</a>. It is in this context that we want to be clear about what our goals are in this space and our approach to releasing data-driven features that draw on techniques from statistics and ML. In short, we want to be clear, open, realistic, and avoid buzzwords at all costs! <p>Over the next 12 months, we are hoping to begin building a layer of intelligence<sup><a href="https://staging-www.netdata.cloud/blog/netdata-cloud-metric-correlations/#1">1</a></sup> throughout Netdata (both Cloud and Agent) to assist with “<a title="human in the loop" href="https://hai.stanford.edu/blog/humans-loop-design-interactive-ai-systems" target="_blank" rel="noopener noreferrer">human in the loop</a>” troubleshooting, mainly to help users more easily surface slowdowns, anomalies, or other issues and lower your <a title="cognitive load" href="https://en.wikipedia.org/wiki/Cognitive_load" target="_blank" rel="noopener noreferrer">cognitive load</a><sup><a href="https://staging-www.netdata.cloud/blog/netdata-cloud-metric-correlations/#2">2</a></sup> as you troubleshoot using Netdata. Simply put, we’re working to streamline your mean time to resolution (MTTR).</p>Netdata Agent v1.25 & Cloud Enhancementshttps://www.netdata.cloud/blog/release-1-25/Wed, 16 Sep 2020 00:00:00 +0000https://www.netdata.cloud/blog/release-1-25/<!--truncate--> <img class="alignnone size-large wp-image-16635" src="../wp-archive/uploads/2022/03/Agent-Release-v1.25@2x-1200x600.png" alt="" width="1200" height="600" /> <p>The <a title="v1.25.0" href="https://github.com/netdata/netdata/releases" target="_blank" rel="noopener noreferrer">v1.25.0</a> release of the Netdata Agent delivers on our commitment to make our metrics collection, visualization, and troubleshooting platform more stable and usable. We enhanced our recently-added <a title="Prometheus collector" href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/prometheus" target="_blank" rel="noopener noreferrer">Prometheus collector</a> with user-configurable filtering and grouping, made dramatic improvements to the reliability of the Agent-Cloud link that streams metrics on-demand to your browser when you use <a title="Netdata Cloud" href="https://app.netdata.cloud/" target="_blank" rel="noopener noreferrer">Netdata Cloud</a>, and more.</p> <p>Let’s jump in and look at each improvement.</p>Netdata named to the Forbes Cloud 100 Rising Starshttps://www.netdata.cloud/blog/forbes-cloud-100-rising-stars-2020/Wed, 16 Sep 2020 00:00:00 +0000https://www.netdata.cloud/blog/forbes-cloud-100-rising-stars-2020/<!--truncate--> <img class=" wp-image-16648 alignleft" src="../wp-archive/uploads/2022/03/Cloud1002020-RisingStars-SMALL.png" alt="" width="390" height="471" /> We’re excited to announce that we’ve been named to the<strong> <a title="Forbes 2020 Cloud 100 Rising Stars" href="https://www.forbes.com/sites/kenrickcai/2020/09/16/cloud-100-rising-stars-2020/" target="_blank" rel="noopener noreferrer">Forbes 2020 Cloud 100 Rising Stars</a>.</strong> This is a list of the top 100 private cloud companies in the world, published by Forbes in partnership with <a title="Bessemer Venture Partners" href="https://www.bvp.com/" target="_blank" rel="noopener noreferrer">Bessemer Venture Partners</a> and <a title="Salesforce Ventures" href="https://www.salesforce.com/company/ventures/" target="_blank" rel="noopener noreferrer">Salesforce Ventures</a>. The 20 Rising Stars represent young, high-growth and category-leading cloud companies who are poised to join the <a title="Cloud 100" href="https://www.forbes.com/cloud100/" target="_blank" rel="noopener noreferrer">Cloud 100</a> ranks. We are extremely honored to be recognized amongst our most-promising peers. This is a testament to our momentum we’ve built in partnership with our passionate community of users and contributors worldwide, as well as a validation of our community-first, open-source approach to democratizing infrastructure monitoring and troubleshooting. The major milestones we’ve hit along the way this year include more than 5,000 new users added each day, more than 3 million users total worldwide, and nearly 50,000 GitHub stars, making Netdata the fourth most starred project in the Cloud Native Computing Foundation landscape. We’ve also launched our monitoring service, Netdata Cloud, which has seen very strong growth since its introduction in May, with more than 15,000 users registered so far. We couldn’t have done it without you! The Forbes 2020 <a title="Cloud 100" href="https://www.forbes.com/cloud100" target="_blank" rel="noopener noreferrer">Cloud 100</a> and 20 Rising Stars lists will also appear in the September 2020 issue of <em>Forbes</em> magazine.The Netdata Community Powered by NodeBBhttps://www.netdata.cloud/blog/the-netdata-community-powered-by-nodebb/Thu, 13 Aug 2020 00:00:00 +0000https://www.netdata.cloud/blog/the-netdata-community-powered-by-nodebb/<!--truncate--> <img class="alignnone size-large wp-image-16658" src="../wp-archive/uploads/2022/03/NodeBB-1-1200x877.png" alt="" width="1200" height="877" /> <p>We recently adopted <a title="NodeBB" href="https://nodebb.org/" target="_blank" rel="noopener noreferrer">NodeBB</a> as our software of choice for building <a title="the Netdata Community" href="https://community.netdata.cloud/" target="_blank" rel="noopener noreferrer">the Netdata Community</a>. We have <a title="many good reasons" href="https://staging-www.netdata.cloud/blog/the-netdata-community/" target="_blank" rel="noopener noreferrer">many good reasons</a> for why we wanted to provide our community with a proper home online, but I wanted to cover some of the technical reasons for choosing NodeBB for our platform, and the many parallels between the NodeBB and Netdata projects, which was certainly a driving force behind this decision.</p>Release 1.24: Prometheus Collector & Multi-Host DBhttps://www.netdata.cloud/blog/release-1-24/Mon, 10 Aug 2020 00:00:00 +0000https://www.netdata.cloud/blog/release-1-24/<!--truncate--> <img class="alignnone size-full wp-image-16663" src="../wp-archive/uploads/2022/03/1.24-release-2.png" alt="" width="683" height="469" /> <p>The v1.24.0 release of the Netdata Agent brings enhancements to the breadth of metrics we collect with a new Prometheus/OpenMetrics collector and enhanced storage and querying with a new multi-host database mode. Let’s take a look at each of these enhancements.</p> <h2>Instantly access thousands of metrics with the new Prometheus/OpenMetrics collector</h2> This release broadens our commitment to open standards, interoperability, and extensibility with a new generic Prometheus collector that works seamlessly with any application that makes its metrics available in the <a href="https://prometheus.io/docs/instrumenting/exposition_formats/">Prometheus</a>/<a href="https://github.com/OpenObservability/OpenMetrics">OpenMetrics</a> exposition format, including support for Windows 10 via <a href="https://github.com/prometheus-community/windows_exporter">windows_exporter</a>. Netdata will autodetect <a href="https://github.com/netdata/go.d.plugin/blob/master/config/go.d/prometheus.conf">over 600 Prometheus endpoints</a> and instantly generate charts with all the exposed metrics, meaningfully visualized. <p>You can also quickly and easily configure the collector with the names and URLs of additional Prometheus endpoints to instantly view automatically generated charts with all the exposed metrics, meaningfully visualized within Netdata at the same high-granularity, per-second frequency you expect, all in real time. To learn more about how to configure, check out our <a title="documentation" href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/prometheus" target="_blank" rel="noopener noreferrer">documentation</a>.</p>Introducing the all-new Netdata Cloudhttps://www.netdata.cloud/blog/introducing-the-all-new-netdata-cloud/Wed, 29 Jul 2020 00:00:00 +0000https://www.netdata.cloud/blog/introducing-the-all-new-netdata-cloud/<!--truncate--> <img class="alignnone size-large wp-image-16672" src="../wp-archive/uploads/2022/03/All-New-Cloud-1200x712.png" alt="" width="1200" height="712" /> <p>In case you missed it, we released an all-new version of Netdata Cloud in May. <a title="Netdata Cloud" href="https://staging-www.netdata.cloud/cloud/">Netdata Cloud</a> is a free service that can be accessed from any browser and provides you with a consolidated view of your entire infrastructure.</p> <p>Netdata Cloud works differently from other monitoring solutions. Most solutions limit the number and frequency of metrics because they rely on architectures that aggregate data. Netdata Cloud, however, streams limited metadata from each node running the Netdata Agent, keeping you in control of the data on your systems. The advantage of this architecture is that there is <strong>no limit</strong> to the number or frequency of metrics, regardless of the scale or complexity of your IT infrastructure. You can truly monitor every metric, from every system and application, across your entire infrastructure, in real time. For free.</p>Sysadmin Day 2020: IT Heroes and Homelabshttps://www.netdata.cloud/blog/sysadmin-day-2020-it-heroes-and-homelabs/Mon, 27 Jul 2020 00:00:00 +0000https://www.netdata.cloud/blog/sysadmin-day-2020-it-heroes-and-homelabs/<!--truncate--> <p dir="ltr" lang="en"><img class="alignnone size-large wp-image-16685" src="../wp-archive/uploads/2022/03/Group-1-2-1200x825.png" alt="" width="1200" height="825" /></p> <p dir="ltr" lang="en">Sysadmin Day 2020 is right around the corner and we’d like to show our appreciation for all the sysadmins out there who keep IT humming along and come to the rescue to resolve critical issues day in and day out. This year, we’re celebrating all week long by hosting an IT Heroes and Homelabs contest. <strong>Join the celebration by retweeting our post with the hashtag #SysadminDay #NetdataWin, and we’ll enter you in a drawing to win some Netdata swag!</strong></p>The Netdata Communityhttps://www.netdata.cloud/blog/the-netdata-community/Mon, 27 Jul 2020 00:00:00 +0000https://www.netdata.cloud/blog/the-netdata-community/<!--truncate--> <img class="alignnone size-large wp-image-16700" src="../wp-archive/uploads/2022/03/Athens-company-meetup-1_2019-scaled-e1588700274782-1200x747.jpeg" alt="" width="1200" height="747" /> <p>Netdata users and contributors comprise a large, global, but somewhat fragmented community – or a set of communities. You can find us on IRC (#netdata on freenode), on <a href="https://www.reddit.com/r/netdata/">Reddit</a>, on <a href="https://twitter.com/linuxnetdata">social media</a>, and, of course, on <a href="https://github.com/netdata/netdata">GitHub</a>, where the main open-source Netdata project repo lives. And yes, you can find us on other platforms as well.</p> <p> </p> <p>GitHub is a great way to get in touch with the Netdata team and project contributors to tell them about bugs or to discuss new features. But we realized that bug reports are not a conversation that works for everyone. A more informal and easier-to-access communication channel would provide a better way for the community to congregate and engage, and would also provide an easier way for everybody to talk to the team. We wanted to provide the community a home.</p>Why Netdata picked VerneMQhttps://www.netdata.cloud/blog/why-netdata-picked-vernemq/Tue, 14 Jul 2020 00:00:00 +0000https://www.netdata.cloud/blog/why-netdata-picked-vernemq/<!--truncate--> <img class="alignnone size-full wp-image-16705" src="../wp-archive/uploads/2022/03/Blog-Why-Netdata-Picked-VerneMQ.jpeg" alt="" width="683" height="470" /> <p>In 2019, the Netdata team already knew that a Netdata Cloud solution in the form of an online platform would greatly complement Netdata’s distributed monitoring by making it much easier to organize large infrastructures and by enabling new ways for teams to collaborate. The old node registry available at the time wasn’t enough for Netdata’s users.</p> <p>Building an online platform, even one that does not directly process users’ metrics, is challenging. But less challenging than it was even a few years ago, since the technology stack has improved greatly over the years.</p>What is Infrastructure Monitoring?https://www.netdata.cloud/blog/what-is-infrastructure-monitoring/Tue, 30 Jun 2020 00:00:00 +0000https://www.netdata.cloud/blog/what-is-infrastructure-monitoring/<!--truncate--> <img class="alignnone size-medium wp-image-16343" src="../wp-archive/uploads/2022/03/Blog-What_is_Infrastructure_Monitoring_Header-600x450.png" alt="" width="600" height="450" /> <p>IT is advancing blazingly fast. To keep up with architectural changes and hybrid environments, it’s more important than ever to maintain efficient infrastructure monitoring and troubleshooting. Adding to the complexity is the increase of distributed systems, comprised of many components and services. For IT teams to effectively manage monitoring modern infrastructure, it’s necessary to have the right practices and tools in place that enable teams to do their jobs as quickly as possible with fewer resources.</p>Release 1.23: Kubernetes & eBPF Observabilityhttps://www.netdata.cloud/blog/release-1-23/Thu, 25 Jun 2020 00:00:00 +0000https://www.netdata.cloud/blog/release-1-23/<!--truncate--> <img class="alignnone size-large wp-image-16712" src="../wp-archive/uploads/2022/03/Agent-1.23-release-1200x900.png" alt="" width="1200" height="900" /> <p>As adoption of container infrastructure grows in popularity, we’re continuing to focus on the most effective ways users can quickly and easily deploy container monitoring to instantly get access to deep, real-time insights. Agent release 1.23 introduces service discovery for Kubernetes clusters, monitoring for individual nodes, and eBPF monitoring per application on an event frequency for quickly identifying the root cause. Quickly shed light on your infrastructure performance with these new features!</p>The role of shift-left testing in an agile environmenthttps://www.netdata.cloud/blog/agile-static-analysis/Tue, 14 Apr 2020 00:00:00 +0000https://www.netdata.cloud/blog/agile-static-analysis/<!--truncate--> <img class="alignnone size-large wp-image-16723" src="../wp-archive/uploads/2022/03/Netdata-Security-use-with-Static-Analysis-1200x899.png" alt="" width="1200" height="899" /> <p>With the rapid growth of security threats to infrastructure, it’s more important than ever to proactively address vulnerabilities. As an open-source project, built on the trust of users and contributors, Netdata has security concerns at its core.</p> <p>Because we’re committed to code security and quality, we apply <a href="https://agilemanifesto.org/">Agile principles</a> throughout the software development process. A component of this includes regular static analysis. Through continuous, automated testing, we’re able to move quickly to keep up with end-user requests without compromising our source code.</p>Release 1.21: New Collectors & Faster Exportershttps://www.netdata.cloud/blog/release-1-21/Mon, 06 Apr 2020 00:00:00 +0000https://www.netdata.cloud/blog/release-1-21/<!--truncate--> <div class="et_pb_module et_pb_text et_pb_text_0 et_pb_text_align_left et_pb_bg_layout_light"> <div class="et_pb_text_inner"> <img class="alignnone size-full wp-image-16737" src="../wp-archive/uploads/2022/03/release-1.21.0.png" alt="" width="1200" height="600" /> <p>We’re in the middle of a scary, uncertain time, and we hope those of you reading are staying safe and healthy.</p> <p>Despite the current challenges, the 40+ members of the <a title="Netdata Remote Working" href="https://staging-www.netdata.cloud/blog/culture/netdata-remote-working/">remote-first Netdata</a> team have been hard at work on the next version of the Netdata Agent: v1.21.0.</p> <p>This release is foundational: While we do have fantastic new collectors and three new ways to export your metrics for long-term storage, many of the most significant changes aren’t even those you’ll notice. While they may be beneath the hood, they’re going to power some amazing new features, UX improvements, and design overhauls.</p>Creating A Thriving, Agile, Remote Teamhttps://www.netdata.cloud/blog/netdata-remote-working/Wed, 25 Mar 2020 00:00:00 +0000https://www.netdata.cloud/blog/netdata-remote-working/<!--truncate--> <img class="alignnone size-large wp-image-16750" src="../wp-archive/uploads/2022/03/netdata-remote-working_01-1200x899.png" alt="" width="1200" height="899" /> <p>The coronavirus (COVID-19) pandemic has forced many organizations to take unprecedented steps towards remote working. As a fully distributed team, we’ve faced the common challenges of remote work. Based on our experience from our very beginning in 2018, all but a few of these organizations new to remote working will face hurdles to overcome and may try to revert to colocation as soon as possible. Remote working is hard, even when it’s carefully planned and executed. When the transition is rushed and seen as a necessary, temporary inconvenience, challenges are all but inevitable.</p>The Netdata Culture and Peoplehttps://www.netdata.cloud/blog/netdata-culture-people/Mon, 23 Mar 2020 00:00:00 +0000https://www.netdata.cloud/blog/netdata-culture-people/<!--truncate--> <p><img src="../wp-archive/uploads/2022/03/people-culture_01.png" alt=""></p> <p>There are many things I absolutely love about Netdata, but I’m most proud of our people and culture. Some words about this unique experience are long overdue.</p> <p>In a career that spans over two decades and six other companies of various sizes, nothing compares to the satisfaction of working in a company like ours. My answer to the canned interview question, “Where do you see yourself in 5 years”, was always the same: I don’t care; I just want to be solving problems and working with good people, real professionals, who I can trust and respect. In retrospect, I was missing another huge part of the equation, which is to mention the kind of company I wanted to work for. “Culture eats strategy for breakfast” is a cliche. More importantly, bad culture devours people’s souls; it sucks out any creative energy one may have, reducing engagement and, therefore, productivity. Short-term wins at the expense of company culture guarantee huge losses in the long run.</p>Contribute to Netdata’s machine learning efforts!https://www.netdata.cloud/blog/contribute-machine-learning/Mon, 16 Mar 2020 00:00:00 +0000https://www.netdata.cloud/blog/contribute-machine-learning/<!--truncate--> <img class="alignnone size-full wp-image-16783" src="../wp-archive/uploads/2022/03/contribute-machine-learning.png" alt="" width="991" height="1072" /> <p>Netdata contributors have greatly influenced the growth of our company and are essential to our success. The time and expertise that contributors volunteer are fundamental to our goal of helping you build extraordinary infrastructures. We highly value end-user feedback during product development, which is why we’re looking to involve you in progressing our machine learning (ML) efforts! <span id="more-2975"></span>As we are continually looking for ways to improve and enhance Netdata, we are starting to explore how we can leverage machine learning to introduce new product features. Our main focus at the moment is around automated <a href="https://en.wikipedia.org/wiki/Anomaly_detection">anomaly detection</a>. This is a really interesting and challenging problem (high volume, high dimensional data, lack of ground truth labels, and so on), but we should be able to use some of the metrics monitored by Netdata to deliver new, awesome product features and user experiences (AI is the <a href="https://www.gsb.stanford.edu/insights/andrew-ng-why-ai-new-electricity">new electricity</a>, after all 😃). However, developing ML-driven product features is quite different than traditional software development (see steps 1 to 7 in the picture above). Mainly, this is because you never really know what specific data transformations, problem formulation, and sets of algorithms will work best in advance. (<a href="https://www.kdnuggets.com/2019/09/no-free-lunch-data-science.html">Here</a> is a good article explaining things, and if you really want to go down a rabbit hole, check out this <a href="https://ai.stackexchange.com/questions/15650/what-are-the-implications-of-the-no-free-lunch-theorem-for-machine-learning">Stack Overflow question</a> and this <a href="https://www.quora.com/What-does-the-No-Free-Lunch-theorem-mean-for-machine-learning-In-what-ways-do-popular-ML-algorithms-overcome-the-limitations-set-by-this-theorem">Quora thread</a>). Ideally, you first need to prototype your solution “in the lab” on some data you have already collected and do a few iterations of data → problem formulation → prototype. This process gives you a level of confidence in what you are doing (and some data to back it up) to move on to the even-more-complicated step of going from prototype to production. At Netdata, we are currently trying to get to step 4, where we can first prototype some solutions on real-world data and come up with ways to measure progress.</p>Linux eBPF monitoring with Netdatahttps://www.netdata.cloud/blog/linux-ebpf-monitoring-with-netdata/Fri, 21 Feb 2020 00:00:00 +0000https://www.netdata.cloud/blog/linux-ebpf-monitoring-with-netdata/<!--truncate--> <img class="alignnone size-full wp-image-16799" src="../wp-archive/uploads/2022/03/linux-ebpf-monitoring-netdata.png" alt="" width="1200" height="600" /> <p>Your application isn’t finished when you’ve closed the last <code>if</code> block and you lined up all the brackets. There’s a whole other world of testing, debugging, and optimization that you haven’t even touched yet.</p> <p>To help you more safely step into that complex phase of making your application <em>even better</em>, we’ve just released a brand-new eBPF collector in <a href="https://staging-www.netdata.cloud/blog/product/release-1.20/">v1.20 of Netdata</a>. With this collector enabled, you can monitor real-time metrics of Linux kernel functions and actions from the very same monitoring and troubleshooting dashboard you use for watching entire systems, or even entire infrastructures.</p>Release 1.20: Kernel Monitoring & Infra-Wide Labelshttps://www.netdata.cloud/blog/release-1-20/Fri, 21 Feb 2020 00:00:00 +0000https://www.netdata.cloud/blog/release-1-20/<!--truncate--> <img class="alignnone size-full wp-image-16790" src="../wp-archive/uploads/2022/03/release-1.20.0.png" alt="" width="1200" height="600" /> <p>In Netdata’s first major release of 2020, we’re introducing two new features on the opposite ends of the monitoring spectrum.</p> <p>On one hand, we’re releasing an eBPF collector, which lets you collect, monitor, and visualize incredibly precise metrics straight from the Linux kernel. On the other, we added the ability to label agents to help you organize entire infrastructures and see <em>every</em> important piece of information about streaming nodes in one place.</p>Redefining monitoring with Netdata (and how it came to be)https://www.netdata.cloud/blog/redefining-monitoring-with-netdata/Thu, 19 Dec 2019 00:00:00 +0000https://www.netdata.cloud/blog/redefining-monitoring-with-netdata/<!--truncate--> <p><img src="../wp-archive/uploads/2019/12/redefining-monitoring-netdata_01.png" alt=""></p> <h2 id="how-netdata-was-born">How Netdata was born</h2> <p>In 2013, I worked for a company that relied on financial transactions. We had a very simple SLA: complete all financial transactions within 3 seconds.</p> <p>We were migrating the infrastructure from colocated (physical servers) to the cloud (VMs). The transition was not smooth. We had a lot of issues on the cloud side, which we couldn’t even detect. Business metrics were randomly reporting significant loss of volume and a very bad SLA, but at the operational level we saw no issues—everything seemed to be working perfectly. Traces were showing a large delay in several transactions, but there were no failures.</p>Release 1.19: Web Log Parsing & Unit Testinghttps://www.netdata.cloud/blog/release-1-19/Wed, 27 Nov 2019 00:00:00 +0000https://www.netdata.cloud/blog/release-1-19/<!--truncate--> <img class="alignnone size-full wp-image-16837" src="../wp-archive/uploads/2022/03/release-1.19.0.png" alt="" width="1200" height="600" /> <p>Network monitoring is complex, which is why we’re developing a monitoring tool that will drastically increase DevOps productivity. This release is all about improving Netdata’s day-in, day-out performance. We’re working hard to make deploy enhancements that help engineers make faster, smarter decisions about their systems.</p> <p> </p> <p>v1.19 of Netdata delivers a vastly improved way to collect, parse, and understand the health and performance of any service or application that runs through an Apache or Nginx web server.</p>Agile Team Safety Harness With cmocka & FOSShttps://www.netdata.cloud/blog/agile-team-cmocka-foss/Tue, 26 Nov 2019 00:00:00 +0000https://www.netdata.cloud/blog/agile-team-cmocka-foss/<!--truncate--> <p>Netdata is made up from agile teams who are deeply committed to improving the usability of our product. We want to respond to our users and introduce in-demand features. Working directly with our community is the best way to make Netdata better.</p> <p> </p> <p>But we face the same the dilemma as all agile teams: <strong>How do we do this safely?</strong></p> <p>Safety means that we can move quickly without compromising the quality of our code. Because we want to move quickly, engage with our users’ desires, and keep quality high, we’re becoming very serious about adopting unit testing in our work.</p>Release 1.18: What’s new with the database engine?https://www.netdata.cloud/blog/release-1-18/Sat, 19 Oct 2019 00:00:00 +0000https://www.netdata.cloud/blog/release-1-18/<!--truncate--> <img class="alignnone size-full wp-image-16859" src="../wp-archive/uploads/2022/03/release-1.18.0.png" alt="" width="1200" height="600" /> <p>As your infrastructure grows more complex, storing long-term metrics becomes difficult and costly to retain. Your team stars to limit the amount of historical data they archive, causing gaps in coverage. Anomalies start to slip through the cracks.</p> <p>Version 1.18 of Netdata aims to solve the monitoring metrics storage problem once and for all.</p> <p>Aside from 5 new collectors, 16 bug fixes, 27 improvements, and 20 documentation updates, here’s what you need to know.</p>Release 1.17: Collection frequency gets flexiblehttps://www.netdata.cloud/blog/release-1-17/Mon, 09 Sep 2019 00:00:00 +0000https://www.netdata.cloud/blog/release-1-17/<!--truncate--> <p>The next version of Netdata has arrived! Aside from dozens of quality-of-life and papercut fixes, we’ve launched some new features we know you’ll be excited to use straight away.</p> <p>Let’s dive in.</p> <h2>What’s new?</h2> Release v1.17.0 contains 38 bug fixes, 33 improvements, and 20 documentation updates. <p>You can, of course, view the full list at the <a href="https://github.com/netdata/netdata/releases/tag/v1.17.0">v1.17.0 release notes</a> on GitHub. But, let’s talk details on a few of the improvements and changes most requested by the Netdata community.</p>How and why we’re bringing long-term storage to Netdatahttps://www.netdata.cloud/blog/db-engine/Wed, 07 Aug 2019 00:00:00 +0000https://www.netdata.cloud/blog/db-engine/<!--truncate--> <p>We’ve built a lot of amazing things into the open-source <a href="https://github.com/netdata/netdata">Netdata</a> monitoring system. But, no matter how far we’ve come, we’ll always be proud of how little RAM it uses.</p> <p>Right now, Netdata stores metrics in your system’s RAM using a ridiculously efficient database. It only saves or loads historical metrics from disk when you restart it. With this system, Netdata can be both low-resource and exhaustive in its collection of real-time metrics.</p>Release 1.16.0: Smarter binaries and built-in TLShttps://www.netdata.cloud/blog/release-1-16/Fri, 19 Jul 2019 00:00:00 +0000https://www.netdata.cloud/blog/release-1-16/<!--truncate--> <p>We’re excited to launch release v1.16.0 of the open-source <a href="https://github.com/netdata/netdata/">Netdata monitoring agent</a>, which delivers real-time health monitoring and performance troubleshooting to nearly any system or application.</p> <p>This release also contains 40 bug fixes, 31 improvements, and 20 documentation updates—if you’d like to see the full list, check out the <a href="https://github.com/netdata/netdata/releases/tag/v1.16.0">full release notes</a>.</p> <p>Details aside, I know people are going to be most curious about the big changes we’ve just delivered to Netdata—let’s dive in.</p>Open Source Contributions: Supporting The Communityhttps://www.netdata.cloud/blog/open-source-contributions/Tue, 02 Jul 2019 00:00:00 +0000https://www.netdata.cloud/blog/open-source-contributions/<!--truncate--> <p>Netdata <em>must</em> be doing something right when it comes to inspiring contributions. Our <a href="https://github.com/netdata/netdata">open-source, distributed monitoring agent</a> has <img src="https://img.shields.io/github/stars/netdata/netdata.svg" alt="GitHub stars" /> on GitHub and has seen contributions from hundreds of people: <img src="https://img.shields.io/github/contributors/netdata/netdata.svg" alt="GitHub contributors" />. We’ve even hired a handful of our contributors to work full-time on making the Netdata ecosystem even more powerful.</p> <p> </p> <p>The community is passionate about what we’re building, and they’re actively interested in making it work better for their particular needs.</p><link>https://www.netdata.cloud/value/calculator/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/value/calculator/</guid><description><p>// ============================================ // NETDATA ROI CALCULATOR - LOGIC &amp; VARIABLES // ============================================</p> <p>// INPUT VARIABLES // ============================================ hosts = integer (10 to 10,000+) // Number of monitored hosts/nodes mttr = integer (5 to 240 minutes) // Current average MTTR for critical incidents incidents = integer (1 to 50+) // Number of critical incidents per month currentCosts = integer ($0 to $1M+) // Annual monitoring tool costs teamSize = integer (5 to 200+) // Size of engineering/DevOps team engineerCost = integer ($50 to $200+) // Average hourly cost per engineer impactGroup = enum [&ldquo;engineering&rdquo;, &ldquo;customers&rdquo;, &ldquo;both&rdquo;] // Who is impacted by downtime revenueImpact = integer ($0 to $1M+) // Revenue loss per hour of downtime</p></description></item><item><title>.NET Framework Monitoringhttps://www.netdata.cloud/monitoring-101/dotnet-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/dotnet-monitoring/<h2 id="net-framework">.NET Framework</h2> <p>.NET Framework is a software development platform that runs on Windows. <a href="https://dotnet.microsoft.com/en-us/download/dotnet-framework">It provides a common set of libraries and tools that developers can use to build different types of applications, such as web apps, desktop apps, mobile apps, games, and more</a>.</p> <h2 id="net-framework-monitoring">.NET Framework Monitoring</h2> <p>One of the challenges of developing and maintaining .NET applications is to ensure their performance, reliability, and security. To do that, developers need to monitor various aspects of their applications, such as code execution, memory usage, exceptions, requests, errors, and more. Monitoring .NET applications can help developers identify and troubleshoot issues before they affect the end users.</p>1-Wire Sensors Monitoringhttps://www.netdata.cloud/monitoring-101/1wiresensors-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/1wiresensors-monitoring/<h2 id="what-are-a-1-wire-sensors">What are a 1-Wire Sensors?</h2> <p>These sensors monitor temperature. On Linux these are supported by the wire, w1_gpio, and w1_therm modules. Currently temperature sensors are supported and automatically detected.</p> <h2 id="monitoring-1-wire-sensors-with-netdata">Monitoring 1-Wire Sensors with Netdata</h2> <p>Netdata auto discovers hundreds of services, and for those it doesn&rsquo;t turning on manual discovery is a one line configuration. For more information on configuring Netdata for 1-Wiresensors monitoring please read the collector <a href="https://learn.netdata.cloud/docs/agent/collectors/python.d.plugin/w1sensor/">documentation</a>.</p> <p>Netdata has a public <a href="https://app.netdata.cloud/spaces/netdata-demo/">demo space</a> (no login required) where you can explore different monitoring use-cases and get a feel for Netdata.</p>1-Wire Sensors Monitoringhttps://www.netdata.cloud/monitoring-101/w1sensor-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/w1sensor-monitoring/<h2 id="1-wire-sensors-monitoring">1-Wire Sensors Monitoring</h2> <h3 id="what-is-1-wire-sensors">What Is 1-Wire Sensors?</h3> <p>1-Wire Sensors are a type of sensor technology used primarily for temperature monitoring through a simple communication protocol. These sensors are commonly employed in environments where real-time temperature tracking is crucial, such as server rooms, laboratories, or manufacturing lines.</p> <h3 id="monitoring-1-wire-sensors-with-netdata">Monitoring 1-Wire Sensors With Netdata</h3> <p>Netdata offers an advanced and intuitive platform for monitoring 1-Wire Sensors. By leveraging the Netdata <strong><a href="https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/1-wire-sensors/">1-Wire Sensors monitoring tool</a></strong>, you can achieve real-time visibility into your environmental conditions, enabling you to respond swiftly to changes that could affect your infrastructure.</p>4D Server Monitoringhttps://www.netdata.cloud/monitoring-101/4d_server-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/4d_server-monitoring/<h2 id="4d-server-monitoring">4D Server Monitoring</h2> <h3 id="what-is-4d-server">What Is 4D Server?</h3> <p>4D Server is a database server that seamlessly combines a powerful SQL engine with innovative application development capabilities. It is renowned for its flexibility and efficiency in managing complex applications and databases. Whether you are building applications, handling large databases, or performing detailed data analysis, 4D Server provides the necessary infrastructure to manage your needs effectively.</p> <h3 id="monitoring-4d-server-with-netdata">Monitoring 4D Server With Netdata</h3> <p>Monitoring 4D Server is essential for maintaining its health and performance. With Netdata, you can easily monitor 4D Server using the integrated capabilities of the go.d.plugin. This monitoring tool leverages an openmetrics (Prometheus) exporter, allowing you to gather essential metrics seamlessly. The Netdata platform can ingest data from any Prometheus exporter, providing users with automated dashboards, real-time alerts, and comprehensive insights—all without the need for a standalone Prometheus server or Grafana setup. Explore how robust 4D Server monitoring can enhance your system management.</p>8430FT Modem Monitoringhttps://www.netdata.cloud/monitoring-101/8430ft-modem-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/8430ft-modem-monitoring/<h2 id="8430ft-modem-monitoring">8430FT Modem Monitoring</h2> <h3 id="what-is-8430ft-modem">What Is 8430FT Modem?</h3> <p>The 8430FT modem is a crucial component within network stacks, providing connectivity and data transfer capabilities in various technical environments. Understanding how this modem operates allows IT professionals, network engineers, and developers to ensure optimal performance and reliability.</p> <h3 id="monitoring-8430ft-modem-with-netdata">Monitoring 8430FT Modem With Netdata</h3> <p>For monitoring the 8430FT modem, Netdata utilizes an advanced openmetrics (Prometheus) exporter. By leveraging the <a href="https://github.com/dernasherbrezon/8430ft_exporter">8430FT Exporter</a>, Netdata can efficiently collect and visualize essential metrics from the modem, aiding in network performance diagnostics. Unlike traditional setups, Netdata can ingest data from any Prometheus exporter, which means that users do not need an entire Prometheus server or Grafana to obtain actionable insights. With Netdata, these metrics are instantly transformed into automated dashboards and alerts, expediting the troubleshooting process.</p>Access Points Monitoringhttps://www.netdata.cloud/monitoring-101/ap-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/ap-monitoring/<h2 id="access-points-monitoring">Access Points Monitoring</h2> <h3 id="what-is-access-points">What Is Access Points?</h3> <p>Access Points, commonly referred to as APs, are pivotal devices in wireless networks, serving as gateways for clients to connect to larger networks. They facilitate seamless communication by acting as a bridge between wireless clients and the wired network infrastructure.</p> <h3 id="monitoring-access-points-with-netdata">Monitoring Access Points With Netdata</h3> <p>Monitoring Access Points effectively is crucial for ensuring optimal network performance and reliability. With <a href="https://www.netdata.cloud/integrations/data-collection/networking/access-points/">Netdata&rsquo;s Access Points monitoring tool</a>, you can gain deep insights into the operations of your wireless network infrastructure. Netdata&rsquo;s platform allows for real-time monitoring and troubleshooting, offering a comprehensive view of various performance metrics. You can <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">explore our live demo</a> to see how it works in real time.</p>Active Directory Monitoringhttps://www.netdata.cloud/monitoring-101/ad-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/ad-monitoring/<h2 id="active-directory">Active Directory</h2> <p>Active Directory (AD) is a tool from Microsoft that helps you manage Windows networks. It comes with most Windows Server systems and does many things. At first, Active Directory only helped you control domains. But now, it also helps you with many other things related to identity.</p> <p><a href="https://learn.microsoft.com/en-us/windows-server/identity/ad-fs/design/ad-fs-requirements">It stores information about objects on the network, such as users, computers, groups, printers, and policies</a>. <a href="https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn781428(v=ws.11)">It also provides methods for authenticating and authorizing users and devices</a>. Active Directory can be deployed on-premises or in the cloud with Azure Active Directory (Azure AD).</p>ActiveMQ Monitoringhttps://www.netdata.cloud/monitoring-101/activemq-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/activemq-monitoring/<h2 id="activemq-monitoring">ActiveMQ Monitoring</h2> <h3 id="what-is-activemq">What Is ActiveMQ?</h3> <p>ActiveMQ is a popular open-source message broker designed for message-oriented middleware. It is known for its versatility in handling various messaging protocols, supporting the Java Messaging Service (JMS) API, and its ability to run as a standalone broker or in a fully distributed enterprise setup. For technical users like DevOps, SREs, and developers, ActiveMQ allows seamless integration of numerous applications, facilitating reliable and asynchronous message exchanges. <a href="https://activemq.apache.org/">Learn more about ActiveMQ</a>.</p>Adaptec RAID Monitoringhttps://www.netdata.cloud/monitoring-101/adaptecraid-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/adaptecraid-monitoring/<h2 id="adaptec-raid-monitoring">Adaptec RAID Monitoring</h2> <h3 id="what-is-adaptec-raid">What Is Adaptec RAID?</h3> <p>Adaptec RAID is a trusted storage solution designed to manage and protect your data using Redundant Array of Independent Disks (RAID) technology. These controllers are widely used for enhancing storage reliability and performance by spreading data across multiple disks.</p> <h3 id="monitoring-adaptec-raid-with-netdata">Monitoring Adaptec RAID With Netdata</h3> <p>To monitor Adaptec RAID efficiently, Netdata offers a comprehensive monitoring tool that integrates seamlessly with your system. The <a href="https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/adaptec-raid/">$name monitoring tool</a> helps you gain insights into the status and health of your RAID arrays in real time, enabling proactive maintenance and swift troubleshooting.</p>Alamos FE2 server Monitoringhttps://www.netdata.cloud/monitoring-101/alamos_fe2-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/alamos_fe2-monitoring/<h2 id="alamos-fe2-server-monitoring">Alamos FE2 server Monitoring</h2> <h3 id="what-is-alamos-fe2-server">What Is Alamos FE2 server?</h3> <p>The Alamos FE2 server is a comprehensive platform that demands diligent monitoring to ensure optimal performance and health. This server acts as a vital component in various infrastructures requiring consistent oversight and data collection for efficient operations.</p> <h3 id="monitoring-alamos-fe2-server-with-netdata">Monitoring Alamos FE2 server With Netdata</h3> <p>Monitoring the Alamos FE2 server is streamlined with Netdata, which employs an openmetrics (Prometheus) exporter. Netdata is capable of ingesting data from any Prometheus exporter, a significant advantage over traditional setups requiring a dedicated Prometheus server or Grafana for visualization. By leveraging Netdata, users obtain automated dashboards, intelligent alerts, and real-time insights designed to keep the Alamos FE2 server running smoothly.</p>AM2320 Monitoringhttps://www.netdata.cloud/monitoring-101/am2320-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/am2320-monitoring/<h2 id="what-is-am2320">What is AM2320?</h2> <p>AM2320 is a temperature and humidity sensor that can be used to measure environment conditions. It features a range of features including a high accuracy of ± 0.5°C and low power consumption. It is suitable for a variety of applications, making it a versatile choice for your project.</p> <h2 id="monitoring-am2320-with-netdata">Monitoring AM2320 with Netdata</h2> <p>The prerequisites for monitoring AM2320 with Netdata are to have AM2320 and <a href="https://learn.netdata.cloud/docs/cloud/get-started/">Netdata installed</a> on your system.</p>AMD CPU & GPU Monitoringhttps://www.netdata.cloud/monitoring-101/amd_smi-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/amd_smi-monitoring/<h2 id="amd-cpu--gpu-monitoring">AMD CPU &amp; GPU Monitoring</h2> <h3 id="what-is-amd-cpu--gpu">What Is AMD CPU &amp; GPU?</h3> <p>AMD CPUs and GPUs form the core of many computational systems, driving performance in everything from gaming computers to data centers that power cloud applications. The AMD System Management Interface (SMI) is crucial for monitoring the performance and health of these processors, helping users optimize hardware performance through precise metrics.</p> <h3 id="monitoring-amd-cpu--gpu-with-netdata">Monitoring AMD CPU &amp; GPU With Netdata</h3> <p>Monitoring AMD CPU &amp; GPU is essential for ensuring that your systems operate efficiently and without interruption. Netdata leverages the <a href="https://github.com/amd/amd_smi_exporter">AMD SMI Exporter</a> to monitor these devices. By using an openmetrics (Prometheus) exporter, Netdata can seamlessly ingest metrics without the need for a Prometheus server or Grafana. Once connected, users can enjoy automated dashboards and alerts, making it a comprehensive AMD CPU &amp; GPU monitoring tool.</p>Apache Monitoringhttps://www.netdata.cloud/monitoring-101/apache-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/apache-monitoring/<h2 id="apache-monitoring">Apache Monitoring</h2> <h3 id="what-is-apache">What Is Apache?</h3> <p>Apache is one of the most widely used web servers in the world. Officially known as the Apache HTTP Server, it was developed and is maintained by an open community under the auspices of the Apache Software Foundation. Since its inception, Apache has grown into an essential component of the web infrastructure. For more details, visit the <a href="https://httpd.apache.org/">official Apache website</a>.</p> <h3 id="monitoring-apache-with-netdata">Monitoring Apache With Netdata</h3> <p>Monitoring Apache is crucial to ensuring optimal web server performance, resource utilization, and improving user experiences. Netdata&rsquo;s real-time monitoring solution provides instant insights into the performance and status of your Apache server. The Netdata Agent, when deployed, offers a wide array of metrics and visualizations to help you keep track of connections, request rates, bandwidth usage, and more. For a full demonstration, check out our <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">Live Demo</a>.</p>Apache Pulsar Monitoringhttps://www.netdata.cloud/monitoring-101/pulsar-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/pulsar-monitoring/<h2 id="apache-pulsar-monitoring">Apache Pulsar Monitoring</h2> <h3 id="what-is-apache-pulsar">What Is Apache Pulsar?</h3> <p><a href="https://pulsar.apache.org/">Apache Pulsar</a> is an open-source distributed messaging and streaming platform. It provides a unified messaging model and is designed to handle high-throughput, low-latency workloads. With its multi-tenancy, geo-replication, and seamless scalability features, Pulsar is a comprehensive solution tailored for both messaging and streaming use cases.</p> <h3 id="monitoring-apache-pulsar-with-netdata">Monitoring Apache Pulsar With Netdata</h3> <p>Monitoring Apache Pulsar is crucial for ensuring the system’s health and performance. Netdata offers a powerful and intuitive way to monitor Pulsar, leveraging its robust capabilities to deliver real-time insights. The <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/pulsar/?utm_source=website&amp;utm_content=monitoring101">Netdata Pulsar monitoring tool</a> taps into Pulsar&rsquo;s <a href="https://pulsar.apache.org/docs/en/deploy-monitoring/#broker-stats">Prometheus endpoint</a> to collect a wide range of metrics that help you keep your messaging system running smoothly.</p>APC UPS Monitoringhttps://www.netdata.cloud/monitoring-101/apcupsd-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/apcupsd-monitoring/<h2 id="apc-ups-monitoring">APC UPS Monitoring</h2> <h3 id="what-is-apc-ups">What Is APC UPS?</h3> <p>APC UPS, or Uninterruptible Power Supply systems from <a href="https://www.apc.com">APC</a>, are crucial components in ensuring the continuity and protection of power to critical infrastructure. These devices ensure that your servers, data centers, and critical systems stay powered even during a power outage, safeguarding your operations against data loss and downtime.</p> <h3 id="monitoring-apc-ups-with-netdata">Monitoring APC UPS With Netdata</h3> <p>Monitoring platforms like Netdata allow you to keep an eye on the health, performance, and capacity of your APC UPS units in real-time. Utilizing the <a href="https://www.netdata.cloud/integrations/data-collection/hardware-and-sensors/apc-ups/">Apcupsd</a> daemon, Netdata provides comprehensive visibility into UPS performance and alerts you to any issues so they can be addressed promptly.</p>APIcast Monitoringhttps://www.netdata.cloud/monitoring-101/apicast-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/apicast-monitoring/<h2 id="apicast-monitoring">APIcast Monitoring</h2> <h3 id="what-is-apicast">What Is APIcast?</h3> <p>APIcast is a powerful API management solution designed for API traffic across various web and cloud applications. It acts as a gateway, controlling how APIs are exposed, secured, and consumed. Built by 3scale, APIcast allows organizations to manage and monetize their APIs effectively, ensuring robust security and operational efficiency. Discover more about <a href="https://github.com/3scale/apicast">APIcast here</a>.</p> <h3 id="monitoring-apicast-with-netdata">Monitoring APIcast With Netdata</h3> <p>To effectively monitor APIcast, Netdata leverages an openmetrics (Prometheus) exporter. This allows Netdata to ingest data from any Prometheus exporter and provide automated dashboards and alerts without necessitating a Prometheus server or Grafana setup. This seamless integration helps in gaining real-time insights into APIcast&rsquo;s performance, ensuring optimal operation. By using the Netdata infrastructure monitoring tool, APIcast users can experience detailed, user-friendly dashboards and benefit from real-time alerts, all designed to keep your API services performing at their peak.</p>Apply to Become a Netdata Partnerhttps://www.netdata.cloud/partnership-contact/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/partnership-contact/ARP cache staleness: when IP-to-MAC mapping goes badhttps://www.netdata.cloud/guides/network/network-arp-cache-staleness/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-arp-cache-staleness/<p>Hosts on the same subnet stop reaching each other after a VM live-migrates, a container gets rescheduled, or a firewall fails over. ICMP works from some hosts but not others. TCP sessions hang or reset. The data plane is healthy, but the ARP cache on one or more hosts holds a stale IP-to-MAC mapping.</p> <p>ARP cache staleness is the gap between when a MAC address changes and when every interested host learns about the change. On Linux, this gap is governed by the neighbor (NUD) state machine and its timing parameters. On Windows Vista and later, the neighbor cache follows the same RFC 4861 model. Both platforms default to roughly the same reachable time window: about 15 to 45 seconds before an entry transitions to a stale state, followed by a probe sequence that adds several more seconds before resolution or eviction.</p>Asymmetric routing: why your path and latency measurements liehttps://www.netdata.cloud/guides/network/network-asymmetric-routing/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-asymmetric-routing/<p>Your monitoring says the path is fine. Ping latency is normal, traceroute shows a clean route, and interface counters look healthy. But applications are slow, TCP sessions stall or reset, and users are complaining. Your tools are measuring only half the path.</p> <p>In asymmetric routing, traffic from host A to host B takes one path (P1) while return traffic from B to A takes a different path (P2). When P2 is degraded, congested, or broken, your measurements average the healthy forward path with the impaired return path. Every acknowledgment and response is fighting through a bad route while the aggregate looks acceptable.</p>Audit log gaps: detecting syslog/trap tampering or losshttps://www.netdata.cloud/guides/network/network-audit-log-gap/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-audit-log-gap/<p>An audit log gap is any period where expected syslog messages or SNMP traps from a network device fail to arrive at the collector. UDP syslog on port 514 and SNMP traps on port 162 are fire-and-forget transports with no delivery guarantee. The kernel silently drops datagrams when socket buffers fill, and the application layer never sees the loss. TCP syslog can stall under collector backpressure. Most gaps are operational: network loss, device-side buffer overflow, or logging subsystem failure. The difficulty is distinguishing those from deliberate log suppression after compromise.</p>AuthLog Monitoringhttps://www.netdata.cloud/monitoring-101/authlog-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/authlog-monitoring/<h2 id="authlog-monitoring">AuthLog Monitoring</h2> <h3 id="what-is-authlog">What Is AuthLog?</h3> <p>AuthLog is a tool designed for monitoring authentication logs to gain security insights and facilitate efficient access management. Its primary function is to track and analyze authentication attempts, providing crucial data for assessing security posture and identifying unauthorized access attempts.</p> <h3 id="monitoring-authlog-with-netdata">Monitoring AuthLog With Netdata</h3> <p>To monitor AuthLog effectively, Netdata uses an openmetrics (Prometheus) exporter, the <a href="https://github.com/woblerr/authlog_exporter">AuthLog Exporter</a>. Netdata&rsquo;s robust monitoring capabilities allow it to ingest data from any Prometheus exporter. This means you can set up automated dashboards, alerts, and more without the need for a Prometheus server or Grafana. By utilizing Netdata, users can leverage real-time monitoring of their AuthLog metrics to ensure comprehensive security coverage and quick response to potential threats.</p>AWS EC2 Compute Instances Monitoringhttps://www.netdata.cloud/monitoring-101/aws_ec2-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/aws_ec2-monitoring/<h2 id="aws-ec2-compute-instances-monitoring">AWS EC2 Compute Instances Monitoring</h2> <h3 id="what-is-aws-ec2-compute-instances">What Is AWS EC2 Compute Instances?</h3> <p>AWS EC2 (Elastic Compute Cloud) instances are a key element of Amazon Web Services, providing scalable computing capacity in the cloud. They eliminate the need to invest in hardware, allowing companies to focus on their applications while benefiting from the flexibility of cloud infrastructure.</p> <h3 id="monitoring-aws-ec2-compute-instances-with-netdata">Monitoring AWS EC2 Compute Instances With Netdata</h3> <p>Netdata offers a comprehensive platform for monitoring AWS EC2 Compute Instances, highlighting the critical metrics that can significantly impact performance and cost management. Utilizing an openmetrics (Prometheus) exporter, Netdata can seamlessly ingest data from any Prometheus exporter, delivering automated dashboards, alerts, and more, all without the need for a Prometheus server or Grafana. This powerful capability allows technical users to monitor AWS EC2 with precision and minimum friction.</p>AWS Quota Monitoringhttps://www.netdata.cloud/monitoring-101/aws_quota-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/aws_quota-monitoring/<h2 id="aws-quota-monitoring">AWS Quota Monitoring</h2> <h3 id="what-is-aws-quota">What Is AWS Quota?</h3> <p>AWS Quota refers to the limits set on the number of resources and API requests you can use in Amazon Web Services. Effective management of AWS Quotas ensures optimal resource usage, cost management, and prevents disruption in services due to resource limitations.</p> <h3 id="monitoring-aws-quota-with-netdata">Monitoring AWS Quota With Netdata</h3> <p>To monitor AWS Quota with Netdata, you can leverage the <a href="https://github.com/emylincon/aws_quota_exporter">aws_quota_exporter</a>, an openmetrics (prometheus) exporter. Netdata is designed to seamlessly ingest data from any Prometheus exporter, providing you with powerful, automated dashboards and alerts without the need for setting up a Prometheus server or Grafana. Netdata’s out-of-the-box integration simplifies the complexity associated with setting up AWS Quota monitoring, enabling you to focus on resource management and optimization.</p>AWS RDS Monitoringhttps://www.netdata.cloud/monitoring-101/aws_rds-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/aws_rds-monitoring/<h2 id="aws-rds-monitoring">AWS RDS Monitoring</h2> <h3 id="what-is-aws-rds">What Is AWS RDS?</h3> <p>Amazon RDS (Relational Database Service) is a managed cloud database service that simplifies database administration tasks such as hardware provisioning, database setup, patching, and backups. It enables organizations to efficiently scale databases while managing performance, availability, and security. AWS RDS supports various database engines, including MySQL, PostgreSQL, MariaDB, Oracle, and SQL Server, making it a versatile choice for cloud-based database solutions.</p> <h3 id="monitoring-aws-rds-with-netdata">Monitoring AWS RDS With Netdata</h3> <p>Monitoring AWS RDS is critical for ensuring the performance, availability, and reliability of your cloud databases. Netdata provides a powerful tool for monitoring AWS RDS using an openmetrics (Prometheus) exporter. Netdata can ingest real-time metrics from any Prometheus exporter, including the <a href="https://github.com/percona/rds_exporter">rds_exporter</a>, without needing a separate Prometheus server or Grafana setup.</p>Beanstalk Monitoringhttps://www.netdata.cloud/monitoring-101/beanstalk-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/beanstalk-monitoring/<h2 id="beanstalk-monitoring">Beanstalk Monitoring</h2> <h3 id="what-is-beanstalk">What Is Beanstalk?</h3> <p>Beanstalk is a simple and fast work queue. It is designed to reduce the complexity of creating distributed applications and focuses on speed and reliability. Beanstalk helps developers manage background jobs easily, allowing processes to be executed asynchronously.</p> <h3 id="monitoring-beanstalk-with-netdata">Monitoring Beanstalk With Netdata</h3> <p>Monitor Beanstalk effortlessly using Netdata&rsquo;s <a href="https://learn.netdata.cloud/docs/collecting-metrics/collectors/databases/beanstalk?utm_source=website&amp;utm_content=monitoring101">beanstalk monitoring tool</a>. Netdata provides real-time performance metrics and analytics, enabling you to keep a close eye on your Beanstalk servers and ensure they are running smoothly. Whether you are dealing with data collection, message brokers, or distributed systems, optimizing performance and preventing resource bottlenecks has never been easier with Netdata.</p>BGP flapping: why a peer keeps resetting and how to find the causehttps://www.netdata.cloud/guides/network/network-bgp-flapping/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-bgp-flapping/<p>A BGP peer cycling between Established and Idle is sending a specific signal. The session tears down because one side sent a NOTIFICATION message, and that message carries an error code and subcode that pinpoints the cause. Most monitoring watches only the FSM state (up or down) and ignores the NOTIFICATION payload, so the operator sees flapping without knowing why.</p> <p>The second trap is treating the symptom. Clearing the session or increasing the hold timer does not fix the underlying cause. The session re-establishes briefly, then drops again identically. The hold timer is not the problem; the hold timer is detecting the problem.</p>BGP NOTIFICATION and Cease messages: what each subcode is telling youhttps://www.netdata.cloud/guides/network/network-bgp-notification-cease/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-bgp-notification-cease/<p>A BGP NOTIFICATION in your router log is a peer telling you why it tore down the session. The message carries an error code and an error subcode. Those two numbers tell you whether you are looking at a maintenance window, a route leak, a prefix-limit hit, a CPU-starved control plane, or a BFD-triggered teardown.</p> <p>Cease (code 6) is the most common NOTIFICATION. Its subcodes, defined in RFC 4486 and extended by RFC 8538 and RFC 9384, hold most of the diagnostic value. Codes 2 through 5 appear less often but point to distinct failure classes: parameter mismatch, malformed updates, hold-timer expiry, and FSM errors.</p>BGP route leak and hijack: the detection signals and alerts that matterhttps://www.netdata.cloud/guides/network/network-bgp-route-leak-hijack/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-bgp-route-leak-hijack/<p>A BGP route leak or hijack does not tear down your session. The peering stays Established, keepalives flow, and the session &ldquo;up&rdquo; indicator stays green. What changes is which prefixes your network believes are reachable, through which origin AS, and via what path. Traffic is silently misrouted or blackholed while the session looks healthy.</p> <p>BGP has no built-in authentication of route ownership. Any AS can announce any prefix. Whether other networks accept the announcement depends on their filtering, and filtering is inconsistently deployed. Approximately 50% of routable IP prefixes carry a Route Origin Authorization (ROA), and only about 6.5% of Internet users sit behind networks that actively reject RPKI-invalid routes. That gap is where leaks and hijacks propagate globally before anyone notices.</p>BGP session Established but stale: detecting silent route losshttps://www.netdata.cloud/guides/network/network-bgp-session-stale/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-bgp-session-stale/<p>Your BGP session to a transit provider or iBGP peer is Established, but destinations are unreachable. The RIB is missing prefixes from that peer, or the routes it has are stale. No NOTIFICATION was sent, no session flap occurred, and your monitoring trusts the FSM state.</p> <p>This is the &ldquo;Established but stale&rdquo; pattern. KEEPALIVEs are still exchanged at the TCP level, but the UPDATE exchange has stopped. The peer stopped sending routes, a middlebox is silently dropping UPDATE packets, or Graceful Restart is holding the session open after the remote side went down.</p>BIND 9 Monitoringhttps://www.netdata.cloud/monitoring-101/bind9-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/bind9-monitoring/<h2 id="what-is-bind-9">What is BIND 9?</h2> <p>BIND 9 is a flexible, full-featured open source DNS system.</p> <h2 id="monitoring-bind-9-with-netdata">Monitoring BIND 9 with Netdata</h2> <p>The prerequisites for monitoring <a href="https://www.isc.org/bind/">BIND 9</a> with Netdata are to have BIND and <a href="https://learn.netdata.cloud/docs/cloud/get-started/">Netdata installed</a> on your system.</p> <p>Netdata auto discovers hundreds of services, and for those it doesn&rsquo;t turning on manual discovery is a one line configuration. For more information on configuring Netdata for BIND 9 monitoring please read the collector <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/bind/">documentation</a>.</p> <p>You should now see the <code>bind</code> section on the Overview tab in Netdata Cloud already populated with charts about all the metrics you care about.</p>Bird Routing Daemon Monitoringhttps://www.netdata.cloud/monitoring-101/bird-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/bird-monitoring/<h2 id="bird-routing-daemon-monitoring">Bird Routing Daemon Monitoring</h2> <h3 id="what-is-bird-routing-daemon">What Is Bird Routing Daemon?</h3> <p>The Bird Routing Daemon is a comprehensive software for managing BGP and other routing protocols. It&rsquo;s favored in the networking community for its scalability and flexibility. With Bird, administrators can maintain robust and efficient network routing essential for data flow across various network architectures.</p> <h3 id="monitoring-bird-routing-daemon-with-netdata">Monitoring Bird Routing Daemon With Netdata</h3> <p>Netdata provides an efficient Bird Routing Daemon monitoring tool that leverages an openmetrics (Prometheus) exporter for data collection. This integration allows seamless ingestion of Bird Routing Daemon metrics without needing an additional Prometheus server or Grafana setup. Netdata offers automated dashboards and alerts out-of-the-box, ensuring you have real-time insight into your network&rsquo;s performance and reliability.</p>Blackbox Monitoringhttps://www.netdata.cloud/monitoring-101/blackbox-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/blackbox-monitoring/<h2 id="blackbox-monitoring">Blackbox Monitoring</h2> <h3 id="what-is-blackbox">What Is Blackbox?</h3> <p>Blackbox is a versatile monitoring tool designed to test endpoints via HTTP, DNS, TCP and ICMP protocols. As a member of the Prometheus ecosystem, Blackbox enables the continuous evaluation of uptime and response times, providing critical insights into external service availability. By simulating requests to your key infrastructure components, Blackbox ensures you are the first to know when issues occur.</p> <h3 id="monitoring-blackbox-with-netdata">Monitoring Blackbox With Netdata</h3> <p>To effectively monitor Blackbox, Netdata integrates with the Prometheus ecosystem via an openmetrics (Prometheus) exporter. This means you can leverage the <a href="https://github.com/prometheus/blackbox_exporter">Blackbox exporter</a> to gather metrics seamlessly. With Netdata, you can ingest data from any Prometheus exporter, streamlining your monitoring setup without needing a full Prometheus server or Grafana dashboard stack. Netdata automatically provides dashboards and alerts, ensuring you have real-time insights into your monitored services.</p>BOINC Monitoringhttps://www.netdata.cloud/monitoring-101/boinc-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/boinc-monitoring/<h2 id="boinc-monitoring">BOINC Monitoring</h2> <h3 id="what-is-boinc">What Is BOINC?</h3> <p>The Berkeley Open Infrastructure for Network Computing (BOINC) is a platform for volunteer computing and is used by various scientific projects. It allows users to donate their computing resources to assist in complex calculations and data analysis. Understanding the underlying metrics of BOINC is crucial for maintaining optimal performance and ensuring that resources are effectively utilized.</p> <h3 id="monitoring-boinc-with-netdata">Monitoring BOINC With Netdata</h3> <p>Netdata provides an intuitive and powerful way to monitor your BOINC instances. Our BOINC monitoring tool collects real-time data and allows you to visualize important metrics to identify trends and potential issues. With Netdata, you can gain insights into task counts and manage distributed computing efforts more effectively.</p>BOSH Monitoringhttps://www.netdata.cloud/monitoring-101/bosh-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/bosh-monitoring/<h2 id="bosh-monitoring">BOSH Monitoring</h2> <h3 id="what-is-bosh">What Is BOSH?</h3> <p>BOSH is an open-source tool used for release engineering, deployment, lifecycle management, and monitoring of distributed systems. As a pivotal component in cloud orchestration, BOSH simplifies the deployment of cloud infrastructure, ensuring scalability and resilience. It&rsquo;s an essential tool for DevOps, SRE, developers, IT admins, and IT engineers who manage complex application environments.</p> <h3 id="monitoring-bosh-with-netdata">Monitoring BOSH With Netdata</h3> <p>To monitor BOSH effectively, Netdata employs a powerful openmetrics (Prometheus) exporter called the <a href="https://github.com/bosh-prometheus/bosh_exporter">BOSH exporter</a>. This integration allows Netdata to ingest data directly from any Prometheus exporter. With Netdata, you get automated dashboards and real-time alerts, all without needing a separate Prometheus server or Grafana setup. This makes Netdata a highly efficient BOSH monitoring tool, allowing for a seamless and comprehensive monitoring experience.</p>BungeeCord Monitoringhttps://www.netdata.cloud/monitoring-101/bungeecord-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/bungeecord-monitoring/<h2 id="bungeecord-monitoring">BungeeCord Monitoring</h2> <h3 id="what-is-bungeecord">What Is BungeeCord?</h3> <p>BungeeCord is a popular proxy server for the Minecraft game, used to connect multiple servers together for seamless gameplay. It allows players to switch between different Minecraft servers without needing to relog, making it an essential tool for managing complex Minecraft networks.</p> <h3 id="monitoring-bungeecord-with-netdata">Monitoring BungeeCord With Netdata</h3> <p>To monitor BungeeCord, Netdata employs an openmetrics (Prometheus) exporter. This approach leverages the <a href="https://github.com/weihao/bungeecord-prometheus-exporter">BungeeCord Prometheus Exporter</a>, allowing Netdata to track important server metrics seamlessly. With Netdata, you can ingest data from any Prometheus exporter, offering automated dashboards, alerting, and more. Remarkably, this doesn&rsquo;t require a Prometheus server or Grafana, making it simple and efficient.</p>Cassandra Batch Too Large Warning: How To Fix Ithttps://www.netdata.cloud/guides/cassandra/cassandra-batch-too-large-warning/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-batch-too-large-warning/<p>Oversized <code>BEGIN BATCH</code> statements cause <code>Batch for [ks.table] is of size N, exceeding specified threshold of M by ...</code> warnings and coordinator OutOfMemoryError. Unlike single-partition batches, which provide atomicity within one partition, multi-partition batches force the coordinator to hold mutation buffers for every affected partition until all replicas acknowledge. When the buffer grows large enough, it triggers heap pressure, long GC pauses, and eventual OOM.</p> <p>Cassandra batches are not a bulk-loading optimization. A logged batch spanning many partitions requires the coordinator to write a batchlog to two additional nodes before forwarding mutations, then retain every mutation in memory until each replica responds. The <code>batch_size_warn_threshold_in_kb</code> and <code>batch_size_fail_threshold_in_kb</code> settings in cassandra.yaml exist to protect the coordinator from this memory pressure. Treat every batch size warning as a pre-incident signal: once the coordinator heap fills, Old Generation collections lengthen, gossip heartbeats miss their phi accrual threshold, and peers mark the node DOWN. After recovery, client retries and hinted handoff replays drive further GC pressure in a feedback loop.</p>Cassandra Commit Log Disk Full: How To Fix Ithttps://www.netdata.cloud/guides/cassandra/cassandra-commitlog-disk-full/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-commitlog-disk-full/<p>WriteTimeoutException from client drivers, a node still UP in gossip, and a commitlog volume nearing 100% with climbing commitlog or flush tasks in <code>nodetool tpstats</code> mean commitlog segment exhaustion. Unlike data disk exhaustion, which slows compaction, commitlog pressure blocks the write path directly: every mutation must be durably appended to the WAL before acknowledgment.</p> <p>Cassandra recycles commitlog segments only after all memtables they reference are flushed to SSTables. When the flush pipeline cannot keep pace, segments accumulate until the total size exceeds <code>commitlog_total_space</code> (or <code>commitlog_total_space_in_mb</code> on older versions) or the filesystem fills. Cassandra then forces flushes of every dirty column family referenced in the oldest segment to free space. If flushes are already backed up, this cascades into blocked segment allocation, dropped mutations, and depending on <code>commit_failure_policy</code>, a node that stops accepting writes entirely.</p>Cassandra commitlog pending tasks: write-path I/O pressurehttps://www.netdata.cloud/guides/cassandra/cassandra-commitlog-pending-tasks/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-commitlog-pending-tasks/<p>Sustained non-zero CommitLog PendingTasks means a Cassandra node&rsquo;s write path is backing up. Every write must be appended to the commitlog and synced to disk before the coordinator acknowledges it. When the fsync thread cannot keep up, mutations queue. This starts as elevated write latency; if the queue persists, it forces emergency memtable flushes, overwhelms the flush and compaction pipeline, and produces dropped mutations.</p> <p>This is a durability bottleneck that affects every write replica-wide. Because the commitlog sits at the start of the write path, a slowdown cascades predictably: delayed acknowledgments, segment allocation pressure, forced flushes, then load shedding. The root cause is almost always I/O saturation on the commitlog device, an undersized or shared disk, or a mismatch between <code>commitlog_sync</code> mode and hardware.</p>Cassandra compaction death spiral: when writes outrun compaction throughputhttps://www.netdata.cloud/guides/cassandra/cassandra-compaction-death-spiral/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-compaction-death-spiral/<p>P99 read latency climbs while disk utilisation on the data volume pins near 100%. <code>nodetool compactionstats</code> shows pending tasks rising hour over hour, and <code>nodetool tablestats</code> reports a growing SSTable count. Writes stay fast; reads slow down. This is the compaction death spiral: writes exceed compaction throughput, SSTables accumulate, and read amplification rises.</p> <p>Unlike a sudden node crash, this failure is gradual. A background queue grows a little each day. Once disk I/O saturates, the cycle self-reinforces: compaction falls further behind, reads consult more files, latency spikes, and the backlog deepens. By the time client SLAs breach, recovery can take hours.</p>Cassandra compaction strategies: STCS vs LCS vs TWCS vs UCShttps://www.netdata.cloud/guides/cassandra/cassandra-choosing-compaction-strategy/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-choosing-compaction-strategy/<p>Compaction merges immutable SSTables, discards tombstones, and reclaims disk space. The strategy assigned to a table controls the tradeoff between write amplification and read amplification, and it determines how much temporary disk headroom you must preserve. A fit strategy keeps SSTable counts low and latency predictable. A mismatch creates compaction debt: creeping P99 read latency first, then disk space exhaustion, and finally write rejections when compaction cannot reclaim space fast enough to keep up with flushes.</p>Cassandra disk space exhaustion: emergency recovery when the data volume fillshttps://www.netdata.cloud/guides/cassandra/cassandra-disk-space-exhaustion/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-disk-space-exhaustion/<p>A Cassandra node that runs out of disk space does not degrade gracefully. Compaction halts because it cannot allocate temporary space to merge SSTables. Old SSTables are never deleted. Writes append to the commitlog until segment allocation blocks. At that point the node rejects mutations and <code>CommitLog.WaitingOnSegmentAllocation</code> climbs. You may see <code>No space left on device</code> errors while the data volume still reports a few percent free, because Cassandra&rsquo;s internal headroom requirements are stricter than the filesystem.</p>Cassandra dropped mutations: silent write loss and load sheddinghttps://www.netdata.cloud/guides/cassandra/cassandra-dropped-mutations/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-dropped-mutations/<p>Your application logs successful writes, but reads return stale or missing data. An alert fires on <code>DroppedMessage</code> rate for <code>MUTATION</code> scope. The client never received an error, yet a replica discarded the write after it sat in the <code>MutationStage</code> queue past timeout. This is Cassandra load shedding. Silent write loss occurs whenever not enough other replicas succeed to meet the consistency level.</p> <p>Dropped mutations are a lagging indicator. By the time they appear, the replica is already choking on commitlog I/O, CPU starvation, GC pauses, or thread pool exhaustion. The <code>DroppedMessage</code> counter is cumulative since JVM start; a single large value means nothing unless the rate is increasing. Any sustained non-zero rate is abnormal and demands immediate investigation.</p>Cassandra dropped reads and other messages: reading nodetool tpstats Droppedhttps://www.netdata.cloud/guides/cassandra/cassandra-dropped-reads-and-messages/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-dropped-reads-and-messages/<p>When <code>nodetool tpstats</code> reports non-zero values in the Dropped section, the node discarded internal messages that exceeded their stage timeout. These counters are cumulative since JVM startup, not rates. A non-zero value warrants investigation: the timeout is defined in <code>cassandra.yaml</code> by settings such as <code>read_request_timeout_in_ms</code> and <code>write_request_timeout_in_ms</code>, so a drop means the message sat in the queue for seconds.</p> <p>Dropped messages are a lagging indicator. Correlate the drop type with the matching thread pool pending count, disk I/O latency, and GC pause duration to find the root cause.</p>Cassandra GC death spiral: long pauses, gossip flapping, and recoveryhttps://www.netdata.cloud/guides/cassandra/cassandra-gc-death-spiral/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-gc-death-spiral/<p>You are paged because a Cassandra node is flapping between UP and DOWN in <code>nodetool status</code>, client timeouts are rising, and system logs show <code>GCInspector</code> warnings. The node has not crashed. It is stuck in a GC death spiral: heap pressure produces long pauses, gossip marks the node DOWN, and the resulting retry and hint traffic creates even more heap pressure when the node recovers. It can start with a single large partition read, a misconfigured cache, or an oversized batch statement, and escalates until the node is effectively useless. Catch it early by watching the GC floor and gossip stability together, not just process uptime.</p>Cassandra GC pauses too long: diagnosing G1 stop-the-world pauseshttps://www.netdata.cloud/guides/cassandra/cassandra-gc-pauses-too-long/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-gc-pauses-too-long/<p><code>ReadTimeoutException</code> and <code>WriteTimeoutException</code> from clients, <code>GCInspector</code> warnings in <code>system.log</code>, and nodes flapping between <code>UP</code> and <code>DOWN</code> in <code>nodetool status</code> without a JVM restart mean G1 is producing long stop-the-world pauses. Root causes include promotion pressure, humongous objects, or allocation bursts. Left unchecked, one node&rsquo;s pauses trigger gossip failures, retries, and hint replay that drive cluster-wide degradation.</p> <h2 id="what-this-means">What this means</h2> <p>G1GC is the default collector for Cassandra 4.x on JDK 11+. During a stop-the-world pause, every thread freezes, including gossip, native transport, and compaction. Cassandra logs <code>GCInspector</code> warnings when a pause exceeds the configured threshold, with a default <code>gc_warn_threshold_in_ms</code> of 1000 ms. Pauses longer than ~2 seconds cause gossip rounds to be missed; under the default phi accrual failure detector threshold of 8, sustained pauses result in the node being marked DOWN by the failure detector. While the JVM is paused, mutations queue, reads stall, hints accumulate on peers, and clients retry. On recovery, hint replay and retry bursts raise allocation pressure, creating a self-reinforcing spiral.</p>Cassandra gossip flapping: nodes bouncing UP and DOWNhttps://www.netdata.cloud/guides/cassandra/cassandra-gossip-flapping/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-gossip-flapping/<p><code>nodetool status</code> shows a node flipping between <code>UN</code> and <code>DN</code>, or multiple nodes doing it in sequence. Each transition forces the cluster to replay hints, recalculate read repair, and propagate gossip state. When a node transitions more than three times in thirty minutes, you are dealing with gossip flapping. It is almost always JVM heap pressure or GC pauses misdiagnosed as a network problem.</p> <p>Cassandra&rsquo;s phi accrual failure detector uses a sliding window of heartbeat inter-arrival times. With the default <code>phi_convict_threshold</code> of 8, a node must miss gossip heartbeats for roughly 18 seconds before peers mark it DOWN. A single long GC pause can cross that threshold. When the pause ends, the node resumes gossip, peers mark it UP, hint delivery begins, and the cycle repeats. The result is a self-reinforcing spiral: redirected traffic and hint replay create more memory pressure, which triggers longer pauses.</p>Cassandra heap pressure: sizing the JVM heap and tuning G1GChttps://www.netdata.cloud/guides/cassandra/cassandra-heap-pressure-tuning/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-heap-pressure-tuning/<p>Cassandra runs as a single JVM process per node. Every write path allocation, memtable mutation, read merge buffer, and cache entry lives on the heap. When the heap is undersized or GC is left at JVM defaults, stop-the-world pauses freeze gossip, client requests, and compaction. A pause longer than roughly 18 seconds (the default phi accrual threshold is 8) causes peers to mark the node DOWN, which triggers hinted handoff, replay storms, and client retries that worsen memory pressure: the GC death spiral.</p>Cassandra hint overflow: max_hint_window expiry and silent data divergencehttps://www.netdata.cloud/guides/cassandra/cassandra-hint-overflow/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-hint-overflow/<p>You restart a node after a four-hour outage. Gossip converges, <code>nodetool status</code> shows <code>UN</code>, and clients reconnect. Reads at consistency level <code>ONE</code> return stale data. The node has never been repaired.</p> <p>The problem is hint overflow: the outage lasted longer than <code>max_hint_window_in_ms</code> (default three hours), so coordinators stopped saving hints after the window expired. Writes accepted during the final hour of the outage are missing from that replica. Coordinator logs show no errors; write acknowledgments succeeded because other replicas responded. Only anti-entropy repair closes the gap. Without it, the missing data sits on that replica indefinitely, surfacing as inconsistent reads or resurrected deletes.</p>Cassandra hints accumulating: hinted handoff backlog and replay stormshttps://www.netdata.cloud/guides/cassandra/cassandra-hints-accumulating/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-hints-accumulating/<p>A coordinator node triggers a disk alert for <code>/var/lib/cassandra/hints</code>, or a replica returning from maintenance flaps UP/DOWN under a write burst it never requested. Hints let writes succeed when a replica is temporarily unreachable, but a large backlog turns that safety net into a secondary failure. Hints consume coordinator disk, expire after <code>max_hint_window_in_ms</code>, and can synchronize into a replay storm that overwhelms a recovering node.</p> <p>The root cause is almost always a DOWN or unreachable node, but the damage spreads to coordinators holding the backlog and then back to the recovering replica. You may discover it as disk exhaustion, gossip flapping, or inconsistent reads after an outage that exceeded the hint window. Unlike dropped mutations, hints appear benign at first: the cluster accepts writes and clients see no errors. The cost is deferred to the moment the missing replica returns, when every coordinator that buffered mutations replays them at once. If the backlog is large and the target is fragile, that deferred cost can exceed the original outage.</p>Cassandra hot partition: when one key saturates a replica sethttps://www.netdata.cloud/guides/cassandra/cassandra-hot-partition/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-hot-partition/<p>One or two nodes run hot while the rest of the cluster idles. Client P99 latency doubles or triples, but the average looks fine. Timeouts cluster on a subset of hosts, and <code>nodetool status</code> shows uneven load that does not match token ring expectations. When you trace requests, a single partition key consumes a disproportionate share of reads or writes. This is a hot partition: the partitioner mapped one key to a narrow token range, and the replicas owning that range are saturated.</p>Cassandra java.lang.OutOfMemoryError: Java heap space - causes and recoveryhttps://www.netdata.cloud/guides/cassandra/cassandra-out-of-memory-error/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-out-of-memory-error/<p>The error <code>java.lang.OutOfMemoryError: Java heap space</code> in Cassandra system logs means the JVM exhausted its allocated heap and could not satisfy an allocation request. The process typically exits, or the Linux OOM killer terminates it. Gossip marks the node DOWN, clients experience timeouts, and the remaining replicas absorb the orphaned traffic.</p> <p>Unlike gradual GC pressure that degrades latency over hours, a heap-space OOM is often a hard stop. The node was serving traffic, then it was not. The challenge is not recognizing the failure (the error string is unambiguous) but finding which of several competing heap consumers caused it.</p>Cassandra killed by the Linux OOM killer: off-heap memory and RSShttps://www.netdata.cloud/guides/cassandra/cassandra-off-heap-oom-kill/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-off-heap-oom-kill/<p>The JVM heap chart shows 50% utilization and a flat line. There is no <code>OutOfMemoryError</code>. Then the Cassandra process vanishes. <code>dmesg</code> shows the OOM killer terminated the JVM: <code>Killed process 12345 (java)</code>. The JVM heap metric does not include native allocations: bloom filters, compression metadata, index summaries, direct buffers, and chunk cache. When heap plus off-heap RSS exceeds available RAM, the kernel kills the process. This guide covers how to confirm that pattern, reduce off-heap footprint, and prevent recurrence.</p>Cassandra large partition pathology: Compacting large partition warnings and readshttps://www.netdata.cloud/guides/cassandra/cassandra-large-partition/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-large-partition/<p>If <code>system.log</code> prints <code>Compacting large partition ks/table:key (N bytes)</code> and reads to the affected table are spiking, a single partition has crossed <code>compaction_large_partition_warning_threshold_mb</code> (default 100 MB). Oversized partitions force the node to deserialize a large in-memory index on reads, rewrite the entire partition during compaction, and move it atomically during streaming or repair. Left alone, the partition grows until it triggers GC pauses, gossip flapping, and cascading retries. Use this guide to confirm the offending key, measure the blast radius, and choose between immediate relief and a data-model fix.</p>Cassandra Monitoringhttps://www.netdata.cloud/monitoring-101/cassandra-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/cassandra-monitoring/<h2 id="cassandra-monitoring">Cassandra Monitoring</h2> <p>Apache Cassandra, an open-source NoSQL database management system renowned for its scalability and high availability, is pivotal to many organizations running large-scale data infrastructures. Efficiently monitor Cassandra to ensure its optimal performance and reliability.</p> <h3 id="what-is-cassandra">What Is Cassandra?</h3> <p>Cassandra is a highly scalable, distributed NoSQL database system designed to manage large amounts of structured data across many commodity servers, providing high availability with no single point of failure. It&rsquo;s specifically used for critical applications needing reliability at large scale. <a href="https://cassandra.apache.org/_/index.html">Learn more about Cassandra</a>.</p>Cassandra monitoring checklist: the signals every production cluster needshttps://www.netdata.cloud/guides/cassandra/cassandra-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-monitoring-checklist/<p>This checklist maps the signals a production Apache Cassandra cluster needs at four levels of monitoring maturity: survival, operational, mature, and expert. Each level is cumulative. A cluster at &ldquo;mature&rdquo; that does not alert on dropped mutations or node DOWN states has a survival-level gap, not a mature-level gap.</p> <p>The levels correspond to how quickly you can detect and diagnose problems. Survival signals tell you something is broken. Operational signals tell you what is degraded. Mature signals tell you why. Expert signals let you predict failures before they happen. Most teams operate at Level 1 or Level 2, learn about Level 3 after their first major incident, and only reach Level 4 after repeated outages that Level 3 should have caught.</p>Cassandra native transport not running: node UP in gossip but refusing CQL clientshttps://www.netdata.cloud/guides/cassandra/cassandra-native-transport-not-running/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-native-transport-not-running/<p>A node reports <code>UN</code> in <code>nodetool status</code> but rejects CQL connections on port 9042. Gossip and replication are healthy; the failure is isolated to the native transport layer.</p> <p>Because the node remains in the token ring, it continues to handle internode replication, gossip, and streaming. Applications see it as down; the cluster sees it as up. The JMX attribute <code>NativeTransportRunning</code> on <code>org.apache.cassandra.db:type=StorageService</code> is <code>false</code> while gossip heartbeats continue. The usual triggers are <code>nodetool disablebinary</code> left active after maintenance, or a firewall blocking TCP 9042.</p>Cassandra node showing DN in nodetool status: gossip, phi, and recoveryhttps://www.netdata.cloud/guides/cassandra/cassandra-node-down-nodetool-status/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-node-down-nodetool-status/<p>You run <code>nodetool status</code> and one of your nodes shows <code>DN</code> (Down/Normal). Before you restart anything, understand that this output is the local node&rsquo;s opinion, not global truth. In Cassandra&rsquo;s peer-to-peer architecture, every node runs its own phi accrual failure detector over gossip heartbeats. A <code>DN</code> mark means this specific observer has not heard from the target for roughly 18 seconds at default settings. Another node in the same cluster may still show the same target as <code>UN</code>.</p>Cassandra Not enough space for compaction: STCS space amplification and recoveryhttps://www.netdata.cloud/guides/cassandra/cassandra-not-enough-space-for-compaction/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-not-enough-space-for-compaction/<p><code>Not enough space for compaction</code> in <code>system.log</code> means STCS has hit a structural space-amplification limit. Disk usage may already be above 50%. Cassandra aborts the compaction, skips the tier, and leaves tombstones and old versions unmerged. SSTable count rises, read amplification increases, and free space stops being reclaimed. Left unchecked, this enters a compaction death spiral that ends in write rejection or disk exhaustion. Recovery requires immediate free space, targeted cleanup, and a headroom plan that accounts for transient STCS amplification.</p>Cassandra OperationTimedOutException: client-side timeouts vs server timeoutshttps://www.netdata.cloud/guides/cassandra/cassandra-operation-timed-out-exception/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-operation-timed-out-exception/<p><code>OperationTimedOutException</code> (driver 3.x) or <code>DriverTimeoutException</code> (driver 4.x) means the driver gave up before the coordinator responded. This is distinct from a server-side <code>ReadTimeout</code> or <code>WriteTimeout</code>, where the coordinator explicitly errors because replicas were too slow. Confusing the two leads to tuning the wrong timeout, masking a server capacity problem or adding unnecessary client latency. Use server-side signals and driver behavior to tell them apart.</p> <p>When the driver timer fires first, the coordinator may still be processing the request. For writes, the mutation can be committed on some replicas even though the client sees an exception. When the server timer fires first, the coordinator returns a <code>READ_TIMEOUT</code> or <code>WRITE_TIMEOUT</code> to the driver. The diagnostic path and fix differ for each case.</p>Cassandra pending compactions growing: the compaction backlog runbookhttps://www.netdata.cloud/guides/cassandra/cassandra-pending-compactions-growing/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-pending-compactions-growing/<p>Pending tasks climbing in <code>nodetool compactionstats</code> is normal after a bulk load under STCS, but when the number trends upward for hours it signals that your node is producing SSTables faster than compaction can merge them.</p> <p>This is the leading indicator of the compaction death spiral. Left unchecked, the backlog drives read amplification up, saturates disk I/O, and eventually exhausts disk space as temporary compaction files accumulate. Writes often stay fast while reads degrade, masking the problem.</p>Cassandra ReadTimeoutException: diagnosing coordinator read timeoutshttps://www.netdata.cloud/guides/cassandra/cassandra-read-timeout-exception/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-read-timeout-exception/<p>The driver throws <code>ReadTimeoutException</code> when the coordinator fails to gather enough replica responses within <code>read_request_timeout_in_ms</code> (default 5000 ms). This is a server-side timeout. It maps directly to the JMX metric <code>ClientRequest,scope=Read,name=Timeouts</code>.</p> <p>This is not <code>OperationTimedOutException</code>, which fires on the driver&rsquo;s socket timeout. It is also not <code>UnavailableException</code>, which means not enough replicas were alive to attempt the read. Here, replicas are alive but too slow. The read may have executed partially on some replicas, yet the coordinator could not assemble a response that met the consistency level within the window.</p>Cassandra repair not running: the silent gap that resurrects deleted datahttps://www.netdata.cloud/guides/cassandra/cassandra-repair-not-running/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-repair-not-running/<p>Deleted rows reappear in application queries, or <code>system_distributed.repair_history</code> shows a last success older than your <code>gc_grace_seconds</code> window. In Cassandra, a repair that is not running, not completing, or not scheduled is an active data integrity risk.</p> <p>Cassandra uses tombstones to track deletions and TTL expirations. Those tombstones must survive on every replica until anti-entropy repair propagates the delete. Once <code>gc_grace_seconds</code> passes, compaction drops tombstones. If repair has not finished for a table within that window, nodes that missed the original delete retain live data while the rest have discarded the tombstone. The result is zombie data resurrection.</p>Cassandra Scanned over N tombstones warning: finding the offending queryhttps://www.netdata.cloud/guides/cassandra/cassandra-scanned-over-tombstones-warning/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-scanned-over-tombstones-warning/<p>Your application latency may still look acceptable at the median, but <code>system.log</code> is filling with warnings like <code>Read 500 live rows and 12000 tombstone cells for query SELECT ...</code> or <code>Scanned over 5000 tombstones</code>. These messages mean a single read is sifting through thousands of delete markers to return a small result set. Each tombstone consumes CPU, disk I/O, and heap memory during the merge phase. Left alone, the same query will eventually cross <code>tombstone_failure_threshold</code> (default 100000) and be aborted by the coordinator. The log line gives you the query text, but the real operational work is deciding whether the root cause is a missing repair, a compaction backlog, or a data model mismatch, and then confirming which partition is the actual source of the dead data.</p>Cassandra TombstoneOverwhelmingException: reads aborted by tombstone_failure_thresholdhttps://www.netdata.cloud/guides/cassandra/cassandra-tombstone-overwhelming-exception/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-tombstone-overwhelming-exception/<p>TombstoneOverwhelmingException is a hard stop. Cassandra aborts the read after scanning more tombstones than <code>tombstone_failure_threshold</code> allows. The default is 100000 tombstones per query. When this exception hits a production table, client reads fail outright.</p> <p>Without the threshold, a tombstone-heavy read pins cores, saturates disk I/O, and triggers GC pauses that cascade into gossip flapping or OOM. The exception is a circuit breaker. It is also a signal that tombstones are accumulating faster than compaction can purge them, or that the data model is generating them faster than the storage engine can remove them.</p>Cassandra Too many open files: file descriptor exhaustionhttps://www.netdata.cloud/guides/cassandra/cassandra-too-many-open-files/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-too-many-open-files/<p>Your application starts logging connection timeouts or <code>Unable to connect</code> errors, yet <code>nodetool status</code> still marks the node as UP. Inside the Cassandra system log, you see <code>java.io.IOException: Too many open files</code> or compaction tasks failing with <code>Cannot open enough files</code>. This is file descriptor exhaustion. The node operates normally until it hits the process ulimit, then it cannot open new SSTables, accept client sockets, or maintain internode connections. The result is a node that looks alive in gossip but is functionally unable to serve reads, writes, or background compaction.</p>Cassandra too many SSTables per table: read amplification and how to fix ithttps://www.netdata.cloud/guides/cassandra/cassandra-too-many-sstables/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-too-many-sstables/<p>Your Cassandra read P99 latency is climbing. Queries that used to take milliseconds now time out. The application reports intermittent <code>ReadTimeoutException</code>. You check <code>nodetool tablestats</code> and see one table sitting at 200 SSTables. For STCS, anything sustained above 50 means compaction has fallen behind. For LCS, the total count matters less than the distribution — 200 SSTables stranded in L0 is a catastrophe, while 200 spread across L1-L2 may be normal.</p>Cassandra UnavailableException: not enough replicas for the consistency levelhttps://www.netdata.cloud/guides/cassandra/cassandra-unavailable-exception/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-unavailable-exception/<p>Cassandra threw <code>UnavailableException</code>. The coordinator rejected the request immediately without contacting replicas. No mutation occurred, and retrying at the same consistency level against the same coordinator fails until enough replicas are <code>UN</code> in the coordinator&rsquo;s gossip view. This is a topology problem, not a performance problem.</p> <p>This exception is qualitatively different from <code>TimeoutException</code>. A timeout means enough replicas were alive but responded too slowly. An unavailable means the coordinator never sent the request because the topology could not satisfy the consistency level.</p>Cassandra zombie data resurrection: gc_grace_seconds and unrepaired tombstoneshttps://www.netdata.cloud/guides/cassandra/cassandra-data-resurrection-gc-grace/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cassandra/cassandra-data-resurrection-gc-grace/<p>A query returns rows that were deleted weeks ago. Application logs show no errors. All nodes report UP in <code>nodetool status</code>. Compaction is running and disk usage looks normal. The data is back because a tombstone was compacted away before anti-entropy repair verified that every replica saw the delete. Once the tombstone is gone, live data on unrepaired replicas is treated as authoritative. The next repair or read repair streams it back to the tombstone-less nodes.</p>Celery Monitoringhttps://www.netdata.cloud/monitoring-101/celery-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/celery-monitoring/<h2 id="celery-monitoring">Celery Monitoring</h2> <h3 id="what-is-celery">What Is Celery?</h3> <p>Celery is an open-source distributed task queue system designed to handle asynchronous tasks effectively. It’s built on a robust, flexible architecture and is commonly used in web development to manage scheduled tasks and ease resource consumption. It functions using a producer/consumer pattern, with workers executing jobs and a message broker dispatching them. Celery is praised for its simplicity, scalability, and language-agnostic nature, making it a favorite among developers seeking reliable task management and distributed computing frameworks.</p>Ceph backfill_toofull: recovery blocked because target OSDs are fullhttps://www.netdata.cloud/guides/ceph/ceph-backfill-toofull/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-backfill-toofull/<p>A PG in <code>backfill_toofull</code> is not making progress toward <code>active+clean</code>. The source OSD has the data, CRUSH has chosen the target, but the target refuses the reservation because it is above <code>backfillfull_ratio</code>. Client reads and writes still succeed; the redundancy gap is not closing.</p> <p>The cluster is usually not at the hard <code>full</code> ratio (0.95 default). It is at <code>backfillfull</code> (0.90 default) on one or more individual OSDs, and that is enough to halt recovery for every PG whose up set includes them. Symptoms: HEALTH_WARN (or HEALTH_ERR on older releases), a flat degraded-object count, and recovery bytes/sec near zero.</p>Ceph blocked ops: client I/O stuck behind a single slow OSDhttps://www.netdata.cloud/guides/ceph/ceph-blocked-ops/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-blocked-ops/<p>A client writes an object. The primary OSD forwards sub-ops to its replicas, then waits for every replica to ack before it acks the client. If any one OSD in the acting set stalls, the whole op stalls. After <code>osd_op_complaint_time</code> (default 30 seconds) the OSD logs a slow op and the monitor raises <code>SLOW_OPS</code>. Past that boundary the op is effectively blocked, not merely slow. Clients time out and retry, which puts more ops in flight against the same stuck OSD.</p>Ceph BLUEFS_SPILLOVER: RocksDB metadata spilling onto the slow devicehttps://www.netdata.cloud/guides/ceph/ceph-bluestore-db-spillover/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-bluestore-db-spillover/<p>A small subset of OSDs shows periodic commit-latency spikes and slow ops while the rest of the cluster looks healthy. Capacity metrics are normal. SMART is clean. <code>ceph -s</code> reports <code>HEALTH_WARN</code>, and <code>ceph health detail</code> returns something like:</p> <pre tabindex="0"><code>BLUEFS_SPILLOVER 3 OSDs spilled over ~18 GiB metadata from &#39;db&#39; device (e.g. osd.12 spilled over 6.1 GiB metadata from &#39;db&#39; device) </code></pre><p>BlueStore&rsquo;s RocksDB metadata has outgrown its dedicated fast DB partition (SSD/NVMe) and is spilling onto the slow HDD data partition. Compaction that took milliseconds on flash now takes seconds on spinning disk. Between compaction cycles the OSD looks fine; during compaction it stalls. This is a cliff edge, not gradual degradation: the moment <code>slow_used_bytes</code> goes nonzero, latency steps up by one to two orders of magnitude on the affected OSDs.</p>Ceph capacity death spiral: an OSD fails and recovery has nowhere to gohttps://www.netdata.cloud/guides/ceph/ceph-capacity-death-spiral/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-capacity-death-spiral/<p>An OSD fails on a cluster you have been running at 80% or higher. <code>ceph -s</code> shows recovery starting, then <code>ceph health detail</code> lists <code>OSD_NEARFULL</code> and <code>BACKFILL_TOOFULL</code>. The degraded PG count climbs, then flatlines. Recovery bytes per second sits near zero. Nothing is healing, and you are one more failure away from data loss.</p> <p>This is the Ceph capacity death spiral. It is not a single fault: it is the intersection of tight capacity, CRUSH imbalance, and the hard thresholds Ceph uses to protect itself. Recovery needs spare space on the surviving OSDs. When those OSDs are already past the backfillfull ratio (default 0.90), Ceph refuses to push more data onto them, and backfill stalls for every PG that would target them.</p>Ceph degraded objects: reduced redundancy and the race against a second failurehttps://www.netdata.cloud/guides/ceph/ceph-degraded-objects/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-degraded-objects/<p>Degraded objects in Ceph are the most direct measure of reduced redundancy: somewhere in the cluster, at least one object has fewer live replicas (or fewer erasure-coded fragments) than its pool requires. The cluster is still serving I/O, but the protection against a follow-on failure has thinned for those objects.</p> <p><code>ceph_num_objects_degraded</code> is not alarming on its own. Every OSD failure, restart, and CRUSH reweight produces a transient spike that recovery is designed to heal. The real signal is the slope: is the count falling back toward zero, or has it plateaued while the cluster is still degraded?</p>Ceph FS_DEGRADED: standby MDS failed to take over a rankhttps://www.netdata.cloud/guides/ceph/ceph-fs-degraded/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-fs-degraded/<p><code>FS_DEGRADED</code> fires when at least one CephFS rank is <code>failed</code> or <code>damaged</code> and a standby did not promote. Clients can usually still reach the filesystem through surviving ranks, but you are running without the failover reserve the MDS cluster was sized to provide.</p> <p><code>FS_DEGRADED</code> is the precursor to <code>MDS_ALL_DOWN</code>. If the last active rank fails before you restore a healthy standby, CephFS becomes fully unavailable. The playbook classifies <code>FS_DEGRADED</code> active for more than 120 seconds as a TICKET. If CephFS is a primary storage interface, treat 120 seconds as the upper bound on response time, not a soft target.</p>Ceph HEALTH_ERR: reading the umbrella status and finding the real faulthttps://www.netdata.cloud/guides/ceph/ceph-health-err/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-health-err/<p><code>ceph_health_status == 2</code> is the most severe top-level status Ceph reports, and one of the most over-paged signals in production. The reason is structural: HEALTH_ERR is an umbrella aggregation. It tells you that one or more child health checks crossed into ERR severity. It does not tell you which subsystem failed, whether I/O is actually blocked, or whether the condition will self-resolve when PGs finish peering.</p> <p>Treating the umbrella as the page to action creates two failure modes. First, it duplicates the more specific child signals (<code>OSD_FULL</code>, PG down, MON quorum loss) that already have their own PAGE conditions with tighter gating, producing parallel escalations for the same incident. Second, it fires on transient cold-start states. A cluster-wide OSD restart will briefly push PGs through <code>peering</code> and <code>incomplete</code>, which trips HEALTH_ERR for tens of seconds before clearing. Operators who page on HEALTH_ERR without context spend their nights chasing ghosts.</p>Ceph LARGE_OMAP_OBJECTS: the RGW bucket-index OMAP storm and reshardinghttps://www.netdata.cloud/guides/ceph/ceph-large-omap-objects/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-large-omap-objects/<p>The <code>LARGE_OMAP_OBJECTS</code> health warning fires when a deep scrub finds a RADOS object carrying more OMAP keys than the configured threshold. On clusters running the RADOS Gateway (RGW), the most common trigger is the bucket-index shard: a single shard that has accumulated too many entries because a bucket holds millions of objects with too few index shards.</p> <p>Once a shard crosses the threshold, the symptoms cluster around two areas. RGW clients see slow LIST responses and slow multipart coordination on the affected bucket. The OSD hosting the shard shows elevated commit latency, slow ops, and in the worst case BlueStore RocksDB pressure that resembles a compaction stall. The OSD usually remains <code>up+in</code>, so cluster-level health stays at WARN rather than ERR, which makes the problem easy to overlook until a user complains about a stuck <code>ListObjects</code> call.</p>Ceph monitor quorum lost: the cluster can no longer update its mapshttps://www.netdata.cloud/guides/ceph/ceph-mon-quorum-lost/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-mon-quorum-lost/<p>Ceph monitor quorum loss is a PAGE condition. Without a majority of MONs agreeing through Paxos, the cluster cannot commit any map update: no OSD up/down transitions, no PG state changes, no pool edits, no CRUSH adjustments. Existing clients keep running on cached maps for a while, but new client connections fail immediately, and as soon as those cached maps go stale, in-flight I/O stalls.</p> <p>The trigger formula is <code>sum(ceph_mon_quorum_status) &lt; floor(count(ceph_mon_quorum_status) / 2) + 1</code>. For 3 MONs you need 2 in quorum. For 5 MONs you need 3. The standard alert sustain is 300 seconds, long enough to ride out a normal sub-second leader election and short enough to page before clients start timing out en masse.</p>Ceph Monitoringhttps://www.netdata.cloud/monitoring-101/ceph-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/ceph-monitoring/<h2 id="ceph-monitoring">Ceph Monitoring</h2> <h3 id="what-is-ceph">What Is Ceph?</h3> <p>Ceph is a distributed storage system designed to provide excellent performance, reliability, and scalability. It achieves this by distributing data across multiple storage devices and ensuring data redundancy. As an open-source project, Ceph has become a popular choice for managing petabytes of data because of its self-healing and self-managing capabilities.</p> <h3 id="monitoring-ceph-with-netdata">Monitoring Ceph With Netdata</h3> <p>Monitoring Ceph clusters effectively is crucial to maintaining their optimal performance and ensuring data availability. Netdata offers a comprehensive Ceph monitoring tool that provides real-time insights into your Ceph infrastructure. By using <a href="https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/ceph/">Netdata&rsquo;s collector for Ceph</a>, you can access granular metrics for your entire Ceph cluster, including individual Pools and OSDs.</p>Ceph monitoring checklist: the signals every production cluster needshttps://www.netdata.cloud/guides/ceph/ceph-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-monitoring-checklist/<p>This checklist defines the signals a production Ceph cluster needs, organized by monitoring maturity. Each level is a superset of the previous one; higher-level signals rely on lower-level context to distinguish real failures from normal churn. The four levels are survival, operational, mature, and expert. You cannot skip levels in practice.</p> <p>Two caveats apply across all levels. First, <code>ceph_health_status</code> is an umbrella, not a complete picture: HEALTH_OK does not guarantee performance, and HEALTH_WARN covers both expected churn (active recovery) and structural problems (nearfull, noout trap, scrub inconsistency). Drill into <code>ceph_health_detail</code> before treating WARN as noise. Second, per-OSD and per-pool metrics matter more than cluster averages. A cluster at 60% average capacity with one OSD at 85% is closer to trouble than the average suggests.</p>Ceph nearfull: the 85% warning that decides whether the cluster can healhttps://www.netdata.cloud/guides/ceph/ceph-osd-nearfull/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-osd-nearfull/<p><code>OSD_NEARFULL</code> or <code>POOL_NEAR_FULL</code> in <code>ceph health detail</code> means <code>HEALTH_WARN</code>. Clients are still reading and writing, and nothing looks broken yet. The nearfull ratio (default 0.85) is not a polite reminder to plan storage. It is the point where Ceph warns it is running out of the spare space it needs to heal itself.</p> <p>One OSD failure at 85% can push surviving OSDs past backfillfull (0.90), at which point backfills refuse to start and recovery stalls. If another OSD fails in that window, you are left with degraded PGs that cannot be recovered, and the next stop is <code>OSD_FULL</code> at 95% where all client writes return ENOSPC.</p>Ceph OSD down: telling a dead disk apart from a network bliphttps://www.netdata.cloud/guides/ceph/ceph-osd-down/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-osd-down/<p><code>OSD_DOWN</code> fires. <code>ceph_osd_up</code> flipped to 0. The 600-second countdown to OUT and recovery has begun.</p> <p>Your first job: figure out whether this is a dead disk (act now, plan a replacement) or a network blip (wait, verify, let the OSD come back). Acting on the wrong diagnosis wastes disk and network I/O on a needless backfill, or worse, leaves a failing disk in service past the point where SMART was already warning you.</p>Ceph OSD flapping: OSDs cycling up and down and the peering storm that followshttps://www.netdata.cloud/guides/ceph/ceph-osd-flapping/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-osd-flapping/<p>OSD flapping is a failure cascade. One OSD misses heartbeats, peers mark it down, its PGs start peering and recovering elsewhere, the OSD comes back, peering reverses, and the cycle repeats. Each flap mints a new OSD map epoch that every OSD in the cluster must process. The peering overhead from a single flapping OSD can slow dozens of healthy OSDs enough that they also miss heartbeats, and the cascade spreads.</p>Ceph OSD_FULL: all writes stopped at the 95% full ratiohttps://www.netdata.cloud/guides/ceph/ceph-osd-full/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-osd-full/<p>The cluster suddenly stops accepting writes. Client applications report ENOSPC errors. <code>ceph status</code> returns <code>HEALTH_ERR</code>. <code>ceph health detail</code> shows <code>OSD_FULL</code> active. Reads still succeed, but every write, update, and delete fails cluster-wide.</p> <p>This is a hard stop, not a throttle. Ceph refuses all write operations once any OSD crosses the configured <code>full_ratio</code> (default 0.95). CRUSH spreads every PG across multiple OSDs, so a single full OSD can block writes to hundreds of PGs even when cluster-average utilization looks moderate.</p>Ceph PG degraded: fewer replicas than the pool size, and when it mattershttps://www.netdata.cloud/guides/ceph/ceph-pg-degraded/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-pg-degraded/<p>A degraded placement group in Ceph has fewer copies of some objects than the pool&rsquo;s configured <code>size</code>. When an OSD goes down or is removed, every PG that had a replica on that OSD drops below target and enters the <code>degraded</code> state. The cluster can still serve I/O as long as the surviving replica count is at or above <code>min_size</code>, but redundancy is reduced until recovery rebuilds the missing copies.</p>Ceph PG down: no surviving replica for reads or writeshttps://www.netdata.cloud/guides/ceph/ceph-pg-down/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-pg-down/<p>A placement group in the <code>down</code> state has no replica that can serve I/O. Reads and writes to objects in that PG fail. Clients see EIO or ENODEV, and <code>ceph health detail</code> reports <code>PG_AVAILABILITY</code> with one or more PGs flagged <code>down</code>. Data is unavailable, not just degraded.</p> <p>A PG can briefly pass through <code>down</code> during peering after an OSD failure, before activating on a surviving replica. The 300-second sustain on <code>sum(ceph_pg_down) &gt; 0</code> filters that transient window. Once a PG has been <code>down</code> past the sustain, no OSD in the acting set can serve it, and the cluster will not heal it without operator action.</p>Ceph PG incomplete: placement groups that cannot serve I/Ohttps://www.netdata.cloud/guides/ceph/ceph-pg-incomplete/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-pg-incomplete/<p>An <code>incomplete</code> placement group means the PG cannot find enough authoritative data to serve reads or writes. This is a data-availability failure, and it does not self-resolve the way a transient <code>peering</code> or <code>recovering</code> state does.</p> <p>Alert on <code>sum(ceph_pg_incomplete) &gt; 0</code> sustained for more than 300 seconds, summed across all pools. The 300 second sustain filters out cold-start peering after a cluster-wide restart, which typically completes within 60-120 seconds. Anything still <code>incomplete</code> after five minutes is genuinely stuck.</p>Ceph PG inconsistent (OSD_SCRUB_ERRORS): scrub found replica divergencehttps://www.netdata.cloud/guides/ceph/ceph-pg-inconsistent/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-pg-inconsistent/<p>A scrub or deep-scrub finished comparing replicas for a placement group and found they disagree. The cluster surfaces this as <code>OSD_SCRUB_ERRORS</code> (often paired with <code>PG_DAMAGED</code>) and the affected PG sits in <code>active+clean+inconsistent</code>. Client reads still succeed because Ceph serves them from a consistent replica, but at least one copy in the acting set is corrupt.</p> <p>The danger is not the symptom. Reads work, and Ceph did what it was designed to do: detect silent divergence. The danger is that the corruption was found, not fixed, and the window during which an uncorrupted replica survives is your margin of safety. If the OSD holding the good copy fails before you repair, the object becomes unreadable or unwritable.</p>Ceph slow requests (SLOW_OPS): operations blocked past osd_op_complaint_timehttps://www.netdata.cloud/guides/ceph/ceph-slow-requests/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-slow-requests/<p><code>ceph_healthcheck_slow_ops</code> greater than zero means operations on the cluster have crossed <code>osd_op_complaint_time</code> (default 30s) and are stuck, not merely slow. The <code>SLOW_OPS</code> health check surfaces them as a warning, and the metric itself is a live gauge pulled from <code>ceph health detail</code>.</p> <p>Slow ops are a symptom of something downstream blocking I/O: a failing disk, a saturated BlueStore RocksDB DB, network timeouts between OSDs, or heavy deep-scrub on HDD during a maintenance window. The right first move is to read where in the pipeline each slow op is stuck before changing any config.</p>Ceph unfound objects: the cluster cannot locate a surviving copyhttps://www.netdata.cloud/guides/ceph/ceph-unfound-objects/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/ceph/ceph-unfound-objects/<p>When a placement group enters <code>recovery_unfound</code> or <code>backfill_unfound</code>, the cluster has objects it knows should exist but cannot locate on any OSD that is currently up and in. <code>ceph health detail</code> surfaces this as the <code>OBJECT_UNFOUND</code> check, and the cluster-wide gauge <code>ceph_num_objects_unfound</code> rises above zero. Every known replica or erasure-coded chunk is on an OSD that is down, destroyed, or has not yet been probed.</p> <p>Recovery of the affected PGs is blocked at the unfound object. Client reads and writes to those objects stall indefinitely rather than erroring out. The only paths forward are to bring back the missing data or to explicitly accept the loss.</p>Chia Monitoringhttps://www.netdata.cloud/monitoring-101/chia-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/chia-monitoring/<h2 id="chia-monitoring">Chia Monitoring</h2> <h3 id="what-is-chia">What Is Chia?</h3> <p>Chia is a blockchain and smart transaction platform designed to be eco-friendly through its innovative use of proof-of-space-and-time. It enables users to participate in the blockchain by utilizing free disk space instead of relying on energy-intensive proof-of-work.</p> <h3 id="monitoring-chia-with-netdata">Monitoring Chia With Netdata</h3> <p>Monitoring your Chia setup is essential for ensuring optimal performance and troubleshooting issues before they escalate. Netdata offers a Chia monitoring tool through a Prometheus exporter <a href="https://github.com/chia-network/chia-exporter">available here</a>. Netdata stands out because it can ingest data from any <a href="https://learn.netdata.cloud/docs/collecting-metrics/generic-collecting-metrics/prometheus-endpoint/?utm_source=website&amp;utm_content=monitoring101">Prometheus exporter</a>, turning this data into automated dashboards and alerts without requiring additional software such as Prometheus servers or Grafana. By using Netdata, you gain powerful insights into your Chia operations with minimal setup.</p>Christ Elektronik CLM5IP Monitoringhttps://www.netdata.cloud/monitoring-101/clm5ip-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/clm5ip-monitoring/<h2 id="christ-elektronik-clm5ip-monitoring">Christ Elektronik CLM5IP Monitoring</h2> <h3 id="what-is-christ-elektronik-clm5ip">What Is Christ Elektronik CLM5IP?</h3> <p>The Christ Elektronik CLM5IP power panel is an advanced instrument designed for monitoring and controlling power systems. It is widely used in industrial and IoT environments for its ability to collect extensive power usage data, ensure efficient energy management, and optimize performance.</p> <h3 id="monitoring-christ-elektronik-clm5ip-with-netdata">Monitoring Christ Elektronik CLM5IP With Netdata</h3> <p>Monitoring the Christ Elektronik CLM5IP power panel can provide invaluable insights into the energy usage and health of your systems. By using Netdata as a monitoring tool, you can leverage OpenMetrics through a Prometheus exporter, such as the <a href="https://github.com/christmann/clm5ip_exporter/">Christmann CLM5IP Exporter</a>, to collect metrics effortlessly. Netdata allows you to ingest data from any Prometheus exporter, providing automated dashboards, real-time alerts, and comprehensive analytics, all without the need for a Prometheus server or Grafana. This makes Netdata a versatile and powerful tool for monitoring Christ Elektronik CLM5IP.</p>Chrony Monitoringhttps://www.netdata.cloud/monitoring-101/chrony-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/chrony-monitoring/<h2 id="chrony-monitoring">Chrony Monitoring</h2> <h3 id="what-is-chrony">What Is Chrony?</h3> <p>Chrony is a versatile software suite for maintaining the system clock accuracy on your Linux distributions. Acting as an implementation of the Network Time Protocol (NTP), Chrony ensures your systems are synchronized to accurate time sources, which is crucial for various server operations. It is highly adaptive, providing swift synchronization capabilities, making it particularly beneficial for systems with sporadic network connectivity or those that endure extreme delays.</p>Cilium Agent Monitoringhttps://www.netdata.cloud/monitoring-101/cilium_agent-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/cilium_agent-monitoring/<h2 id="cilium-agent-monitoring">Cilium Agent Monitoring</h2> <h3 id="what-is-cilium-agent">What Is Cilium Agent?</h3> <p>Cilium is an open-source software package that provides networking, security, and load balancing for cloud-native environments like Kubernetes. The Cilium Agent is a key component within this framework, responsible for enforcing policies and facilitating complex networking requirements with simplicity and transparency.</p> <h3 id="monitoring-cilium-agent-with-netdata">Monitoring Cilium Agent With Netdata</h3> <p>To monitor Cilium Agent efficiently, Netdata employs an OpenMetrics (Prometheus) exporter. This integration allows Netdata to ingest valuable monitoring data directly from any Prometheus exporter. With Netdata, you don’t need a separate Prometheus server or Grafana setup. The tool provides automated dashboards and real-time alerts, streamlining the process of monitoring Cilium Agent metrics like network security and connectivity.</p>Cilium Operator Monitoringhttps://www.netdata.cloud/monitoring-101/cilium_operator-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/cilium_operator-monitoring/<h2 id="cilium-operator-monitoring">Cilium Operator Monitoring</h2> <h3 id="what-is-cilium-operator">What Is Cilium Operator?</h3> <p>Cilium Operator is a crucial component for Kubernetes network security management. It enhances Kubernetes networking by providing secure and transparent connections within your cluster. Whether you are a DevOps engineer or a Site Reliability Engineer (SRE), understanding the intricacies of the Cilium Operator and monitoring its performance can significantly enhance the security and efficiency of your deployments.</p> <h3 id="monitoring-cilium-operator-with-netdata">Monitoring Cilium Operator With Netdata</h3> <p>To effectively monitor Cilium Operator, Netdata uses an openmetrics (Prometheus) exporter. This seamless integration allows Netdata to ingest data from any Prometheus exporter. By doing so, you can access automated dashboards, alerts, and more—all without needing a separate Prometheus server or Grafana. This makes Netdata an ideal Cilium Operator monitoring tool, combining ease of use with powerful capabilities.</p>Cilium Proxy Monitoringhttps://www.netdata.cloud/monitoring-101/cilium_proxy-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/cilium_proxy-monitoring/<h2 id="cilium-proxy-monitoring">Cilium Proxy Monitoring</h2> <h3 id="what-is-cilium-proxy">What Is Cilium Proxy?</h3> <p>Cilium Proxy is a key component in modern network security and performance for Kubernetes environments. It acts as an intermediary that controls and processes requests and responses between different microservices, ensuring secure and efficient communication.</p> <h3 id="monitoring-cilium-proxy-with-netdata">Monitoring Cilium Proxy With Netdata</h3> <p>Monitoring Cilium Proxy is crucial for maintaining optimal network performance and security. Netdata offers an intuitive solution to monitor Cilium Proxy using an openmetrics (Prometheus) exporter. Netdata can seamlessly ingest data from any Prometheus exporter, providing automated dashboards, alerts, and insightful metrics without the need for a Prometheus server or Grafana. This allows DevOps teams to quickly troubleshoot issues and maintain seamless network operations using Netdata&rsquo;s unparalleled real-time monitoring capabilities.</p>ClamAV Daemon Monitoringhttps://www.netdata.cloud/monitoring-101/clamd-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/clamd-monitoring/<h2 id="clamav-daemon-monitoring">ClamAV Daemon Monitoring</h2> <h3 id="what-is-clamav-daemon">What Is ClamAV Daemon?</h3> <p>ClamAV Daemon is part of the ClamAV antivirus software toolkit, developed for detecting threats and viruses on various platforms. It plays a crucial role in ensuring the security of IT infrastructures by scanning files and attachments in real-time to prevent malware and other malicious threats from affecting your systems.</p> <h3 id="monitoring-clamav-daemon-with-netdata">Monitoring ClamAV Daemon With Netdata</h3> <p>Monitoring the ClamAV Daemon is seamless with <a href="https://www.netdata.cloud">Netdata</a>, as it utilizes an openmetrics (<em>Prometheus</em>) exporter to fetch real-time metrics. With Netdata, you can ingest data from any Prometheus exporter providing an automated setup with dashboards, alerts, and in-depth analytics, all without the need for setting up a Prometheus server or Grafana.</p>Clamscan Results Monitoringhttps://www.netdata.cloud/monitoring-101/clamscan-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/clamscan-monitoring/<h2 id="clamscan-results-monitoring">Clamscan Results Monitoring</h2> <h3 id="what-is-clamscan-results-monitoring">What Is Clamscan Results Monitoring?</h3> <p>Clamscan is a command-line utility used in conjunction with ClamAV for detecting malware on a system. Monitoring Clamscan results is crucial to ensure the effectiveness of your anti-malware efforts, track performance metrics, and maintain the security of your network. By keeping an eye on the data provided by Clamscan, IT admins, DevOps, and security personnel can act promptly in response to vulnerabilities or infections.</p>Clash Monitoringhttps://www.netdata.cloud/monitoring-101/clash-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/clash-monitoring/<h2 id="clash-monitoring">Clash Monitoring</h2> <h3 id="what-is-clash">What Is Clash?</h3> <p>Clash is a versatile and powerful proxy server designed for efficient network traffic management. It serves as an essential component in managing and troubleshooting network performance in today&rsquo;s complex IT environments. With various features designed to seamlessly handle traffic routing, Clash ensures that data flows are optimized, which is vital for maintaining network health and performance.</p> <h3 id="monitoring-clash-with-netdata">Monitoring Clash With Netdata</h3> <p>To effectively monitor Clash, Netdata offers a seamless integration using an openmetrics (prometheus) exporter. This integration allows technical teams—be it DevOps, SREs, Developers, IT admins, or engineers—to gain comprehensive insights into the performance of their Clash instances. Netdata can ingest data from any Prometheus exporter, providing users with automated dashboards, real-time alerts, and more, without the necessity of having a dedicated Prometheus server or Grafana setup. This makes it easier for users looking for a $name monitoring tool to implement and manage network performance monitoring efficiently.</p>ClickHouse Active Part Count Growing: How To Fixhttps://www.netdata.cloud/guides/clickhouse/clickhouse-active-part-count-growing/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-active-part-count-growing/<p>Rising <code>MaxPartCountForPartition</code> is the leading indicator for the most common ClickHouse production failure: parts accumulating faster than background merges can consolidate them. A single partition crossing 500 active parts means you have hours, not days, before inserts delay and eventually fail with <code>TOO_MANY_PARTS</code>.</p> <p>The thresholds are per-partition. A table with ten partitions at fifty parts each is healthy; one partition at 950 parts is approaching throttling. Projections create hidden parts inside the same table that count toward the same limits. Materialized views route inserts to separate target tables that can hit their own limits independently.</p>ClickHouse cannot connect to ZooKeeper/Keeper: diagnosing the coordination layerhttps://www.netdata.cloud/guides/clickhouse/clickhouse-keeper-connection-lost/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-keeper-connection-lost/<p>If <code>SELECT * FROM system.zookeeper WHERE path = '/'</code> fails, replicated tables flip to readonly, or <code>ON CLUSTER</code> DDL hangs, the coordination layer is broken. The server stays up and <code>GET /ping</code> returns <code>Ok.</code>, so liveness checks miss the problem. Partial degradation can escalate to a write outage if replicated tables cannot re-establish sessions.</p> <p>ClickHouse uses the coordination service for ReplicatedMergeTree leader election, replication log queues, insert deduplication, and distributed DDL. ClickHouse Keeper typically listens on port 9181; external ZooKeeper ensembles listen on 2181. The diagnostic path differs slightly, but the symptom is the same: ClickHouse cannot reliably complete coordination operations.</p>ClickHouse checksum mismatch and broken parts: detecting data corruptionhttps://www.netdata.cloud/guides/clickhouse/clickhouse-data-corruption-checksum-mismatch/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-data-corruption-checksum-mismatch/<p>ClickHouse logs showing <code>Checksum doesn't match</code>, <code>Broken part</code>, or similar errors indicate data corruption. Affected parts move to <code>system.detached_parts</code>. Queries may throw exceptions or return partial results. On replicated clusters, a replica with corrupt parts may lag because it cannot validate fetched parts. Corruption does not self-resolve. You must quarantine the bad part, identify the root cause, and rebuild the data from a healthy source or backup.</p> <p>ClickHouse stores every data part with checksum files covering column data, index files, and metadata. When the server reads a part during a query, merge, or replication fetch, it recomputes checksums and compares them against the stored values. A mismatch means the bytes on disk no longer match what was written. The server detaches the part, moving it out of the active dataset. If the table is replicated, the replica may attempt to re-fetch the part from a peer. If no healthy copy exists, the data is effectively lost. On standalone nodes, the only recovery path is external restore or re-ingestion.</p>ClickHouse DB::Exception: Too many parts - causes and fixeshttps://www.netdata.cloud/guides/clickhouse/clickhouse-too-many-parts/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-too-many-parts/<p>When logs show <code>DB::Exception: Too many parts (N with average size of S) in table 'T'. Merges are processing significantly slower than inserts</code> (exception code 252), INSERTs that succeeded yesterday are now failing. Data backs up in ingestors, message queues, or client buffers, and every retry adds load to a system already drowning in small files.</p> <p>At least one partition in a MergeTree table has exceeded the hard limit for active data parts, and background merges cannot consolidate them fast enough. Do not restart the server or raise the limit indefinitely. Reduce the part creation rate, remove blockers from the merge pipeline, and give background threads runway to catch up.</p>ClickHouse DelayedInserts climbing: the warning before too-many-partshttps://www.netdata.cloud/guides/clickhouse/clickhouse-delayed-inserts/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-delayed-inserts/<p>Insert latency is climbing and <code>system.events.DelayedInserts</code> is no longer flat. ClickHouse is sleeping during INSERT because at least one partition has crossed <code>parts_to_delay_insert</code>. The database still accepts writes, but injects a sleep before each insert commits. This is the warning window before hard failure. If the merge backlog is not resolved, <code>DelayedInserts</code> climbs until <code>RejectedInserts</code> starts ticking and clients receive <code>DB::Exception: Too many parts</code>.</p> <p><code>DelayedInserts</code> and <code>RejectedInserts</code> are cumulative counters in <code>system.events</code>. Alert on their rate of change, not absolute value. A sustained positive rate means the merge pipeline is losing to the insert pipeline.</p>ClickHouse disk space collapse: why merges need free space and how the spiral startshttps://www.netdata.cloud/guides/clickhouse/clickhouse-disk-space-collapse/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-disk-space-collapse/<p>Disk usage climbs from 75% to 85% over a week, then hits 90%. A few hours later ClickHouse rejects inserts, part counts spike, and the volume is at 98%. The system did not simply run out of space. It entered a self-reinforcing spiral where background merges, the mechanism that reclaims space, stalled because they needed free space to work.</p> <p>This guide covers the mechanics, early signals, and recovery steps.</p> <h2 id="what-this-means">What this means</h2> <p>ClickHouse stores data in immutable parts. Every INSERT creates one or more parts on disk. Background merges combine smaller parts into larger ones to maintain query performance and keep file counts low. A merge reads all source parts and writes a new merged part before deleting the sources, so it temporarily needs space for both the old and new data.</p>ClickHouse disk space monitoring: free_space, unreserved_space, and the 80% targethttps://www.netdata.cloud/guides/clickhouse/clickhouse-disk-space-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-disk-space-monitoring/<p>ClickHouse disk space is not a simple capacity gauge. Merges write new parts before deleting old ones, so free space is an operational dependency of the storage engine. Insufficient disk does not just mean &ldquo;running low&rdquo;: background merges stall, parts accumulate, and the system enters a self-reinforcing death spiral.</p> <p>This guide covers the <code>system.disks</code> metrics, why <code>unreserved_space</code> matters more than <code>free_space</code>, and operational targets that keep merges alive.</p> <h2 id="what-it-is-and-why-it-matters">What it is and why it matters</h2> <p>ClickHouse stores data in immutable parts. Every insert creates at least one part, and background merges continuously combine smaller parts into larger ones to keep query performance healthy and storage efficient. A merge reads all source parts in a partition, writes a new merged part to the same disk, and only then removes the sources. This means a single merge temporarily requires space for both the sources and the result.</p>ClickHouse distributed DDL stuck: ON CLUSTER queries that never finishhttps://www.netdata.cloud/guides/clickhouse/clickhouse-distributed-ddl-stuck/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-distributed-ddl-stuck/<p><code>ON CLUSTER</code> DDL is not atomic. The initiator writes a task into a shared queue in ZooKeeper or ClickHouse Keeper under <code>/clickhouse/task_queue/ddl/</code>. Each node pulls entries in order, executes the DDL locally, and reports status back. One slow, down, or misconfigured node can leave the entry unfinished forever, blocking all later DDL on that node and creating schema drift that is invisible until a replica rejects an insert or a subsequent ALTER fails.</p>ClickHouse full table scan: partition pruning failures and the primary keyhttps://www.netdata.cloud/guides/clickhouse/clickhouse-full-table-scan-no-partition-pruning/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-full-table-scan-no-partition-pruning/<p>A query that returned in milliseconds yesterday now takes minutes and saturates CPU. Check whether it is reading every row before you add vCPUs or shards. A missing filter on the partition key or a mismatch with the primary key prefix forces ClickHouse to open every part and scan every granule. Symptoms are runaway <code>read_rows</code> counts, tail latency spikes, and sustained CPU decompression that hardware scaling cannot fix.</p> <p>ClickHouse is not a row-store with dense B-tree indexes. It uses a sparse primary index built from the <code>ORDER BY</code> key and directory-level pruning via the <code>PARTITION BY</code> clause. When these are unused, the engine reads all column files, decompresses every granule, and filters row by row. <code>system.query_log</code> will show <code>read_rows</code> near the total table row count. The fix is in the query shape, not cluster size.</p>ClickHouse Keeper saturation spiral: too many tables, DDL storms, and cluster freezehttps://www.netdata.cloud/guides/clickhouse/clickhouse-keeper-saturation-spiral/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-keeper-saturation-spiral/<p>INSERTs fail. Replicated tables flip read-only. <code>ON CLUSTER</code> DDL hangs. <code>curl http://localhost:8123/ping</code> still returns <code>Ok.</code> and <code>SELECT 1</code> still works. This is Keeper saturation: the coordination layer is choking while liveness probes give false confidence.</p> <p>The spiral starts when ZooKeeper or ClickHouse Keeper cannot keep up with metadata load. Every replicated table registers znodes and watches. Every DDL operation adds more. Coordination latency climbs until heartbeat traffic cannot complete within the negotiated session timeout; sessions expire, replicas become read-only, and writes fail. Reconnecting nodes then trigger a thundering herd.</p>ClickHouse killed by the OOM killer: RSS, max_server_memory_usage, and cgroup limitshttps://www.netdata.cloud/guides/clickhouse/clickhouse-oom-killed-by-kernel/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-oom-killed-by-kernel/<p>You restart a pod and <code>kubectl describe pod</code> shows <code>Reason: OOMKilled</code> with exit code 137. Inside ClickHouse, <code>MemoryTracking</code> sits well below <code>max_server_memory_usage</code>, and <code>system.text_log</code> shows no warning. The process is gone, merges are dead, and replication queues are backing up.</p> <p>The Linux OOM killer targets RSS, not ClickHouse&rsquo;s internal <code>MemoryTracking</code>. Untracked allocations, jemalloc arena fragmentation, and cgroup accounting quirks create a persistent gap between what ClickHouse thinks it is using and what the kernel sees. In containerized environments, the cgroup OOM killer can evict the pod before ClickHouse ever triggers its own server-wide limit.</p>ClickHouse long-running queries: finding and killing the resource hoghttps://www.netdata.cloud/guides/clickhouse/clickhouse-long-running-queries/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-long-running-queries/<p>A query that should finish in seconds is still running after twenty minutes. Memory on the ClickHouse node is climbing, query latency has doubled, and you suspect a single query is holding resources it will never release. In ClickHouse, a long-running query can be a legitimate analytical job crunching terabytes, a Cartesian JOIN exploding in memory, or a GROUP BY that has spilled to disk and slowed to a crawl. Telling the difference determines whether you kill it or let it finish.</p>ClickHouse Memory limit (for query) exceeded: per-query limits and GROUP BY/JOIN blowupshttps://www.netdata.cloud/guides/clickhouse/clickhouse-memory-limit-for-query-exceeded/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-memory-limit-for-query-exceeded/<p><code>Code: 241. DB::Exception: Memory limit (for query) exceeded</code> means a single query&rsquo;s allocations breached the <code>max_memory_usage</code> ceiling. ClickHouse tracks memory in a hierarchy: server-wide, per-user, and per-query. The server kills the query to protect the rest of the workload.</p> <p>This differs from <code>Memory limit (total) exceeded</code> (server-level pressure) and <code>Memory limit (for user) exceeded</code> (profile-level pressure). A query-level breach usually stems from one of three patterns: a high-cardinality <code>GROUP BY</code>, an unbounded <code>DISTINCT</code>, or a <code>JOIN</code> that materializes more rows than expected.</p>ClickHouse Memory limit (total) exceeded - server-wide memory pressure and fixeshttps://www.netdata.cloud/guides/clickhouse/clickhouse-memory-limit-total-exceeded/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-memory-limit-total-exceeded/<p><code>Code: 241. DB::Exception: Memory limit (total) exceeded: would use X bytes (attempt to allocate chunk of C bytes), current RSS: Y bytes, maximum: Z bytes.</code> is the server-level cap, not a per-query limit. When ClickHouse&rsquo;s <code>MemoryTracking</code> hits <code>max_server_memory_usage</code> (effective default: 90% of physical RAM, because the setting defaults to 0 and is derived from <code>max_server_memory_usage_to_ram_ratio</code>), the server kills the heaviest running queries to protect the process. New and existing queries fail until memory drops. Find the largest memory consumer and stop it before the OOM killer does.</p>ClickHouse memory pressure death spiral: runaway queries, retries, and OOMhttps://www.netdata.cloud/guides/clickhouse/clickhouse-memory-pressure-death-spiral/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-memory-pressure-death-spiral/<p><code>MEMORY_LIMIT_EXCEEDED</code> errors climb in the query log. Queries that normally finish in seconds now take minutes or are killed outright. The ClickHouse process is near its memory limit, but killing the heaviest query only frees capacity for a moment before another query is killed. If the application retries immediately, pressure never drops. With spill-to-disk enabled, the bottleneck shifts to disk I/O, starving background merges and slowing the whole system.</p> <p>This is the memory pressure death spiral: a composite failure pattern where memory saturation triggers query termination or spill-to-disk, rising latency provokes retries, and repeated attempts keep memory pinned near the limit. The spiral ends with an OS-level OOM kill if internal tracker and cgroup limits are misaligned, or with a merge crisis if temporary disk files consume all I/O bandwidth.</p>ClickHouse merge death spiral: when parts accumulate faster than merges consolidatehttps://www.netdata.cloud/guides/clickhouse/clickhouse-merge-death-spiral/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-merge-death-spiral/<p>Insert latency climbs. Application logs show ClickHouse throttling writes. Eventually inserts fail with <code>Too many parts</code>. Disk usage rises even though ingestion volume is flat. The cluster is up but refusing writes.</p> <p>This is the merge death spiral: a self-reinforcing loop where parts accumulate faster than background merges consolidate them. Every INSERT creates immutable on-disk parts. Background merge threads combine smaller parts into larger ones to keep query performance healthy and part counts low. When insert pressure exceeds merge throughput, the backlog grows, merge overhead increases, and the system chokes on its own structure.</p>ClickHouse merges not keeping up: diagnosing a stalled or starved merge poolhttps://www.netdata.cloud/guides/clickhouse/clickhouse-merges-not-keeping-up/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-merges-not-keeping-up/<p>When insert latency climbs and <code>system.merges</code> is empty while active parts grow, the background merge pool is likely stalled or starved. ClickHouse relies on background merges to consolidate immutable parts after each INSERT. Without merges, parts accumulate: query scans open more files, memory pressure shifts to the mark cache and file descriptor tables, and the system approaches the <code>TOO_MANY_PARTS</code> threshold.</p> <p>A stalled pool is not always obvious. The server accepts queries, replication appears healthy, and the HTTP ping endpoint returns <code>Ok.</code>. The real signals are rising part counts per partition, insert delays, and a merge pool that is either fully occupied or idle. Because merges and mutations share the background pool, a heavy <code>ALTER UPDATE</code> or <code>ALTER DELETE</code> can silently monopolize the threads that should consolidate parts.</p>ClickHouse Monitoringhttps://www.netdata.cloud/monitoring-101/clickhouse-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/clickhouse-monitoring/<h2 id="clickhouse-monitoring">ClickHouse Monitoring</h2> <h3 id="what-is-clickhouse">What Is ClickHouse?</h3> <p><a href="https://clickhouse.com/">ClickHouse</a> is a columnar database management system (DBMS) known for its high performance in managing online analytical processing (OLAP) queries. It excels in processing large volumes of data, making it a popular choice for data analytics tasks. Understanding and monitoring the performance of ClickHouse can ensure that your systems are running efficiently and reliably.</p> <h3 id="monitoring-clickhouse-with-netdata">Monitoring ClickHouse With Netdata</h3> <p>Netdata provides a comprehensive &ldquo;ClickHouse monitoring tool&rdquo; that allows you to monitor ClickHouse instances in real-time, with insightful visuals and metabolism into the system&rsquo;s performances. You can easily integrate Netdata with ClickHouse by using the <a href="https://www.netdata.cloud/integrations/data-collection/databases/clickhouse/">go.d.plugin</a>, enabling automatic discovery and effortless setup.</p>ClickHouse monitoring checklist: the signals every production cluster needshttps://www.netdata.cloud/guides/clickhouse/clickhouse-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-monitoring-checklist/<p>ClickHouse failures usually begin as storage-structure debt: immutable parts accumulate faster than merges consolidate them, coordination sessions expire, or disk space drops below the threshold merges need to complete. Query latency degrades only after the crisis is hours old.</p> <p>This checklist groups monitoring signals into four maturity levels. Level 1 is the minimum viable instrumentation to avoid data loss and unavailability. Each subsequent level adds leading indicators that catch part accumulation, replication divergence, and memory pressure while they are still reversible. The signals are drawn from ClickHouse system tables and OS-level metrics. They apply to single-node, sharded, and replicated setups; replicated tables add ZooKeeper/Keeper signals that belong in Level 2.</p>ClickHouse mutation stuck: parts_to_do not decreasing and how to recoverhttps://www.netdata.cloud/guides/clickhouse/clickhouse-mutation-stuck/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-mutation-stuck/<p>Check <code>system.mutations</code> and find a mutation active for hours. <code>parts_to_do</code> has not moved in thirty minutes and parts are accumulating. Queries return, but insert latency climbs. On replicated tables, each replica processes mutations independently, so a stall on one node creates silent divergence while the rest of the cluster appears healthy.</p> <p>Mutations rewrite data parts to apply <code>ALTER UPDATE</code>, <code>ALTER DELETE</code>, or projection changes. They run sequentially per table and share the background merge and mutation pool with regular merges. A stalled mutation blocks subsequent mutations for that table and consumes threads needed for merges. The result is merge starvation, insert delays, and eventually <code>Too many parts</code> rejections.</p>ClickHouse mutations silently blocking merges: the hidden cause of part growthhttps://www.netdata.cloud/guides/clickhouse/clickhouse-mutations-blocking-merges/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-mutations-blocking-merges/<p>You are watching part counts climb on a ClickHouse node. <code>system.merges</code> shows active background tasks, health checks return Ok, and the log shows no mutation errors. Yet inserts are slowing and <code>MaxPartCountForPartition</code> is trending toward the delay threshold. The pool looks busy, so merges should be keeping up. They are not: some of those busy slots are mutations, and mutations starve merges silently.</p> <p>ClickHouse implements <code>ALTER UPDATE</code> and <code>ALTER DELETE</code> as <strong>mutations</strong>: asynchronous background jobs that rewrite matching data parts. Mutations and regular merges share the same <code>BackgroundMergesAndMutationsPool</code>. A mutation holds one pool slot for minutes to hours. If the backlog is large enough, merges fall behind insert-driven part creation and the system drifts toward the <code>Too many parts</code> threshold without logging a mutation-specific error.</p>ClickHouse No space left on device: emergency recovery when the data disk fillshttps://www.netdata.cloud/guides/clickhouse/clickhouse-no-space-left-on-device/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-no-space-left-on-device/<p>When ClickHouse returns <code>No space left on device</code> to client inserts or the server log fills with write errors, the situation is past a simple capacity alert. ClickHouse does not degrade gradually on a full disk. Background merges halt immediately because they require temporary free space to write combined parts before removing source files. Once merges stop, small insert parts accumulate, metadata overhead grows, and disk usage accelerates. TTL-based expiration also stops because TTL cleanup is executed by merges. ClickHouse system tables such as <code>system.query_log</code> and <code>system.part_log</code> are MergeTree tables that can grow unbounded and consume the remaining space.</p>ClickHouse query error rate high: reading exception codes 241, 252, and 999https://www.netdata.cloud/guides/clickhouse/clickhouse-query-error-rate-high/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-query-error-rate-high/<h2 id="what-this-means">What this means</h2> <p>ClickHouse logs failed queries to system.query_log with type = &lsquo;ExceptionWhileProcessing&rsquo; and a numeric exception_code. The FailedQuery counter in system.events increments for each failure. Keep the FailedQuery / Query ratio below 1%. A sustained climb above that threshold signals a systemic issue, not a few bad queries.</p> <p>The codes that dominate production incidents fall into five classes.</p> <ul> <li>241 MEMORY_LIMIT_EXCEEDED</li> <li>252 TOO_MANY_PARTS</li> <li>159 TIMEOUT_EXCEEDED (including distributed-query shard timeouts)</li> <li>999 / 210 KEEPER_EXCEPTION / NETWORK_ERROR</li> <li>60 / 81 UNKNOWN_TABLE / UNKNOWN_DATABASE</li> </ul> <pre class="mermaid" data-source="markdown-fence">flowchart TD A[Query error rate above 1 percent] --> B[Query system.query_log by exception_code] B --> C{Code 241} B --> D{Code 252} B --> E{Code 159} B --> F{Code 999 or 210} B --> G{Code 60 or 81} C --> H[Memory pressure or runaway query] D --> I[Merge crisis or too many parts] E --> J[Shard unavailable or network timeout] F --> K[ZooKeeper session loss or coordination failure] G --> L[Schema drift or missing table]</pre> <h2 id="common-causes">Common causes</h2> <table> <thead> <tr> <th>Cause</th> <th>What it looks like</th> <th>First thing to check</th> </tr> </thead> <tbody> <tr> <td>Runaway query or cache eviction</td> <td>Code 241 spike; MemoryTracking near server limit</td> <td>system.processes ordered by memory_usage</td> </tr> <tr> <td>Merge debt or insert micro-batching</td> <td>Code 252 spike; insert latency climbs before rejections</td> <td>system.parts per partition; system.events RejectedInserts</td> </tr> <tr> <td>Shard unavailable or slow replica</td> <td>Code 159 spike on distributed tables</td> <td>system.replicas absolute_delay and queue_size on target shards</td> </tr> <tr> <td>ZooKeeper / Keeper session loss</td> <td>Codes 999/210 spike; replicated tables become readonly</td> <td>system.zookeeper_connection is_expired; system.replicas is_session_expired</td> </tr> <tr> <td>Schema drift after deploy</td> <td>Codes 60/81 spike following a migration</td> <td>system.distributed_ddl_queue status; query text in system.query_log</td> </tr> </tbody> </table> <h2 id="quick-checks">Quick checks</h2> <p>Run these read-only queries to classify the failure.</p>ClickHouse query latency P99 spikes: tail latency, hot shards, and cold datahttps://www.netdata.cloud/guides/clickhouse/clickhouse-query-latency-p99-spikes/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-query-latency-p99-spikes/<p>Your ClickHouse cluster shows healthy average query latency, but users report intermittent timeouts. P99 spikes while P50 stays flat. This divergence is tail latency: a subset of queries is dramatically slower. In distributed clusters, the culprit is often a single hot shard or a replica serving stale data. In tiered storage, a query touching cold S3 data can be one to two orders of magnitude slower.</p> <p>ClickHouse tail latency does not degrade gracefully. A slow shard in a distributed query forces the coordinator to wait, inflating latency for every query that touches it. Cold cache after restart, part accumulation, and background merge I/O all produce the same symptom. The sections below distinguish the causes.</p>ClickHouse Replica is lost: SYSTEM RESTORE REPLICA and recovering a diverged replicahttps://www.netdata.cloud/guides/clickhouse/clickhouse-replica-is-lost/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-replica-is-lost/<p>You run <code>SELECT count()</code> on two replicas and get different results. Your application returns inconsistent aggregations depending on which node answers. The replication dashboard looks green: ZooKeeper sessions are active, <code>queue_size</code> is zero, and no replica is <code>readonly</code>. The replica has permanently lost parts, but ZooKeeper does not know because the loss happened outside the replication log. Silent divergence hides behind healthy metrics until queries start returning wrong results.</p> <h2 id="what-this-means">What this means</h2> <p>ClickHouse replicated tables coordinate through a shared log in ZooKeeper or ClickHouse Keeper. Each replica downloads parts and applies log entries independently. If parts disappear locally &ndash; for example through disk corruption, filesystem damage, or direct file deletion outside ClickHouse replication commands &ndash; the replica does not detect the absence unless a later log entry references that part. With no pending merge or fetch referencing the missing part, the replica reports an empty queue and continues serving queries with incomplete data. Load balancers keep routing traffic to it.</p>ClickHouse replication lag: absolute_delay, queue_size, and catch-up diagnosishttps://www.netdata.cloud/guides/clickhouse/clickhouse-replication-lag/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-replication-lag/<p>You notice <code>absolute_delay</code> climbing on one replica. SELECTs there return older rows than on peers, and failover to the lagging node risks losing recently inserted data. In ClickHouse, replication lag is not a single failure; it is a symptom with several distinct causes. A replica can fall behind because it cannot pull entries from the Keeper log, because it cannot fetch parts fast enough, because a mutation is blocking the queue, or because the source replica itself is too slow to serve data.</p>ClickHouse replication queue stuck: num_tries, last_exception, and dead entrieshttps://www.netdata.cloud/guides/clickhouse/clickhouse-replication-queue-stuck/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-replication-queue-stuck/<p>A replica can show low <code>absolute_delay</code> in <code>system.replicas</code> while <code>system.replication_queue</code> contains entries with <code>num_tries</code> in the hundreds and the same <code>last_exception</code> repeating for hours. These dead entries do not self-resolve. They block merges, fetches, or mutations, causing silent divergence and stale reads. This guide shows how to read the queue correctly, identify the failure mode from the entry type, and clear the blockage without making the replica diverge further.</p> <h2 id="what-this-means">What this means</h2> <p>In ReplicatedMergeTree, each replica maintains a local <code>system.replication_queue</code> of operations from the shared replication log.</p>ClickHouse small inserts anti-pattern: why single-row inserts melt the merge poolhttps://www.netdata.cloud/guides/clickhouse/clickhouse-small-inserts-anti-pattern/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-small-inserts-anti-pattern/<p><code>DB::Exception: Too many parts</code> spikes, query latency climbs, and the background merge pool runs flat out while making no progress. Disk, CPU, and memory look healthy. The cause is usually single-row INSERTs from the application.</p> <p>Every INSERT into a MergeTree table creates at least one immutable data part on disk. ClickHouse is optimized for batch inserts. When clients send single-row or micro-batch inserts, parts are created faster than background merges can consolidate them. This is the number one driver of part accumulation in production clusters.</p>ClickHouse Table is in readonly mode: is_readonly on replicated tables and how to fix ithttps://www.netdata.cloud/guides/clickhouse/clickhouse-table-is-in-readonly-mode/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-table-is-in-readonly-mode/<p>Inserts fail with <code>TABLE_IS_READ_ONLY</code>. <code>system.replicas</code> shows <code>is_readonly = 1</code> for affected tables and the replica rejects writes. For replicated tables, this is a coordination failure, not a disk or memory problem: the replica has lost its session with ClickHouse Keeper or ZooKeeper, or the ensemble is unreachable.</p> <p>Reads from local parts may still succeed, which hides the failure from load balancers and monitoring probes that rely on <code>SELECT 1</code> or the HTTP ping endpoint. Brief readonly states lasting seconds are normal during Keeper leader elections. Sustained readonly lasting minutes means the replica is diverging and inserts are being lost or routed elsewhere.</p>ClickHouse too many partitions: why over-partitioning multiplies your part counthttps://www.netdata.cloud/guides/clickhouse/clickhouse-too-many-partitions/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-too-many-partitions/<p>You are watching <code>MaxPartCountForPartition</code> climb, or you have already seen <code>DB::Exception: Too many parts</code>. You check the table and see a modest total of active parts. The table looks healthy, but ClickHouse rejects inserts anyway.</p> <p>The problem is not the table total. It is the partition boundary.</p> <p>ClickHouse enforces part limits per partition, not per table. A high-cardinality <code>PARTITION BY</code> key like <code>toYYYYMMDD(timestamp)</code> or a business identifier creates thousands of isolated part pools. Parts never merge across those pools. One hundred partitions with thirty parts each produces 3,000 parts, multiplied merge-scheduling overhead, and higher file-descriptor pressure. One partition crossing the hard limit kills inserts for that partition while the rest of the table appears idle.</p>ClickHouse Too many simultaneous queries: max_concurrent_queries and query stormshttps://www.netdata.cloud/guides/clickhouse/clickhouse-too-many-simultaneous-queries/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-too-many-simultaneous-queries/<p>You run a query and ClickHouse returns <code>Too many simultaneous queries. Maximum: N</code>, or one of the kind- or user-specific variants of the same error. New connections either queue or fail outright. Queries that completed in seconds yesterday now time out. The server is not down, but it is not usable.</p> <p>ClickHouse is optimized for fewer, heavier analytical queries. As concurrency rises, CPU, memory, and I/O contention increase non-linearly. A small spike can become a storm because each query is greedy.</p>ClickHouse ZooKeeper session has expired: causes, recovery, and tuninghttps://www.netdata.cloud/guides/clickhouse/clickhouse-zookeeper-session-expired/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-zookeeper-session-expired/<p>When <code>system.replicas</code> shows <code>is_session_expired = 1</code>, the replica has lost its ZooKeeper session and stopped participating in replication. It rejects inserts, coordinated merges, and distributed DDL. Depending on quorum and load-balancer configuration, writes may shift silently to other replicas or halt for entire shards.</p> <p><code>is_session_expired</code> often appears alongside <code>is_readonly = 1</code>, but the two are distinct. Session expiration means the coordination session is dead. Read-only means the replica refuses writes. Session expiration is the most severe because it breaks the replica&rsquo;s contract with the cluster.</p>Cloud Foundry Firehose Monitoringhttps://www.netdata.cloud/monitoring-101/cloud_foundry_firebase-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/cloud_foundry_firebase-monitoring/<h2 id="cloud-foundry-firehose-monitoring">Cloud Foundry Firehose Monitoring</h2> <h3 id="what-is-cloud-foundry-firehose">What Is Cloud Foundry Firehose?</h3> <p>Cloud Foundry Firehose is a powerful component of the Cloud Foundry platform providing a single interface to access a variety of operational data streams. It serves as the backbone for collecting metrics, logs, events, and other crucial data about the system, making it indispensable for effective cloud service management and troubleshooting.</p> <h3 id="monitoring-cloud-foundry-firehose-with-netdata">Monitoring Cloud Foundry Firehose With Netdata</h3> <p>To monitor Cloud Foundry Firehose effectively, Netdata leverages an openmetrics (Prometheus) exporter. This integration makes it possible to ingest real-time data from any Prometheus exporter, providing users with automated dashboards, alerts, and more, all without the need for a Prometheus server or Grafana. By using Netdata’s <a href="https://github.com/bosh-prometheus/firehose_exporter">Cloud Foundry Firehose monitoring tool</a>, DevOps teams can visualize live metrics and troubleshoot issues much faster, enhancing the overall reliability and efficiency of the Cloud Foundry environment.</p>Cloud Foundry Monitoringhttps://www.netdata.cloud/monitoring-101/cloud_foundry-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/cloud_foundry-monitoring/<h2 id="cloud-foundry-monitoring">Cloud Foundry Monitoring</h2> <h3 id="what-is-cloud-foundry">What Is Cloud Foundry?</h3> <p>Cloud Foundry is an open-source platform as a service (PaaS) providing a choice of cloud service providers, development frameworks, and application services. With Cloud Foundry, developers can efficiently manage application deployment, lifecycle, and scaling. This platform supports a variety of languages and frameworks, including Java, Node.js, Ruby, and Python, making it versatile for many development needs.</p> <h3 id="monitoring-cloud-foundry-with-netdata">Monitoring Cloud Foundry With Netdata</h3> <p>To monitor Cloud Foundry, Netdata utilizes an openmetrics (Prometheus) exporter. This capability allows Netdata to ingest data efficiently from any Prometheus exporter, providing users with automated dashboards and alerting systems without the hassle of managing a separate Prometheus server or Grafana. This seamless integration ensures that monitoring gets technical teams actionable insights promptly, optimizing their operations and infrastructure management.</p>CloudWatch Monitoringhttps://www.netdata.cloud/monitoring-101/aws_cloudwatch-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/aws_cloudwatch-monitoring/<h2 id="cloudwatch-monitoring">CloudWatch Monitoring</h2> <h3 id="what-is-cloudwatch">What Is CloudWatch?</h3> <p>Amazon CloudWatch is a powerful monitoring and management service offered by AWS that provides data and actionable insights to monitor applications, understand and respond to system-wide performance changes, optimize resource utilization, and gain a unified view of operational health. It enables DevOps engineers, IT admins, and developers to track metrics, monitor log files, and set alarms to quickly react to potential performance issues.</p> <h3 id="monitoring-cloudwatch-with-netdata">Monitoring CloudWatch With Netdata</h3> <p>To monitor CloudWatch with ease and precision, Netdata employs the openmetrics (prometheus) exporter. The great advantage of using Netdata as a CloudWatch monitoring tool is that it can ingest data from any Prometheus exporter. This setup allows for automated dashboards and alerts, which eliminate the need for a standalone Prometheus server or Grafana. By bridging these functionalities, tools for monitoring CloudWatch become highly intuitive and efficient.</p>ClusterControl CMON Monitoringhttps://www.netdata.cloud/monitoring-101/cmon-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/cmon-monitoring/<h2 id="clustercontrol-cmon-monitoring">ClusterControl CMON Monitoring</h2> <h3 id="what-is-clustercontrol-cmon">What Is ClusterControl CMON?</h3> <p>ClusterControl CMON is a robust database management platform designed to streamline the management and monitoring of database clusters. By providing critical insights into database health, performance, and security, it serves as an invaluable tool for IT administrators and developers who need to maintain high availability and performance.</p> <h3 id="monitoring-clustercontrol-cmon-with-netdata">Monitoring ClusterControl CMON With Netdata</h3> <p>Netdata offers a seamless solution to monitor ClusterControl CMON using its advanced metrics collection capabilities. To monitor ClusterControl CMON, Netdata uses an openmetrics (Prometheus) exporter, allowing you to harness the benefits of Prometheus without the complexity of setting up a Prometheus server. By ingesting data from any Prometheus exporter, Netdata provides automated dashboards, alerts, and more. This streamlined setup means you do not need additional services like Grafana, simplifying your monitoring stack while ensuring detailed insights into your ClusterControl CMON environment.</p>CockroachDB Backup Job Failures: How To Fix Themhttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-backup-job-failures/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-backup-job-failures/<p>CockroachDB scheduled backups run through the internal jobs system, visible via <code>crdb_internal.jobs</code> (backed by <code>system.jobs</code>). When a scheduled backup fails silently, stalls indefinitely, or grows so slowly that it cannot complete within its interval, your recovery point objective (RPO) is at risk. The failure is insidious: backups often appear healthy until you realize the last successful completion was 36 hours ago.</p> <p>The severity distinction is sharp. A single backup failure with a recent prior success is a TICKET. The retry will probably succeed. But when no successful backup exists within your RPO window (for example, last success over 24 hours ago with a 24-hour RPO), you are in PAGE territory.</p>CockroachDB certificate expired: TLS handshake failures and online rotationhttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-certificate-expired/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-certificate-expired/<p>CockroachDB uses mutual TLS for every connection: node-to-node, client-to-node, and admin UI. There is no plaintext fallback and no grace period. When a certificate expires, affected connections fail immediately.</p> <p>Node certificate expiry prevents nodes from completing TLS handshakes with each other, which can look like a network partition or quorum loss. Client certificate expiry prevents applications from connecting. CA certificate expiry invalidates the entire trust chain at once, breaking every connection simultaneously.</p>CockroachDB changefeed lag: changefeed_max_behind_nanos and the GC time bombhttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-changefeed-lag/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-changefeed-lag/<p>Changefeed lag in CockroachDB starts as a consumer latency problem and ends as a disk space emergency. The <code>changefeed_max_behind_nanos</code> gauge measures how far behind your CDC feeds have fallen, but the real danger is what follows: a stalled changefeed holds a protected timestamp that prevents MVCC garbage collection, and dead data accumulates silently until the disk fills. The cluster appears healthy from the SQL side. Queries are fast, nodes are up, ranges are available. But every deleted row and every overwritten value stays on disk because GC cannot reclaim the space.</p>CockroachDB clock skew cascade: how shared NTP drift causes quorum losshttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-clock-skew-cascade/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-clock-skew-cascade/<p>Multiple CockroachDB nodes crashed overnight. The logs show &ldquo;clock synchronization error: this node is more than 500ms away from at least half of the known nodes.&rdquo; You restart them, and they crash again. Some ranges are now unavailable. The cluster is losing quorum.</p> <p>A shared NTP failure caused multiple nodes to drift past CockroachDB&rsquo;s self-termination threshold in quick succession. Single-node clock skew is bad but recoverable. Multi-node skew from a shared NTP source can take down quorum faster than the cluster can heal.</p>CockroachDB clock synchronization error: this node is more than 500ms away from at least half of the known nodeshttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-clock-synchronization-error-500ms/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-clock-synchronization-error-500ms/<p>You see this fatal log line on a CockroachDB node:</p> <pre tabindex="0"><code>clock synchronization error: this node is more than 500ms away from at least half of the known nodes </code></pre><p>The process exits immediately. If the node is managed by systemd, Kubernetes, or a process supervisor, it restarts and crashes again. The crash-loop continues until the clock problem is fixed.</p> <p>CockroachDB uses Hybrid Logical Clocks (HLC) to enforce serializable consistency across distributed transactions. HLC combines physical wall-clock time with a logical counter. Every node must agree on time within a bounded window, controlled by <code>--max-offset</code> (default 500ms). When a node detects its clock has drifted beyond 80% of <code>--max-offset</code> relative to a majority of peers, it calls <code>log.Fatal</code> and exits rather than risk serving stale reads or assigning timestamps that conflict with committed transactions.</p>CockroachDB clock_offset_meannanos high: catching clock drift before self-terminationhttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-clock-offset-high/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-clock-offset-high/<p><code>clock_offset_meannanos</code> measures the mean clock offset between a CockroachDB node and its peers. When it climbs, you are on a path that ends in silent performance degradation from widened read uncertainty windows, or a node self-terminating to preserve data consistency.</p> <p>The thresholds are unforgiving. CockroachDB uses a default <code>--max-offset</code> of 500ms. A node self-terminates when its mean offset exceeds 80% of that value (400ms) relative to at least half of its peers. But a constant 200ms offset, stable and below any threshold, still doubles the uncertainty interval for every read. Transactions silently restart more often, P99 read latency creeps up, and nobody suspects the clock.</p>CockroachDB compaction backlog growing: when Pebble can't keep pace with writeshttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-compaction-backlog-growing/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-compaction-backlog-growing/<p>Pebble&rsquo;s background compaction threads sometimes fall behind foreground writes. In CockroachDB, this does not cause immediate failure. SSTable files accumulate in Level 0 and the compaction queue, read amplification rises, and the node drifts toward write stalls. Because the database continues to serve traffic, the backlog is easy to miss until it becomes severe.</p> <p>The earliest visible sign is a gentle upward trend in Level 0 file counts or marked-for-compaction files over hours. These metrics fluctuate with workload bursts, but a sustained upward slope means the store is consuming headroom. Healthy operation requires compaction throughput at least twice the write ingestion rate. Less than that leaves no margin for bursts, MVCC garbage collection, or rebalancing.</p>CockroachDB connection storm after failover: reconnect stampedes and surviving-node overloadhttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-connection-storm-after-failover/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-connection-storm-after-failover/<p>When a CockroachDB node dies, every client connected to it reconnects at the same time. Without jittered backoff in client connection pools, hundreds or thousands of new connections land on the surviving nodes within seconds. The survivors are not overwhelmed by additional query load. They are overwhelmed by connection overhead: per-connection goroutines, session memory allocations, TLS handshakes, and SQL planner initialization.</p> <p>The signature is a 2-3x spike in <code>sql_conns</code> on surviving nodes, with a simultaneous jump in <code>sys_goroutines</code> and <code>sql_mem_root_current</code>. Latency rises across all nodes, not just those receiving the flood. The storm usually self-resolves as pools stabilize. But if memory pressure reaches OOM, one node failure can cascade into a multi-node outage.</p>CockroachDB consistency check failed: checksum mismatches and confirmed corruptionhttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-data-consistency-check-failure/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-data-consistency-check-failure/<p>When the background consistency checker detects a checksum mismatch between replicas of a range, CockroachDB logs a fatal error and the node terminates. This is not a transient condition. The database is telling you that data integrity is compromised.</p> <p>The definitive messages: &ldquo;consistency check failed&rdquo; (the fatal follow-up is &ldquo;This node is terminating because a replica inconsistency was detected between this node and its other replicas&rdquo;) or a Pebble-level &ldquo;pebble/table: invalid table&rdquo; / &ldquo;checksum mismatch&rdquo; error. Both originate from CockroachDB&rsquo;s consistency checker subsystem, not from unrelated log noise. This article covers the failure mechanism, the recovery path, and the signals that help you scope the damage.</p>CockroachDB context deadline exceeded: timeouts, slow ranges, and overloadhttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-context-deadline-exceeded/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-context-deadline-exceeded/<p>&ldquo;context deadline exceeded&rdquo; tells you something is slow. It does not tell you what. The same error appears whether a leaseholder is overloaded, a network path is congested, L0 sublevels are climbing past write-stall territory, or the application set a 2-second statement timeout on a query that normally takes 50 milliseconds.</p> <p>Treat the error as a symptom, not a diagnosis. The diagnostic question is: which layer is slow?</p> <h2 id="what-this-means">What this means</h2> <p>Every internal CockroachDB RPC carries a context with a deadline. SQL statements sent from a gateway node to a leaseholder, KV batches forwarded to range replicas, and Raft heartbeats all have timeouts. When a deadline expires, the caller receives a &ldquo;context deadline exceeded&rdquo; error that propagates up through the SQL layer to the client.</p>CockroachDB CPU saturation: Raft ticking, SQL execution, and the per-node ceilinghttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-cpu-saturation/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-cpu-saturation/<p>CockroachDB is CPU-hungry by design. Every range runs its own Raft state machine. Every SQL statement parses, plans, and executes through Go. Compaction, encryption-at-rest, and checksumming all burn cycles. When CPU saturates, the failure mode is not a clean slowdown: Raft heartbeats get delayed, admission control starts queuing, GC pauses lengthen, and the node risks losing liveness. The cluster average can look healthy while one leaseholder melts.</p> <p>CockroachDB recommends keeping sustained utilization below 60-70% so Raft processing and background tasks have headroom. The documented ceiling is 80% — above it, degradation is nonlinear: Raft, GC, and admission control contend for the remaining cycles simultaneously, and the node starts losing leases.</p>CockroachDB detecting hot ranges: per-range QPS, CPU asymmetry, and the Hot Ranges pagehttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-detecting-hot-ranges/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-detecting-hot-ranges/<p>Hot ranges are the most common performance bottleneck in CockroachDB that does not surface in aggregate metrics. The leaseholder model routes all reads and writes for a range through a single node. When one range receives disproportionate traffic, that node saturates while the rest of the cluster idles. The cluster-wide CPU average looks healthy. The per-node breakdown tells a different story.</p> <p>Detection uses three complementary layers, each with different cost and fidelity tradeoffs. Per-node CPU and QPS asymmetry (standard Prometheus metrics) is cheap and continuous but indirect: it tells you a hot range likely exists, not which one. The DB Console Hot Ranges/Top Ranges page provides direct per-range QPS visibility but is manual and point-in-time. <code>crdb_internal.ranges</code> provides programmatic access to range layout (leaseholder, range size, replicas) but exposes no per-range QPS and is expensive to query, so it must not be scraped at regular intervals.</p>CockroachDB disk stall detected: storage_disk_stalled and node self-terminationhttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-disk-stall-detected/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-disk-stall-detected/<p>When <code>storage_disk_stalled</code> increments on a CockroachDB node, the Pebble storage engine has detected that disk I/O is no longer completing within the expected time window. The node is on a countdown to self-termination. This is not a performance degradation warning. It is a safety mechanism preparing to fire.</p> <p>CockroachDB writes every committed transaction through a write-ahead log (WAL). The WAL fsync is on the critical path for every write: Raft cannot acknowledge a commit until the log entry is persisted to disk. If that fsync blocks for long enough, the node cannot process Raft heartbeats, cannot commit writes, and cannot renew its liveness record. Rather than continue operating in a state that could produce data inconsistency, CockroachDB terminates the process.</p>CockroachDB error 53200: SQL memory budget exhausted and query rejectionhttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-sql-memory-budget-53200/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-sql-memory-budget-53200/<p>Error 53200 is CockroachDB&rsquo;s PostgreSQL-compatible signal that the per-node SQL memory budget has run out. Applications see SQLSTATE 53200 (&ldquo;insufficient resources&rdquo;) with text such as &ldquo;memory budget exceeded&rdquo; and byte counts showing what was requested, what is allocated, and what the budget allows.</p> <p>The SQL memory budget is enforced per-node, bounded by <code>--max-sql-memory</code> (default 25% of system RAM). When a node&rsquo;s SQL execution layer exhausts its budget, queries on that node either spill to temporary disk storage (slow) or are rejected outright with 53200. One large analytical query on a single gateway node can starve every other session connected to that node, even if the rest of the cluster has memory to spare.</p>CockroachDB LSM compaction death spiral: L0 sublevels, read amplification, and write stallshttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-lsm-compaction-death-spiral/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-lsm-compaction-death-spiral/<p>SQL P99 latency jumps from milliseconds to seconds. KV write latency climbs. Nodes transfer leases. Logs show Pebble write stall messages. This is the LSM compaction death spiral: writes outpace the storage engine&rsquo;s ability to compact data from Level 0 down the LSM tree. L0 sublevels stack up, read amplification rises, and the node eventually stalls writes to protect itself. By the time write stalls appear, the node is already at risk of losing Raft leases and appearing partially unavailable. This guide shows how to diagnose the spiral, stop it, and prevent it.</p>CockroachDB memory pressure, GC thrashing, and Raft liveness failurehttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-memory-gc-liveness-thrash/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-memory-gc-liveness-thrash/<p>A CockroachDB node loses liveness in a repeating pattern: it drops out, the cluster redistributes its leases, it recovers, reacquires leases, then drops again. Each cycle lasts seconds to minutes. Application queries see intermittent timeouts, ambiguous results, and latency spikes that correlate with the node&rsquo;s oscillation. The DB Console shows the node flapping between live and not-live states.</p> <p>This is the memory pressure to GC thrashing to Raft liveness failure cascade. The Go runtime heap grows until garbage collection pauses become long enough to prevent the node from renewing its liveness heartbeat. Once the heartbeat interval lapses, the cluster marks the node dead and moves its leases. When GC completes and memory is freed, the node recovers and reacquires leases, restarting the cycle.</p>CockroachDB Monitoringhttps://www.netdata.cloud/monitoring-101/cockroachdb-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/cockroachdb-monitoring/<h2 id="cockroachdb-monitoring">CockroachDB Monitoring</h2> <p>CockroachDB is a cloud-native distributed SQL database designed to scale horizontally and survive datacenter failures. Monitoring CockroachDB is crucial for maintaining the health, performance, and reliability of your database infrastructure. Netdata provides a comprehensive CockroachDB monitoring tool that enables real-time visibility and enhanced troubleshooting capabilities to ensure optimal database operations.</p> <h3 id="what-is-cockroachdb">What Is CockroachDB?</h3> <p>CockroachDB is a distributed SQL database, similar in functionality to Google Spanner, designed to deliver strong fault tolerance, consistency, and scalability across distributed environments. Its architecture allows for seamless scaling and resilience, making it an ideal choice for modern, high-demand database operations.</p>CockroachDB monitoring checklist: the signals every production cluster needshttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-monitoring-checklist/<p>CockroachDB layers SQL execution on a replicated KV store backed by Pebble LSM trees, Raft consensus, and MVCC concurrency control. Each subsystem has distinct failure modes, and interactions between them create cascades that single-signal monitoring cannot catch. A cluster can show healthy CPU, adequate disk space, and sub-millisecond SQL latency while L0 sublevels climb toward write stalls or clock offset drifts toward the self-termination threshold.</p> <p>This checklist defines four monitoring maturity levels (survival, operational, mature, expert) and maps every production signal to its level. Use it to audit current coverage, identify gaps before they cause incidents, and plan what to add as your cluster grows.</p>CockroachDB node liveness failure: heartbeats, lease redistribution, and flappinghttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-node-liveness-failure/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-node-liveness-failure/<p>Lease transfer spikes, briefly unavailable ranges, and client errors such as ambiguous results or connection resets indicate node liveness failure. In the logs, nodes transition to not-live and back within seconds. When the cluster decides a node cannot renew its liveness heartbeat, it redistributes leases. If the node recovers fast enough to renew but not fast enough to stay healthy, it flaps: an oscillating state more destructive than a clean outage because it repeatedly interrupts in-flight work and prevents stable failover.</p>CockroachDB out of memory: sys_rss, --cache, --max-sql-memory, and the OOM killerhttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-out-of-memory-oom/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-out-of-memory-oom/<p>A CockroachDB node disappears. No graceful shutdown, no drain sequence, no error in the SQL layer. The process is gone, and <code>dmesg</code> shows the kernel OOM killer selected it. Or in Kubernetes, the pod restarts with reason <code>OOMKilled</code>.</p> <p>The root cause is almost always a mismatch between what CockroachDB thinks it can allocate and what the container or host actually allows. CockroachDB partitions its memory into two manually-sized pools: the Pebble block cache (<code>--cache</code>) and the SQL execution budget (<code>--max-sql-memory</code>). The Go garbage collector only manages the Go heap. CGo allocations, primarily the Pebble block cache and memtables, are manually managed. When the sum of these pools plus runtime overhead exceeds the container or host limit, the OOM killer intervenes.</p>CockroachDB Pebble write stalls: when the storage engine refuses writeshttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-pebble-write-stalls/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-pebble-write-stalls/<p>When application writes time out or return ambiguous errors, check CockroachDB logs for <code>write stall</code> messages (Pebble emits <code>write stall beginning</code> / <code>write stall ending</code>) and watch <code>storage_write_stalls</code>. Pebble pauses writes to a store when Level 0 compaction debt exceeds safe thresholds. Until compaction drains L0, that store cannot accept new writes.</p> <p>Write stalls are the most severe storage signal in CockroachDB. A brief stall during bulk loading may be harmless, but sustained stalls at one per second mean the node cannot meet its Raft obligations. The node may still serve reads, but it can lose Raft leadership because it cannot append log entries. That cascades into lease transfers and temporary range unavailability.</p>CockroachDB ReadWithinUncertaintyInterval restarts: the near-diagnostic signal of clock skewhttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-readwithinuncertainty-restarts/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-readwithinuncertainty-restarts/<p>When CockroachDB reports <code>readwithinuncertainty</code> as a transaction restart cause, you have a clock synchronization problem. This restart cause does not appear in meaningful quantities for any other reason. Any sustained nonzero rate, even well below the self-termination threshold, indicates that NTP or the underlying clock source is not keeping node clocks aligned.</p> <p>The error stems from CockroachDB&rsquo;s Hybrid Logical Clock (HLC) design. Each transaction receives a timestamp from its gateway node&rsquo;s HLC, which combines physical wall-clock time with a logical counter. When a read on one node encounters a write from a transaction that started on a different node, and the two nodes&rsquo; clocks are not aligned, the database cannot determine which transaction began first. CockroachDB conservatively restarts the reading transaction at a higher timestamp. Under SERIALIZABLE isolation, this restart requires client-side retry logic and adds directly to tail latency.</p>CockroachDB replica unavailable: lost quorum and stuck Raft groupshttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-replica-unavailable/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-replica-unavailable/<p><code>ranges_unavailable</code> has gone nonzero. Clients are seeing &ldquo;replica unavailable&rdquo; errors. Some portion of your keyspace cannot be read or written. This is an active availability incident.</p> <p>In CockroachDB, every range (a ~512 MiB slice of the keyspace) is replicated across multiple nodes. A write requires quorum acknowledgment from a majority of replicas before it commits. When too few replicas are reachable, the range loses quorum and cannot serve reads or writes. The <code>ranges_unavailable</code> metric tracks exactly this condition: ranges with no leaseholder or with lost Raft quorum.</p>CockroachDB result is ambiguous: ambiguous commit errors and how to handle themhttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-result-is-ambiguous/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-result-is-ambiguous/<p>Your application received <code>result is ambiguous</code> (PostgreSQL error code 40003, <code>statement_completion_unknown</code>) from CockroachDB. The transaction may have committed. It may have been aborted. The database does not know, and neither do you.</p> <p>This is not a bug. It is a correctness property of CockroachDB&rsquo;s distributed commit protocol. When the transaction coordinator loses contact with the leaseholder during the final commit step, or during the last statement of an implicit transaction, it cannot determine whether the commit succeeded. Rather than guess and risk a silent double-apply, CockroachDB surfaces the ambiguity.</p>CockroachDB RETRY_WRITE_TOO_OLD: the most common contention restart and how to kill ithttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-write-too-old/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-write-too-old/<p>Your cluster is healthy: nodes are live, ranges are available, disk space is fine, L0 sublevels are low. But transaction commit latency is climbing, P99 is widening, and the <code>txn_restarts</code> metric shows a rising rate tagged <code>writetooold</code>. Whether applications surface errors to users depends on whether their retry logic works.</p> <p>RETRY_WRITE_TOO_OLD is the most common transaction restart cause under CockroachDB&rsquo;s default SERIALIZABLE isolation. It is not an infrastructure problem. It is a contention problem rooted in schema design, key patterns, and transaction scope. Adding nodes does not help because the bottleneck is logical serialization, not physical capacity. Once you identify the conflicting keys and the transaction patterns driving them, writetooold restarts are fixable.</p>CockroachDB SQL error rate: XX000 internal errors and error-code triagehttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-sql-error-rate-xx000/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-sql-error-rate-xx000/<p><code>sql_failure_count</code> is a single Prometheus counter with no error-code labels. A serialization conflict (40001) is expected noise in a contended workload. An internal error (XX000) is a database fault that needs immediate escalation. Treating the aggregate counter as one signal guarantees the wrong response.</p> <p>This article covers how to break that aggregate apart by error code, when XX000 internal errors warrant paging, and how to triage the other common error classes.</p>CockroachDB store is full: emergency disk recovery and why deletes don't free spacehttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-store-is-full/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-store-is-full/<p>A CockroachDB node&rsquo;s store directory is full or nearly full, and the node may have already shut itself down to protect data integrity.</p> <p>Deleting data will not help immediately. CockroachDB uses MVCC: a SQL DELETE writes tombstones at new timestamps rather than removing old data. Until those tombstones propagate through Pebble compaction, the old versions stay on disk. A large-scale delete can temporarily increase disk usage because the tombstones are written before old data is reclaimed.</p>CockroachDB too many connections: sql_conns, pooling, and goroutine pressurehttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-too-many-connections/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-too-many-connections/<p>CockroachDB has no default connection limit comparable to PostgreSQL&rsquo;s <code>max_connections</code>. The optional cluster setting <code>server.max_connections_per_gateway</code> (default <code>-1</code>, i.e. unlimited) can cap non-superuser connections per gateway node, but it is not configured out of the box. Connections accumulate until something else breaks: goroutine pressure, memory exhaustion, or file descriptor limits.</p> <p>The <code>sql_conns</code> gauge tracks active pgwire (SQL) connections per node. With properly configured client-side pooling, this number stays modest. When it climbs past 1000-2000 per node, you almost certainly have a pooling problem upstream.</p>CockroachDB TransactionRetryWithProtoRefreshError: RETRY_SERIALIZABLE causes and fixeshttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-transaction-retry-serializable/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-transaction-retry-serializable/<p>The application logs show <code>TransactionRetryWithProtoRefreshError: TransactionRetryError: retry txn (RETRY_SERIALIZABLE - failed preemptive refresh due to a conflict: committed value on key /Table/.../0)</code>. SQLSTATE is 40001. Clients are timing out or failing outright. The cluster looks healthy: nodes are live, ranges are available, disk space is fine. The problem is in the transaction layer.</p> <p>Under SERIALIZABLE isolation (CockroachDB&rsquo;s default), the database uses optimistic concurrency. It proceeds as if no conflict exists, then detects conflicts at commit or statement boundary. When a transaction&rsquo;s preemptive refresh fails because another transaction already committed a write to a key the first transaction read, CockroachDB emits RETRY_SERIALIZABLE. This is expected behavior, not a bug.</p>CockroachDB under-replicated ranges: ranges_underreplicated and the healing marginhttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-under-replicated-ranges/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-under-replicated-ranges/<p>When <code>ranges_underreplicated</code> rises above zero, CockroachDB has ranges with fewer live replicas than the configured replication factor. The replicate queue is already working to heal them by transferring Raft snapshots to new target nodes, but until healing completes, those ranges have reduced or zero fault tolerance margin.</p> <p>The key operational question is not whether under-replicated ranges exist (they will, transiently, after almost any node event), but whether the cluster is healing fast enough to stay ahead of the next failure. This is the healing margin: the buffer between the current replication state and the point where a range loses quorum and becomes unavailable.</p>Collectd Monitoringhttps://www.netdata.cloud/monitoring-101/collectd-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/collectd-monitoring/<h2 id="collectd-monitoring">Collectd Monitoring</h2> <h3 id="what-is-collectd">What Is Collectd?</h3> <p>Collectd is a powerful tool for monitoring systems and applications. It collects performance data from your systems and networks, providing detailed insights to help troubleshoot issues and optimize performance. As a long-standing part of the open-source community, Collectd offers a comprehensive and extensible solution for those needing robust data collection capabilities.</p> <h3 id="monitoring-collectd-with-netdata">Monitoring Collectd With Netdata</h3> <p>To monitor Collectd effectively, Netdata uses an OpenMetrics (Prometheus) exporter. This integration allows Netdata to ingest data directly from any Prometheus exporter without requiring a Prometheus server or Grafana setup. With Netdata, you gain access to automated dashboards, real-time alerts, and insightful metrics visualization, making it an ideal Collectd monitoring tool. Easily connect and start monitoring your systems using <a href="https://github.com/prometheus/collectd_exporter">Collectd exporter</a> combined with <a href="https://app.netdata.cloud/?utm_source=website&amp;utm_content=monitoring101">Netdata&rsquo;s intuitive interface</a>.</p>Communityhttps://www.netdata.cloud/community/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/community/Concourse Monitoringhttps://www.netdata.cloud/monitoring-101/concourse-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/concourse-monitoring/<h2 id="concourse-monitoring">Concourse Monitoring</h2> <h3 id="what-is-concourse">What Is Concourse?</h3> <p>Concourse is a powerful, open-source CI/CD system that automates and streamlines your application development and deployment processes. Its clean and straightforward interface, coupled with its ability to handle complex workflows, makes it a popular choice among DevOps teams looking to enhance their software release cycles.</p> <h3 id="monitoring-concourse-with-netdata">Monitoring Concourse With Netdata</h3> <p>Monitoring your Concourse environment is crucial for ensuring optimal pipeline performance and detecting issues before they affect application delivery. With Netdata, monitoring Concourse becomes seamless and efficient. Netdata leverages an openmetrics (Prometheus) exporter to collect comprehensive metrics from your Concourse instance. This means that you can ingest data directly from any Prometheus exporter, receiving automated dashboards, alerts, and more, without the need for a separate Prometheus server or Grafana setup.</p>Consul Monitoringhttps://www.netdata.cloud/monitoring-101/consul-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/consul-monitoring/<h2 id="consul-monitoring">Consul Monitoring</h2> <h3 id="what-is-consul">What Is Consul?</h3> <p>Consul is a highly scalable and distributed service networking platform that enables users to manage and secure their microservices connections. Developed by HashiCorp, Consul offers key features such as service discovery, health checking, load balancing, and a secure service mesh. <a href="https://www.consul.io/">Learn more about Consul</a>.</p> <h3 id="monitoring-consul-with-netdata">Monitoring Consul With Netdata</h3> <p>Netdata provides a powerful and real-time monitoring solution for Consul, utilizing the go.d.plugin. This tool connects seamlessly to your Consul installation, enabling comprehensive monitoring by leveraging the <a href="https://developer.hashicorp.com/consul/api-docs">Consul REST API</a>. By using Netdata, you gain instant access to crucial Consul metrics, helping you ensure optimal performance and quick identification of potential issues. To see Netdata in action, check our <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">Live Demo</a>.</p>Contact Netdatahttps://www.netdata.cloud/contact-us/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/contact-us/CoreDNS Monitoringhttps://www.netdata.cloud/monitoring-101/coredns-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/coredns-monitoring/<h2 id="coredns-monitoring">CoreDNS Monitoring</h2> <h3 id="what-is-coredns">What Is CoreDNS?</h3> <p>CoreDNS is a flexible and extensible DNS server that can serve as a cluster DNS inside Kubernetes or provide other DNS services. Built with a focus on flexibility, plugin support, and efficiency, it&rsquo;s designed to facilitate the addition and combination of functionalities. You can read more about CoreDNS on their <a href="https://coredns.io/">official website</a>.</p> <h3 id="monitoring-coredns-with-netdata">Monitoring CoreDNS With Netdata</h3> <p>Netdata is an ideal tool for monitoring CoreDNS, offering real-time visibility and insightful metrics. With Netdata, you can track DNS queries, responses, and errors to ensure the robustness and performance of your DNS server. Explore our <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">Live Demo</a> to experience Netdata’s capabilities firsthand.</p>Correlating cloud VPC flow logs with on-prem NetFlowhttps://www.netdata.cloud/guides/network/network-cloud-onprem-flow-correlation/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-cloud-onprem-flow-correlation/<p>Cloud flow logs and on-prem flow records share the 5-tuple concept but diverge in nearly every dimension that matters for correlation: transport, latency, sampling, timestamps, topology, and NAT visibility. Cloud providers emit VPC flow logs via push to object storage with implicit sampling and aggregation intervals measured in minutes. On-premises devices export NetFlow v5/v9, IPFIX, or sFlow over UDP with configurable sampling and near-real-time delivery.</p> <p>This gap is a recurring contributor to operational incidents. An attacker pivoting from a compromised cloud workload to on-prem via VPN is invisible across the boundary if no join exists between the two telemetry sources. The same gap hides legitimate operational issues: cross-boundary packet loss, asymmetric routing through cloud transit gateways, and NAT translation mismatches between cloud NAT and on-prem firewalls.</p>Couchbase Monitoringhttps://www.netdata.cloud/monitoring-101/couchbase-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/couchbase-monitoring/<h2 id="couchbase-monitoring">Couchbase Monitoring</h2> <h3 id="what-is-couchbase">What Is Couchbase?</h3> <p>Couchbase is a distributed NoSQL cloud database ideal for interactive web and mobile applications. Designed to support massive data volumes and a large number of users, Couchbase provides core database functions while enhancing performance through its advanced memory-first architecture.</p> <h3 id="monitoring-couchbase-with-netdata">Monitoring Couchbase With Netdata</h3> <p>Monitoring Couchbase’s health and performance is essential to maintaining its operations-efficiently. With Netdata, you can seamlessly integrate Couchbase monitoring and get real-time insights into vital metrics. Netdata’s intuitive dashboard provides detailed metrics, enabling you to keep a close watch on Couchbase’s performance.</p>CouchDB Monitoringhttps://www.netdata.cloud/monitoring-101/couchdb-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/couchdb-monitoring/<h2 id="couchdb-monitoring">CouchDB Monitoring</h2> <h3 id="what-is-couchdb">What Is CouchDB?</h3> <p>CouchDB is an open-source database developed by the Apache Software Foundation, known for its seamless storage and retrieval of JSON documents. It features a distributed architecture with easy replication, making it a popular choice for web applications and mobile apps that require offline-first functionality. Learn more on the <a href="https://couchdb.apache.org/">CouchDB official site</a>.</p> <h3 id="monitoring-couchdb-with-netdata">Monitoring CouchDB With Netdata</h3> <p>Monitoring CouchDB is crucial to ensure optimal performance and reliability of your database infrastructure. Netdata provides powerful tools for monitoring CouchDB, offering real-time insights into various metrics such as database activity, HTTP requests, active tasks, and more. Leveraging the Netdata agent, you can efficiently track these metrics and respond swiftly to potential issues.</p>CraftBeerPi Monitoringhttps://www.netdata.cloud/monitoring-101/ftbeerpi-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/ftbeerpi-monitoring/<h2 id="craftbeerpi-monitoring">CraftBeerPi Monitoring</h2> <h3 id="what-is-craftbeerpi">What Is CraftBeerPi?</h3> <p>CraftBeerPi is an open-source brewing automation software designed to revolutionize the homebrewing experience. By integrating with various sensors and controllers, CraftBeerPi helps manage the entire brewing process, ensuring precision and consistency with every batch.</p> <h3 id="monitoring-craftbeerpi-with-netdata">Monitoring CraftBeerPi With Netdata</h3> <p>When it comes to ensuring the peak performance of your brewing setup, monitoring CraftBeerPi with Netdata is an optimal choice. To monitor CraftBeerPi, Netdata employs an openmetrics (Prometheus) exporter, specifically the <a href="https://github.com/jo-hannes/craftbeerpi_exporter">CraftBeerPi exporter</a>. This integration allows Netdata to ingest data from any Prometheus exporter seamlessly.</p>Crowdsec Monitoringhttps://www.netdata.cloud/monitoring-101/crowdsec-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/crowdsec-monitoring/<h2 id="crowdsec-monitoring">Crowdsec Monitoring</h2> <h3 id="what-is-crowdsec">What Is Crowdsec?</h3> <p>Crowdsec is an open-source, collaborative security solution designed to detect and respond to threats. It emphasizes community collaboration to build a robust defense against cyber threats by leveraging shared threat intelligence.</p> <h3 id="monitoring-crowdsec-with-netdata">Monitoring Crowdsec With Netdata</h3> <p>To effectively monitor Crowdsec, Netdata utilizes an openmetrics (Prometheus) exporter. This approach allows Netdata to assimilate data from any Prometheus exporter, providing seamless integration for users without the necessity of deploying a Prometheus server or Grafana. With automatic dashboards and alerting capabilities, Netdata transforms your Crowdsec monitoring setup into a high-performance, real-time monitoring system.</p>Cryptowatch Monitoringhttps://www.netdata.cloud/monitoring-101/cryptowatch-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/cryptowatch-monitoring/<h2 id="cryptowatch-monitoring">Cryptowatch Monitoring</h2> <h3 id="what-is-cryptowatch">What Is Cryptowatch?</h3> <p>Cryptowatch is a powerful platform that provides market information for cryptocurrencies, allowing traders and analysts to track price changes, volume, and other critical metrics in real-time. It aggregates data from various exchanges to present a unified view of cryptocurrency markets, making it an indispensable tool for anyone involved in this digital asset space.</p> <h3 id="monitoring-cryptowatch-with-netdata">Monitoring Cryptowatch With Netdata</h3> <p>Netdata&rsquo;s advanced monitoring capabilities make it an excellent choice for keeping tabs on Cryptowatch. By using an openmetrics (Prometheus) exporter, specifically the <a href="https://github.com/nbarrientos/cryptowat_exporter">Cryptowatch Exporter</a>, Netdata can seamlessly ingest data from Cryptowatch. This process does not require a full Prometheus server or Grafana setup, providing automated dashboards and alerts out of the box. This simplicity and integration capability mark Netdata as a leading Cryptowatch monitoring tool in the market.</p>Dell EMC ScaleIO Monitoringhttps://www.netdata.cloud/monitoring-101/scaleio-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/scaleio-monitoring/<h2 id="dell-emc-scaleio-monitoring">Dell EMC ScaleIO Monitoring</h2> <h3 id="what-is-dell-emc-scaleio">What Is Dell EMC ScaleIO?</h3> <p>Dell EMC ScaleIO, also known as VxFlex OS, is a software-defined storage solution designed to turn local storage into shared block storage. ScaleIO is tailored for modern data centers, providing enhanced flexibility and efficiency in handling storage needs. You can learn more about ScaleIO <a href="https://www.dell.com/en-ca/dt/storage/scaleio/scaleioreadynode.htm">here</a>.</p> <h3 id="monitoring-scaleio-with-netdata">Monitoring ScaleIO With Netdata</h3> <p>Netdata offers a comprehensive and user-friendly platform to monitor ScaleIO instances effectively. By utilizing Netdata&rsquo;s ScaleIO monitoring tools, you can collect detailed metrics from ScaleIO components via the VxFlex OS Gateway API. This enables real-time insights and actionable analytics, crucial for maintaining optimal performance.</p>Device control-plane CPU saturation: when SNMP polling causes the spikehttps://www.netdata.cloud/guides/network/network-device-control-plane-cpu/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-device-control-plane-cpu/<p>The router&rsquo;s control-plane CPU is pinned at 95%. SNMP polls are timing out. BGP sessions are approaching hold-time expiry. The instinct is to blame the device or suspect an attack, but the monitoring system itself is frequently the source of the load.</p> <p>The control-plane CPU handles everything that is not hardware-forwarded packet switching: the SNMP agent, BGP, OSPF, STP, the CLI, syslog, AAA, and management interfaces. When SNMP polling saturates this CPU, every control-plane function degrades at once. The symptoms look like a device problem. The cause is often on the collector side.</p>Discourse Monitoringhttps://www.netdata.cloud/monitoring-101/discourse-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/discourse-monitoring/<h2 id="discourse-monitoring">Discourse Monitoring</h2> <h3 id="what-is-discourse">What Is Discourse?</h3> <p><strong>Discourse</strong> is a modern forum software for your community. It reimagines what a discussion platform should be, offering seamless integration with existing web apps, and a mobile-optimized experience.</p> <h3 id="monitoring-discourse-with-netdata">Monitoring Discourse With Netdata</h3> <p>To monitor Discourse effectively and ensure optimal performance, you can rely on Netdata—a powerful real-time monitoring solution. Netdata leverages the Discourse Prometheus exporter to collect relevant metrics. This allows users to monitor Discourse without the need for setting up a Prometheus server or Grafana. Automated dashboards, alerts, and visual insights are readily available from Netdata&rsquo;s platform.</p>Discuss Netdata Enterprise requirementshttps://www.netdata.cloud/request-enterprise/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/request-enterprise/DMARC Monitoringhttps://www.netdata.cloud/monitoring-101/dmarc-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/dmarc-monitoring/<h2 id="dmarc-monitoring">DMARC Monitoring</h2> <h3 id="what-is-dmarc">What Is DMARC?</h3> <p>DMARC (Domain-based Message Authentication, Reporting &amp; Conformance) is an email authentication policy and reporting protocol. It is designed to give domain owners a way to protect their domain from being used in email spoofing, phishing scams, and other cybercrimes. By implementing DMARC, organizations can significantly improve the security and credibility of their email communications.</p> <h3 id="monitoring-dmarc-with-netdata">Monitoring DMARC With Netdata</h3> <p>Netdata provides a robust DMARC monitoring tool using the openmetrics exporter from Prometheus. Specifically, it uses the <a href="https://github.com/jgosmann/dmarc-metrics-exporter">dmarc-metrics-exporter</a> to collect detailed metrics that offer insights into email authentication processes. With Netdata, you can ingest data from any Prometheus exporter and instantly gain access to automated dashboards and alerts without necessitating a Prometheus server or Grafana setup. This streamlined setup helps you keep a close watch on DMARC metrics in a user-friendly manner.</p>DMCache Monitoringhttps://www.netdata.cloud/monitoring-101/dmcache-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/dmcache-monitoring/<h2 id="dmcache-monitoring">DMCache Monitoring</h2> <h3 id="what-is-dmcache">What Is DMCache?</h3> <p>DMCache, a critical component of storage systems, acts as a device mapper cache enabling systems to manage disk block caching. By leveraging DMCache, systems can significantly enhance I/O performance by storing frequently accessed disk blocks in a faster storage medium.</p> <h3 id="monitoring-dmcache-with-netdata">Monitoring DMCache With Netdata</h3> <p>Effective DMCache monitoring ensures that your storage systems are performing optimally and that resources are efficiently utilized. The <a href="https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/dmcache-devices/">Netdata DMCache monitoring tool</a> offers real-time visibility into your DMCache devices, allowing you to track critical performance metrics and gain actionable insights through comprehensive visualizations.</p>DNS Query Monitoringhttps://www.netdata.cloud/monitoring-101/dnsquery-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/dnsquery-monitoring/<h2 id="dns-query-monitoring">DNS Query Monitoring</h2> <h3 id="what-is-dns-query">What Is DNS Query?</h3> <p>DNS Query refers to the process by which an inquiry is made to the Domain Name System to obtain information about a domain, such as the corresponding IP address. It&rsquo;s a critical function that ensures users can access websites and services smoothly.</p> <h3 id="monitoring-dns-query-with-netdata">Monitoring DNS Query With Netdata</h3> <p>Netdata offers a robust DNS Query monitoring tool that allows users to track the round-trip time (RTT) of DNS queries. Utilizing Netdata, you can efficiently monitor DNS query performance, ensuring that your applications and services maintain optimal connectivity.</p>DNSBL Monitoringhttps://www.netdata.cloud/monitoring-101/dnsbl-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/dnsbl-monitoring/<h2 id="dnsbl-monitoring">DNSBL Monitoring</h2> <h3 id="what-is-dnsbl">What Is DNSBL?</h3> <p>DNSBL, or Domain Name System-based Blackhole List, is a mechanism that helps identify and block email messages from known spammers by using a real-time database of blacklisted IP addresses often employed by email servers to filter out unwanted messages and reduce spam.</p> <h3 id="monitoring-dnsbl-with-netdata">Monitoring DNSBL With Netdata</h3> <p>To monitor DNSBL, Netdata utilizes an openmetrics (Prometheus) exporter. This approach ensures that users can gather comprehensive metrics related to DNSBL effectively. With Netdata, there is no necessity for a dedicated Prometheus server or Grafana setup as Netdata integrates seamlessly with any Prometheus exporter, showcasing automated dashboards, alerts, and in-depth visibility into DNSBL metrics such as domain reputation and security management.</p>DNSdist Monitoringhttps://www.netdata.cloud/monitoring-101/dnsdist-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/dnsdist-monitoring/<h2 id="dnsdist-monitoring">DNSdist Monitoring</h2> <h3 id="what-is-dnsdist">What Is DNSdist?</h3> <p>DNSdist is a highly flexible and powerful DNS proxy server designed to handle a wide range of queries efficiently. It helps balance and protect your DNS infrastructure with advanced features like query filtering, load balancing, and telemetry.</p> <h3 id="monitoring-dnsdist-with-netdata">Monitoring DNSdist With Netdata</h3> <p>Netdata provides unparalleled visibility into DNSdist operations through its comprehensive dashboard. By using the <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/dnsdist/">DNSdist monitoring tool</a>, you can quickly understand traffic patterns, identify bottlenecks, and ensure DNS reliability.</p>Dnsmasq DHCP Monitoringhttps://www.netdata.cloud/monitoring-101/dnsmasq-dhcp-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/dnsmasq-dhcp-monitoring/<h2 id="what-is-dnsmasq-for-dhcp">What is Dnsmasq for DHCP?</h2> <p><a href="https://thekelleys.org.uk/dnsmasq/doc.html">Dnsmasq</a> is an open-source, lightweight, DNS caching and forwarding server. It is designed to provide DNS resolution for small and home networks. Dnsmasq provides local DNS caching, forwarding, and recursive lookups, as well as DHCP, TFTP, and other related services. It also has support for DNS and DHCPv6, as well as various other features such as DNS-over-TLS and IPv6 privacy extensions. Dnsmasq is a versatile and highly configurable tool that is simple to use. DNSMasq_DHCP is a feature of DNSMasq that provides a combined server to serve both DNS (Domain Name System) and DHCP (Dynamic Host Configuration Protocol) requests. It is a fast and lightweight DHCP server with support for both IPv4 and IPv6, and can be used to serve IP addresses to hosts on a LAN. DNSMasq_DHCP also offers features such as DNS and DHCP performance tuning, DHCP address range management, and support for multiple DNS domains.</p>Dnsmasq DHCP Monitoringhttps://www.netdata.cloud/monitoring-101/dnsmasq_dhcp-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/dnsmasq_dhcp-monitoring/<h2 id="dnsmasq-dhcp-monitoring">Dnsmasq DHCP Monitoring</h2> <p>Dnsmasq is a lightweight, easy-to-configure, and highly efficient DHCP server that serves small- to medium-sized networks. Monitoring Dnsmasq DHCP effectively ensures the reliability and performance of your network configuration services.</p> <h3 id="what-is-dnsmasq-dhcp">What Is Dnsmasq DHCP?</h3> <p>Dnsmasq provides network infrastructure for small networks: DNS, DHCP, router advertisement, and network boot. These server functionalities are crucial for network management and troubleshooting.</p> <h3 id="monitoring-dnsmasq-dhcp-with-netdata">Monitoring Dnsmasq DHCP With Netdata</h3> <p>Netdata is the perfect solution for monitoring Dnsmasq DHCP as it provides real-time monitoring, enabling swift identification and resolution of potential network issues. With its turnkey installation, Netdata automatically detects and visualizes metrics needed for effective Dnsmasq DHCP monitoring.</p>Dnsmasq Monitoringhttps://www.netdata.cloud/monitoring-101/dnsmasq-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/dnsmasq-monitoring/<h2 id="dnsmasq-monitoring">Dnsmasq Monitoring</h2> <h3 id="what-is-dnsmasq">What Is Dnsmasq?</h3> <p>Dnsmasq is a lightweight and robust DNS forwarder and DHCP server, perfect for networking tools used in small to medium scale networks. It&rsquo;s designed to be easy to configure while maintaining a wide variety of functionalities. Dnsmasq can cache DNS queries for improved performance of local networks. You can learn more about Dnsmasq on <a href="https://thekelleys.org.uk/dnsmasq/doc.html">its official documentation</a>.</p> <h3 id="monitoring-dnsmasq-with-netdata">Monitoring Dnsmasq With Netdata</h3> <p>Netdata provides an unparalleled real-time monitoring solution for Dnsmasq. By leveraging Netdata&rsquo;s <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/dnsmasq/?utm_source=website&amp;utm_content=monitoring101">Dnsmasq monitoring tool</a>, administrators and developers gain seamless insights into the DNS and DHCP services. Netdata&rsquo;s easy-to-navigate UI, with real-time visualizations, and <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">live demo</a>, brings valuable metrics to the forefront, aiding proactive diagnosis and trend recognition.</p>Docker commands hang: docker ps, inspect, and exec freezeshttps://www.netdata.cloud/guides/docker/docker-commands-hang/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-commands-hang/<p><code>docker ps</code>, <code>docker inspect</code>, and <code>docker exec</code> hang while containers continue serving traffic. This is a Docker daemon hang: the management plane is dead while the data plane survives. Standard process monitors show <code>dockerd</code> as alive, yet you cannot manage, inspect, or evacuate workloads.</p> <p>This guide covers how to distinguish a hang from a crash, identify whether the root cause is storage, a stuck shim, a plugin, or an internal deadlock, and recover without unnecessary host reboots or container kills.</p>Docker Container Can't Connect To Internet: Fixeshttps://www.netdata.cloud/guides/docker/docker-container-cannot-connect-to-internet/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-container-cannot-connect-to-internet/<p>The host may be online while Docker&rsquo;s bridge, iptables rules, DNS proxy, or connection tracking table is in a broken state. Applications fail with connection timeouts, package managers stall, and external health checks return unhealthy. Isolate whether the failure is DNS, routing, packet filtering, or daemon state before fixing it.</p> <h2 id="what-this-means">What this means</h2> <p>Outbound connectivity from a container traverses the container&rsquo;s network namespace, a veth pair attached to a bridge (docker0 or user-defined), iptables NAT and filter rules managed by Docker&rsquo;s libnetwork, the host&rsquo;s routing table, and the upstream physical interface. On user-defined networks, Docker&rsquo;s embedded DNS resolver at 127.0.0.11 proxies queries to the host&rsquo;s configured resolvers. On the default bridge network, there is no embedded DNS; containers inherit the host&rsquo;s /etc/resolv.conf directly. A failure at any layer produces the same symptom: requests time out.</p>Docker container cannot connect to another containerhttps://www.netdata.cloud/guides/docker/docker-container-cannot-connect-to-container/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-container-cannot-connect-to-container/<p>Connection timeouts or &ldquo;connection refused&rdquo; between containers on the same host point to a failure in one of four layers: the bridge network, Docker&rsquo;s embedded DNS, iptables, or the application bind address. Inter-container networking relies on Linux bridges, veth pairs, iptables rules, and an embedded DNS resolver at 127.0.0.11. This guide isolates the faulty layer and fixes it.</p> <h2 id="what-this-means">What This Means</h2> <p><a href="https://www.netdata.cloud/guides/docker/">Docker</a> isolates each container in its own network namespace. Containers on the same custom bridge communicate through a Linux bridge and resolve each other by name via Docker&rsquo;s embedded DNS. The default <code>bridge</code> network has no embedded DNS. If containers are on different networks, if the target application binds to 127.0.0.1, or if iptables rules were wiped by an external firewall reload, traffic stops. The symptom appears at the application layer, but the root cause can be Layer 2, Layer 3, or the application itself.</p>Docker container exits immediately: how to diagnose ithttps://www.netdata.cloud/guides/docker/docker-container-exits-immediately/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-container-exits-immediately/<p>A container that exits immediately prints its ID during <code>docker run</code>, appears briefly in <code>docker ps</code>, then vanishes. <code>docker ps -a</code> lists it as <code>Exited</code> with an uptime measured in seconds. Unlike a restart loop, it stays stopped.</p> <p>A Docker container is a Linux process wrapper, not a virtual machine. Its lifecycle is bound to PID 1 in the container&rsquo;s namespace. When that process completes, crashes, or is killed, the container exits. An immediate exit means the process finished its work, failed to start, or was terminated during initialization. This guide gives you a diagnostic flow to find out why PID 1 terminated, interpret the exit code, and fix the root cause.</p>Docker container high CPU usage: causes and fixeshttps://www.netdata.cloud/guides/docker/docker-container-high-cpu-usage/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-container-high-cpu-usage/<p>A container alert for high CPU is easy to generate but hard to interpret. Docker reports CPU as a percentage of total host cores, so a value of 340% on an 8-core machine simply means the container is using 3.4 cores. That might be expected for a multi-threaded workload, or it might signal a runaway process, CFS throttling, or a cryptominer. This guide shows how to distinguish legitimate compute from pathological behavior, and how to fix the root cause without restarting the container blindly.</p>Docker container high memory usage: how to diagnose ithttps://www.netdata.cloud/guides/docker/docker-container-high-memory-usage/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-container-high-memory-usage/<p>Your container is sitting at 90% of its memory limit but has not been OOMKilled. Or it is being killed repeatedly and you cannot tell whether the limit is too low or the application is leaking. docker stats shows a single percentage, but that number does not reveal the breakdown between reclaimable page cache and anonymous memory that the kernel cannot reclaim. To diagnose this correctly, you need to decompose cgroup memory.stat, map it to your runtime&rsquo;s actual allocations, and decide whether the problem is cache pressure, a runtime mismatch, or a true leak.</p>Docker container keeps restarting: causes, checks, and fixeshttps://www.netdata.cloud/guides/docker/docker-container-keeps-restarting/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-container-keeps-restarting/<p>A container that restarts every few seconds is not self-healing. It is a crash loop that wastes CPU, floods logs, and masks the real failure. Docker&rsquo;s restart policy can hide whether the application is OOM-killed, segfaulting, or waiting for a dependency that never arrives. This guide shows how to read the signals, map exit codes to causes, and stop the loop before it degrades the host.</p> <h2 id="what-this-means">What This Means</h2> <p>When a container&rsquo;s main process exits or is killed, Docker increments <code>RestartCount</code> in the container metadata and starts a new instance if the restart policy allows. The count persists across daemon restarts. A container that crashes immediately on every start creates a death spiral: each cycle truncates ephemeral state, writes new log data, and adds overhead to the daemon and storage driver. The container may appear to be &ldquo;running&rdquo; for a few seconds before it disappears again, which makes the failure easy to miss if you only check whether the process exists.</p>Docker container memory leak: how to find one and prove ithttps://www.netdata.cloud/guides/docker/docker-container-memory-leak/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-container-memory-leak/<p>Memory that only ever climbs is easy to spot. The harder problem is proving whether the growth is a leak, unbounded caching, or a limit set below the working set. During an incident, operators need to decide in minutes whether to page an on-call developer or bump a cgroup limit. This guide shows how to use cgroup memory.stat, process-level RSS, and container restart patterns to build a defensible diagnosis. You will be able to separate anonymous memory growth from <a href="https://www.netdata.cloud/guides/docker/docker-memory-usage-explained/">reclaimable cache</a>, identify whether the leak lives in application heap or runtime overhead, and present evidence that justifies either a code fix or a capacity change.</p>Docker Container Running But Unhealthy: How To Fixhttps://www.netdata.cloud/guides/docker/docker-container-running-but-unhealthy/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-container-running-but-unhealthy/<p>The container is up. <code>docker ps</code> shows it running. But the status is <code>(unhealthy)</code> and your load balancer or orchestrator has stopped sending traffic. This means Docker&rsquo;s health check command is returning a non-zero exit code, or timing out, while the container&rsquo;s main process stays alive. The container is running, but Docker does not consider it ready.</p> <p>An unhealthy state is not a crash. In Swarm, it triggers replacement. In Compose, <code>depends_on</code> with <code>condition: service_healthy</code> blocks downstream services. Even on a single host, an unhealthy mark often precedes a restart loop that buries the real error in noise. You need to distinguish between a broken application, a broken probe, and a broken runtime configuration.</p>Docker CPU throttling: the hidden cause of container latencyhttps://www.netdata.cloud/guides/docker/docker-cpu-throttling/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-cpu-throttling/<p>Your application latency just spiked. p99 response times doubled or tripled. CPU dashboards show the container at 40% utilization. Memory is fine. Network is quiet. You restart the container, redeploy, or blame the code, but the pattern repeats.</p> <p>The culprit is often CPU throttling. <a href="https://www.netdata.cloud/guides/docker/">Docker</a> uses Linux CFS bandwidth control to enforce CPU limits in discrete 100ms periods. A container can exhaust its quota in a burst, spend the rest of each period throttled by the kernel, and still report a modest average CPU over a longer window. This guide shows how to confirm throttling from cgroup metrics, calculate its severity, and fix it without guessing.</p>Docker daemon not responding: how to troubleshoot a hung dockerdhttps://www.netdata.cloud/guides/docker/docker-daemon-not-responding/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-daemon-not-responding/<p>A hung Docker daemon is one of the more disorienting production failures you can face. The process is still running, your containers are still serving traffic, but every <code>docker</code> command hangs. You cannot inspect, stop, or create containers. Deployments stall. Automation times out.</p> <p>This guide covers the diagnostic ladder from socket probe to storage driver investigation, explains when to wait versus when to restart, and describes what to avoid when you are not sure what is wrong.</p>Docker disk space full: how to troubleshoot /var/lib/dockerhttps://www.netdata.cloud/guides/docker/docker-disk-space-full/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-disk-space-full/<p>You notice deployments failing with &ldquo;no space left on device,&rdquo; image pulls hanging, or the Docker daemon becoming sluggish. On a <a href="https://www.netdata.cloud/guides/docker/">Docker</a> host, everything lives under /var/lib/docker: image layers, container writable layers and logs, named volumes, and build cache. When this filesystem fills, the failure is cascading and abrupt. New containers cannot start, running containers may fail on writes, and daemon operations deadlock.</p> <p>This guide walks through identifying which of the five major consumers is dominating your disk, safely reclaiming space without deleting data you still need, and fixing the configuration gaps that let it happen again.</p>Docker DNS not working inside containershttps://www.netdata.cloud/guides/docker/docker-dns-not-working/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-dns-not-working/<p>Your application logs show connection timeouts. Health checks against dependency names are failing. <code>curl</code> from inside a container returns &ldquo;Could not resolve host&rdquo; while the same name resolves fine on the host. DNS inside Docker is not a simple passthrough to the host resolver. It is a stack of namespace-specific forwarders, embedded resolvers, and inherited configuration that breaks in specific, repeatable ways.</p> <p>This guide will help you determine whether the failure is a missing embedded DNS, a poisoned resolv.conf, an upstream forwarding issue, or a version regression. You will be able to distinguish between inter-container name resolution failures and external lookup failures, identify the root cause with safe read-only checks, and apply the correct fix without guessing.</p>Docker exit code 1: application errors and how to find themhttps://www.netdata.cloud/guides/docker/docker-exit-code-1/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-exit-code-1/<p>A container exiting immediately with code 1 is a common production incident. Unlike exit code 137 (OOM killer) or code 125 (Docker daemon error), code 1 means the application inside the container called <code>exit(1)</code>. <a href="https://www.netdata.cloud/guides/docker/">Docker</a> is only reporting what PID 1 did.</p> <p>The challenge is that code 1 is a catch-all. It can mask an unhandled JavaScript exception, a Python import error, a missing configuration file, a shell script failing under <code>set -e</code>, or a Go binary that cannot reach its database. Time spent checking Docker daemon health or host memory is wasted when the real failure is an application-level error written to stdout or stderr.</p>Docker exit code 137: OOMKilled or SIGKILL?https://www.netdata.cloud/guides/docker/docker-exit-code-137/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-exit-code-137/<p>A container exits with code 137. Docker restarts it, or it stays down, and you need to know why. The number itself only tells you that the process received SIGKILL. What matters for your next step is whether the kernel&rsquo;s cgroup OOM killer fired because the container exceeded its memory limit, or whether an external actor sent the signal. The remediation for an undersized memory limit is completely different from fixing a misconfigured stop timeout or an orchestrator sending a premature kill. This guide shows how to classify the cause in under a minute using only the Docker CLI and cgroup files.</p>Docker exit code 143: SIGTERM and graceful shutdown failureshttps://www.netdata.cloud/guides/docker/docker-exit-code-143/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-exit-code-143/<p>You are reviewing container exit codes after a deployment or node drain and see 143. If your monitoring alerts on it, you might think something failed. Exit code 143 is not an error. It is 128 plus signal 15 (SIGTERM), and it means the container&rsquo;s PID 1 process received SIGTERM and exited voluntarily. This is exactly what <code>docker stop</code> is designed to do.</p> <p>The operational problem is not the code itself, but what happens around it. If your application never receives the signal, it gets SIGKILL after the timeout and exits 137, potentially dropping connections and corrupting state. If your orchestrator pages you for 143 during a normal rolling restart, your alerts are noisy. If your stop timeout is too short for your database to finish checkpointing, you risk data inconsistency.</p>Docker Hub Monitoringhttps://www.netdata.cloud/monitoring-101/dockerhub-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/dockerhub-monitoring/<h2 id="docker-hub-monitoring">Docker Hub Monitoring</h2> <h3 id="what-is-docker-hub">What Is Docker Hub?</h3> <p>Docker Hub is a cloud-based repository where Docker users and partners create, test, store, and distribute container images. It is the centralize hub for approximately 100,000 container images; providing the ability to automate workflows, build images from GitHub or Bitbucket, and distribute them to your users.</p> <h3 id="monitoring-docker-hub-with-netdata">Monitoring Docker Hub With Netdata</h3> <p>To effectively monitor Docker Hub, leverage the insightful metrics retrieved by Netdata’s robust monitoring agent—the go-to Docker Hub monitoring tool. Netdata&rsquo;s Docker Hub collector keeps track of your repository statistics, providing essential visibility into its health and performance.</p>Docker image cleanup: safe pruning strategies for production hostshttps://www.netdata.cloud/guides/docker/docker-image-cleanup/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-image-cleanup/<p>When <code>df -h /var/lib/docker</code> shows 87% utilization, the urge to run <code>docker system prune -a</code> is strong. On production hosts, that is a mistake. Cleanup is not about finding the single command that reclaims the most space. It is about knowing exactly what each flag deletes, what it leaves behind, and which filters prevent a 3 a.m. image re-pull because a base layer was removed.</p> <p>This guide covers the safe pruning hierarchy: dangling images, unused tagged images, build cache, and the dangerous flags that touch volumes or running workloads. The goal is to reclaim space, automate cleanup safely, and avoid outage patterns caused by aggressive pruning.</p>Docker image pull failures: registry, network, and auth diagnosishttps://www.netdata.cloud/guides/docker/docker-image-pull-failures/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-image-pull-failures/<h2 id="what-this-means">What This Means</h2> <p>When you run <code>docker pull</code>, the daemon negotiates a TLS connection to the registry, authenticates if required, resolves the manifest for the requested tag and architecture, then downloads missing layers. If any step fails, the pull aborts.</p> <p>Registry errors surface as HTTP 429 or 401/403 responses. Network errors appear as timeouts, connection resets, or TLS handshake failures. Local problems such as a full disk or a hung daemon can also abort a pull even when the registry is healthy. In orchestrated environments, a single node&rsquo;s pull failure can trigger the scheduler to retry on other nodes, turning a localized auth error into a cluster-wide rate limit storm. Distinguishing these layers quickly is the difference between a five-minute fix and a prolonged outage.</p>Docker JVM memory tuning: heap, off-heap, and the cgroup mismatchhttps://www.netdata.cloud/guides/docker/docker-jvm-memory-tuning/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-jvm-memory-tuning/<p>Your Java container is <a href="https://www.netdata.cloud/guides/docker/docker-oomkilled/">OOMKilled</a> at 02:00. Heap usage is 60%. Docker reports exit code 137 and <code>OOMKilled: true</code>. The JVM never threw an <code>OutOfMemoryError</code>.</p> <p>In a container, the kernel enforces memory limits through cgroups, but the JVM heap is only one component of process RSS. Off-heap memory, metaspace, thread stacks, direct byte buffers, and GC overhead all count against the same cgroup limit. When total RSS crosses that limit, the kernel kills the container without a JVM-level error. In some JDK and kernel combinations, the JVM fails to detect the cgroup limit entirely and sizes the heap against host RAM, which guarantees an OOM kill.</p>Docker log rotation: preventing json-file logs from filling diskhttps://www.netdata.cloud/guides/docker/docker-log-rotation/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-log-rotation/<p>Docker&rsquo;s default <code>json-file</code> log driver appends every line of container stdout and stderr to a JSON file on the host under <code>/var/lib/docker/containers/&lt;id&gt;/</code>. Without size limits, that file grows monotonically. A single verbose container can consume tens of gigabytes, and because the driver is the default, this often happens silently until <code>/var/lib/docker</code> fills. At that point image pulls fail, container creates are rejected, and the daemon may hang on storage operations. This guide covers how to cap log files with <code>daemon.json</code> and per-container <code>log-opt</code> overrides, verify the caps are working, and choose a different driver when json-file is not appropriate.</p>Docker logs taking too much disk space: how to fix log growthhttps://www.netdata.cloud/guides/docker/docker-logs-disk-space/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-logs-disk-space/<p>The default json-file logging driver captures every line a container writes to stdout and stderr and appends it to a file under <code>/var/lib/docker/containers/</code>. There is no size limit out of the box. A container with verbose logging, a stuck retry loop, or a crash spiral can grow its log file by gigabytes per day until the filesystem is full.</p> <p>When <code>/var/lib/docker</code> fills, the impact is not limited to logging. <a href="https://www.netdata.cloud/guides/docker/">Docker</a> cannot create new containers, <a href="https://www.netdata.cloud/guides/docker/docker-image-cleanup/">image pulls fail</a>, running containers may error on writes, and the daemon can hang during storage operations. This article shows how to identify which containers are responsible, safely reclaim space without restarting workloads, and configure durable limits so the problem does not recur.</p>Docker memory limits: how to set them and what happens when they hithttps://www.netdata.cloud/guides/docker/docker-memory-limits/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-memory-limits/<p>A container without a memory limit can consume all available RAM, force the kernel to reclaim page cache, push the system into swap, and eventually trigger a host-level OOM kill that takes down the Docker daemon or other critical processes. Setting <code>--memory</code> is not enough: limits can be silently ignored, misread by runtimes, or masked by swap behavior that turns a clean failure into a slow crawl.</p> <p>Exit code 137 can mean an OOM kill or an external SIGKILL. The difference matters because the fix for an undersized limit is not the same as the fix for a runtime sizing its heap from host memory instead of the cgroup limit.</p>Docker memory usage explained: anonymous, file, slab, and what countshttps://www.netdata.cloud/guides/docker/docker-memory-usage-explained/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-memory-usage-explained/<p>You see a container using 1.2 GB of a 1.5 GB cgroup limit and assume it is about to explode. It might be fine. The raw cgroup total includes page cache the kernel can reclaim under pressure; <code>docker stats</code> subtracts inactive file cache. Meanwhile, a different container reports 600 MB with no limit set, yet its anonymous memory grows 50 MB per hour and will force a host-level OOM kill before lunch.</p>Docker Monitoringhttps://www.netdata.cloud/monitoring-101/docker-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/docker-monitoring/<h2 id="docker-monitoring">Docker Monitoring</h2> <h3 id="what-is-docker">What Is Docker?</h3> <p>Docker is an open platform that packages applications and their dependencies into lightweight, portable units called <strong>containers</strong>. A container bundles everything the software needs to run — code, runtime, system tools, libraries, and settings — so it behaves the same way on a developer&rsquo;s laptop, in staging, and in production. Because containers share the host operating system&rsquo;s kernel instead of shipping a full guest OS, they start in milliseconds and use far fewer resources than virtual machines.</p>Docker monitoring checklist: the signals every production host needshttps://www.netdata.cloud/guides/docker/docker-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-monitoring-checklist/<p>Production Docker incidents rarely look like Docker problems at first. They show up as application latency, deployment failures, or hosts that suddenly refuse to schedule containers. By the time you notice, the daemon may be hung, a log file has filled the disk, or a container has been silently throttled into unusable latency. This checklist groups the essential production signals into three priority tiers: must-have alerts that keep the host alive, should-have metrics that expose resource pressure before it becomes an outage, and nice-to-have security and internal signals for mature environments. Every signal includes where to read it from the raw cgroup filesystem or the Docker API so you can instrument hosts without guessing paths.</p>Docker OOMKilled: causes, detection, and preventionhttps://www.netdata.cloud/guides/docker/docker-oomkilled/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-oomkilled/<p>A container exits with code 137 and restarts. The application loses in-memory state. Dependent services start failing. The restart loop begins. This is the OOMKilled pattern, and it is one of the most common and most misdiagnosed failure modes in Docker environments.</p> <p>This article covers how to confirm an OOM kill, distinguish it from an external SIGKILL, understand why it happened, and prevent recurrence. It also covers the JVM-in-container memory mismatch, which is responsible for a large share of OOM kills in Java workloads.</p>Docker port binding: address already in usehttps://www.netdata.cloud/guides/docker/docker-port-binding-address-already-in-use/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-port-binding-address-already-in-use/<p>A <code>docker run -p 8080:80</code> or <code>docker compose up</code> fails with <code>bind: address already in use</code>. The error is clear, but the owner is not. <code>ss</code> may show a system service. <code>docker ps</code> may show nothing, yet Docker still refuses. The port can appear free while an orphaned DNAT rule or a split firewall backend blocks the bind.</p> <p>Distinguish a genuine socket conflict from an orphaned DNAT rule, a rootless Docker regression, and a WSL2 iptables/nftables split brain. Then reclaim the port and prevent recurrence.</p>Docker published port not reachable: troubleshooting -p and EXPOSEhttps://www.netdata.cloud/guides/docker/docker-published-port-not-reachable/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-published-port-not-reachable/<p>You mapped a port with <code>-p 8080:80</code>, but <code>curl</code> against the host IP returns connection refused. <code>docker ps</code> shows the mapping, the container is running, and the port still appears closed.</p> <p>A published port depends on three layers: a runtime mapping rule (<code>-p</code>), a host forwarding path (iptables DNAT and FORWARD policy), and an application listener inside the container bound to an interface that receives the forwarded packet. EXPOSE in a Dockerfile is metadata. It does not publish ports, create firewall rules, or set bind addresses.</p>Docker socket security: why /var/run/docker.sock is root accesshttps://www.netdata.cloud/guides/docker/docker-socket-security/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-socket-security/<p>Mounting <code>/var/run/docker.sock</code> into a container grants that container a root-equivalent privilege boundary. This is not a Docker vulnerability. The daemon runs as root, listens on a filesystem socket, and trusts any client that can write to it.</p> <p>Symptoms of abuse look like container escape or host compromise, but the container never escaped. It asked the root-owned daemon to perform privileged operations on its behalf. This guide explains the mechanism, how to audit exposure, and what constraints you can apply without rebuilding your pipeline.</p>Docker volume cleanup: finding and removing orphaned volumeshttps://www.netdata.cloud/guides/docker/docker-volume-cleanup/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-volume-cleanup/<p>Run <code>docker system df</code> and the <code>Local Volumes</code> line keeps growing. Run <code>docker system prune</code> and you reclaim images and build cache, but the volume count barely drops. A few weeks later the disk alert fires again.</p> <p>Data persists in <code>/var/lib/docker/volumes/</code> after its consumer is long gone. These volumes waste disk, complicate capacity planning, and can hide sensitive data in forgotten corners of the filesystem.</p> <p>This guide covers how Docker volumes become orphaned, how to distinguish unused volumes from named data stores that should stay, and how to remove them safely.</p>Domain Monitoringhttps://www.netdata.cloud/monitoring-101/whoisquery-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/whoisquery-monitoring/<h2 id="domain-monitoring">Domain Monitoring</h2> <h3 id="what-is-domain-monitoring">What Is Domain Monitoring?</h3> <p>Domain monitoring involves tracking various domain-related metrics such as the time until a domain expires. This ensures that your domain remains operational without unexpected downtime due to expiry. By using tools designed for monitoring domains, businesses can avoid disruptions to their online presence.</p> <h3 id="monitoring-domain-expiration-with-netdata">Monitoring Domain Expiration With Netdata</h3> <p>Netdata offers a comprehensive domain monitoring tool through its WhoisQuery module. This tool helps in tracking domain expiration dates effectively. By integrating this into your monitoring strategy, you can maintain continuous oversight of your domains’ expiration status and take proactive measures to renew them on time.</p>Dovecot Monitoringhttps://www.netdata.cloud/monitoring-101/dovecot-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/dovecot-monitoring/<h2 id="dovecot-monitoring">Dovecot Monitoring</h2> <h3 id="what-is-dovecot">What Is Dovecot?</h3> <p>Dovecot is a widely-used open-source IMAP and POP3 server for Unix-like operating systems. Its focus on security, ease of use, and performance makes it a preferred choice for many system administrators when it comes to mail server deployments. For more details on Dovecot, visit the <a href="https://www.dovecot.org/">official Dovecot website</a>.</p> <h3 id="monitoring-dovecot-with-netdata">Monitoring Dovecot With Netdata</h3> <p>Netdata provides a comprehensive $name monitoring tool designed to capture and visualize a wide array of metrics from your Dovecot server. By monitoring Dovecot with Netdata, you gain real-time insights into your server&rsquo;s performance, understand traffic patterns, and detect anomalies that could indicate underlying issues.</p>Dutch Electricity Smart Meter Monitoringhttps://www.netdata.cloud/monitoring-101/dutch_electricity_smart_meter-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/dutch_electricity_smart_meter-monitoring/<h2 id="dutch-electricity-smart-meter-monitoring">Dutch Electricity Smart Meter Monitoring</h2> <h3 id="what-is-dutch-electricity-smart-meter">What Is Dutch Electricity Smart Meter?</h3> <p>Dutch Electricity Smart Meters are advanced IoT devices used for tracking energy consumption in households. They provide granular data through the P1 port, which is beneficial for energy management and efficient monitoring. To gather insights, these meters can be hooked up with various monitoring tools, such as the Prometheus P1 Exporter.</p> <h3 id="monitoring-dutch-electricity-smart-meters-with-netdata">Monitoring Dutch Electricity Smart Meters With Netdata</h3> <p>To monitor Dutch Electricity Smart Meters, Netdata utilizes an openmetrics (Prometheus) exporter. This integration enables Netdata to ingest data from any Prometheus exporter. With this setup, users benefit from Netdata’s automated dashboards, alerts, and other features without the need for a Prometheus server or Grafana. This means you can have a comprehensive and real-time view of your smart meter data effortlessly.</p>Dynatrace Monitoringhttps://www.netdata.cloud/monitoring-101/dynatrace-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/dynatrace-monitoring/<h2 id="dynatrace-monitoring">Dynatrace Monitoring</h2> <h3 id="what-is-dynatrace">What Is Dynatrace?</h3> <p>Dynatrace is a leading application performance management (APM) solution that provides comprehensive visibility into your applications, infrastructure, and user experiences. It is designed to help organizations monitor, optimize, and scale their environments effectively. Whether it&rsquo;s cloud-native applications or more traditional server-client architectures, Dynatrace offers automated and intelligent observability across the stack.</p> <h3 id="monitoring-dynatrace-with-netdata">Monitoring Dynatrace With Netdata</h3> <p>Monitoring Dynatrace with Netdata offers seamless integration via the openmetrics (Prometheus) exporter. Netdata can ingest metrics from any Prometheus exporter, allowing it to create automated dashboards, alerts, and more without the need for a Prometheus server or Grafana. By utilizing the <a href="https://github.com/Apside-TOP/dynatrace_exporter">Dynatrace Exporter</a>, you can easily monitor Dynatrace metrics in real-time with Netdata, enabling better application performance management.</p>Elasticsearch All Shards Failed: How To Fix Ithttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-all-shards-failed/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-all-shards-failed/<p>You run a search and Elasticsearch returns <code>search_phase_execution_exception</code> with reason <code>all shards failed</code>. Every shard copy involved in the query returned a failure to the coordinating node. The outer error is a container; the actual root cause lives in the per-shard failure reasons inside the response body. Do not assume the cluster is down. This error fires on clusters with green health and stable nodes when a query is malformed, a mapping is incompatible, or a resource limit is breached uniformly across every target shard.</p>Elasticsearch ALLOCATION_FAILED after max retries: reroute and corrupt shard recoveryhttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-shard-allocation-failed-max-retries/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-shard-allocation-failed-max-retries/<p>A shard that repeatedly fails allocation exhausts <code>index.allocation.max_retries</code> (default 5) and becomes permanently UNASSIGNED. Elasticsearch stops automatic placement. Cluster health is RED if the shard is a primary, YELLOW if it is a replica. Indexing to the affected index is blocked until the primary is assigned.</p> <p>This state typically follows transient node restarts, disk pressure events, or translog corruption. After the fifth failed attempt, the allocator stops retrying. The shard will not move without explicit operator action: <code>POST /_cluster/reroute?retry_failed=true</code> for transient failures, or forced allocation with accepted data loss when no valid copy remains.</p>Elasticsearch cluster health red: unassigned primaries and how to recoverhttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-cluster-health-red/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-cluster-health-red/<p>Cluster health <code>red</code> means at least one primary shard is unassigned. Queries against affected indices return partial results or fail; writes are blocked. <code>yellow</code> only signals missing replicas, but <code>red</code> signals active data unavailability.</p> <p>Cluster health is a lagging indicator. A red status sustained longer than two minutes after the cluster has formed is a real fault; a brief flash during startup is normal. By the time the status turns red, a node has likely departed, a disk has crossed a watermark, or a shard copy has been rejected as corrupt.</p>Elasticsearch cluster health yellow: unassigned replicas vs real allocation blockshttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-cluster-health-yellow/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-cluster-health-yellow/<p><code>GET /_cluster/health</code> returning <code>status: yellow</code> means all primaries are assigned but at least one replica is not. Some clusters are yellow by design. Others are yellow because a disk cascade, stuck allocator, or failed shard is blocking recovery. Benign yellow resolves. Structural yellow persists. If your cluster has been yellow for more than thirty minutes, something is actively blocking allocation. Teams that treat yellow as cosmetic often miss the transition from transient recovery to a real incident, leaving them one node failure away from red.</p>Elasticsearch cluster state too large: field count, index count, and per-node heaphttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-cluster-state-too-large/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-cluster-state-too-large/<p>Every node holds a copy of the cluster state in heap. When it grows large, the cost is paid everywhere: 200 MB of state consumes 200 MB on every node, and the elected master burns additional CPU and heap serializing and publishing updates. Symptoms show up indirectly: the master feels sluggish, pending tasks queue for minutes, heap pressure climbs on nodes that should be idle, and master elections stall indexing and shard allocation. The usual drivers are too many indices from per-minute or per-hour time-series patterns; a mapping explosion from uncontrolled dynamic fields; excessive aliases; or churn from frequent template and setting changes. Raw size measured via <code>/_cluster/state</code> is a rough proxy. The indicators that matter are field-count growth, cluster state version churn, pending-task age, and master node heap pressure.</p>Elasticsearch cluster_block_exception: blocked by, the read-only blocks explainedhttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-cluster-block-exception/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-cluster-block-exception/<p>Elasticsearch returns <code>cluster_block_exception</code> when a write or metadata operation hits an active index or cluster-level block. The <code>blocked by</code> array contains a <code>FORBIDDEN</code> or <code>TOO_MANY_REQUESTS</code> string, a numeric code, and an API label. Writes stop. Depending on the code, deletes and metadata changes may also fail.</p> <p>This article maps the four numeric codes most common in production, explains how to confirm which block is active, and gives the exact commands to clear it. Most incidents involve the <code>/12</code> flood-stage disk watermark, but manual index blocks and cluster-level overrides produce the same exception and require different fixes.</p>Elasticsearch coordinating node overload: aggregation merge, heap spikes, and 429shttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-coordinating-node-overload/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-coordinating-node-overload/<p>HTTP 429 or 503 responses appear on search requests while data nodes look healthy. Heap spikes on one node while others stay flat. The slow log shows heavy aggregation queries. That node is the coordinator, and it is running out of heap during the reduce phase.</p> <p>Every node can act as a coordinating node. For each search, the coordinator broadcasts the query to relevant shards, collects partial results, and merges them. Aggregations compute locally per shard and reduce in memory on the coordinator. High-cardinality terms aggregations, deep pagination, or large fetch sizes force the coordinator to hold massive intermediate structures in heap. If the estimate exceeds the circuit breaker limit, the request is rejected. If the breaker is too slow, the node may suffer long GC pauses or disconnect from the cluster.</p>Elasticsearch disk full: emergency recovery and freeing space safelyhttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-disk-full-emergency-recovery/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-disk-full-emergency-recovery/<p>Writes fail with <code>TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block</code>. Cluster health is red or yellow and data nodes are pinned above 90 percent disk. Indexers buffer or drop data while the cluster attempts shard relocations onto already-full disks. Recover without corrupting metadata or amplifying pressure.</p> <h2 id="what-this-means">What this means</h2> <p>Elasticsearch uses three disk watermarks. Low (85 percent) stops new shard allocation. High (90 percent) starts relocating shards off the node. Flood stage (95 percent) forces every index with a shard on that node into <code>index.blocks.read_only_allow_delete: true</code>, which stops writes.</p>Elasticsearch disk watermark cascade: from low watermark to cluster-wide read-onlyhttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-disk-watermark-cascade/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-disk-watermark-cascade/<p>Writes fail with <code>cluster_block_exception</code> or <code>FORBIDDEN/12/index read-only / allow delete (api)</code>. Kibana becomes unreachable; Logstash and Beats buffer or drop data. The cluster did not fail at once. It crossed a sequence of thresholds that turned single-node disk pressure into a cluster-wide write outage. With homogeneous disk sizes, every data node likely hit the thresholds within minutes, leaving no relocation target and no relief valve.</p> <p>Elasticsearch uses three disk watermarks. The low watermark (85% by default) stops new shard allocation. The high watermark (90%) triggers shard relocation, which consumes I/O and disk on both source and target. The flood stage (95%) forces every index with a shard on the affected node into a <code>read_only_allow_delete</code> state. Writes stop, but relocation traffic may still run, compounding the pressure.</p>Elasticsearch EsRejectedExecutionException: write thread pool rejections and HTTP 429https://www.netdata.cloud/guides/elasticsearch/elasticsearch-esrejectedexecutionexception-write-queue/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-esrejectedexecutionexception-write-queue/<p>HTTP 429 responses from Elasticsearch, or stack traces containing <code>EsRejectedExecutionException</code>, mean the <code>write</code> thread pool queue is full. The <code>write</code> thread pool (named <code>bulk</code> before Elasticsearch 6.3) executes indexing, bulk, update, and delete operations on each data node using a bounded queue. When all threads are busy and the queue fills, the node rejects the operation. This guide covers how to confirm the diagnosis, distinguish it from other rejection paths, and fix the root cause instead of masking the symptom.</p>Elasticsearch expensive queries: leading wildcards, regex, deep pagination, and scriptshttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-expensive-queries/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-expensive-queries/<p>Search latency spikes and data-node CPU saturation usually trace to one of four query patterns: leading wildcards or unbounded regex, deep <code>from+size</code> pagination, runtime Painless scripts, and deep aggregations. Elasticsearch uses a scatter-gather read path: the coordinating node broadcasts every query to one copy of every target shard. A single expensive query fans out, and the slowest shard sets overall latency. Coordinating-node heap pressure rises when it merges large intermediate result sets during the fetch phase or aggregation reduce phase.</p>Elasticsearch exposed without authentication: open clusters and snapshot exfiltrationhttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-exposed-without-authentication/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-exposed-without-authentication/<p>TCP/9200 is externally reachable and responds without credentials. When Elasticsearch binds to a public interface with security disabled, anyone who can reach the HTTP port can query indices, modify cluster state, and register snapshot repositories. The fastest exfiltration path is not reading documents individually. It is registering an attacker-controlled snapshot repository and copying entire indices out in a single background operation.</p> <p>This article explains how to confirm exposure, identify active or past exfiltration, and lock the cluster down without causing an outage.</p>Elasticsearch fielddata circuit breaker tripped: text-field aggregations and the keyword fixhttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-fielddata-circuit-breaker-tripped/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-fielddata-circuit-breaker-tripped/<p>Queries return <code>CircuitBreakingException: [fielddata] Data too large...</code> and HTTP 429s while JVM heap on one or more data nodes climbs toward the breaker limit. The node rejects queries to protect itself before OOM. This almost always means a query is aggregating, sorting, or scripting against an analyzed <code>text</code> field that lacks a <code>keyword</code> sub-field, forcing Elasticsearch to load an expensive fielddata cache into heap.</p> <p>Analyzed <code>text</code> fields are tokenized and optimized for full-text search, not columnar operations such as <code>terms</code> aggregations or sorting. Running these against a raw <code>text</code> field forces Elasticsearch to uninvert the inverted index per segment into an in-memory structure called fielddata. This cache consumes JVM heap proportional to unique term cardinality. On large indices it approaches the fielddata circuit breaker limit, which defaults to 40% of the JVM heap.</p>Elasticsearch FORBIDDEN/12/index read-only / allow delete (api) — flood stage recoveryhttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-forbidden-12-index-read-only-allow-delete/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-forbidden-12-index-read-only-allow-delete/<p>When Elasticsearch returns <code>cluster_block_exception</code> with <code>FORBIDDEN/12/index read-only / allow delete (api)</code>, every write, update, and index creation fails with HTTP 403. Search continues to work.</p> <p>This happens when a data node crosses the flood-stage disk watermark (95% by default). Elasticsearch auto-applies <code>index.blocks.read_only_allow_delete</code> to every index with a shard on that node, preventing writes to avoid Lucene segment corruption from a full disk.</p> <p>In 7.x and 8.x, the block auto-clears once disk usage drops below the high watermark (90%). If you cannot reach that threshold, or if you need writes to resume immediately after freeing space, clear the block manually. Until then, ingestion pipelines back up and time-series data is lost.</p>Elasticsearch heap pressure death spiral: GC, node removal, and the cascadehttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-heap-pressure-death-spiral/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-heap-pressure-death-spiral/<p>When a node drops from <code>_cat/nodes</code> and network tests pass, check its JVM GC logs. Stop-the-world pauses over 10 seconds cause the master to remove the node. Survivors then absorb recovery traffic, their heap climbs, and they begin missing fault-detection checks too. This feedback loop is the heap pressure death spiral. It masquerades as network instability because operators check connectivity while the real problem is memory saturation.</p> <h2 id="what-this-means">What this means</h2> <p>By default, Elasticsearch fault detection removes a node after roughly 10-15 seconds of sustained unresponsiveness. A stop-the-world GC pause that prevents the node from responding to fault-detection checks triggers this removal. A hard TCP disconnect removes the node immediately.</p>Elasticsearch high disk watermark [90%] exceeded: shard relocation and the cascadehttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-high-disk-watermark-exceeded/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-high-disk-watermark-exceeded/<p>When Elasticsearch logs <code>high disk watermark [90%] exceeded on [node] ... shards will be relocated away</code>, the allocator immediately begins moving shards off the affected node. Relocation generates disk I/O and network traffic on both source and target. If targets were already close to their own watermarks, incoming shards can push them past 90%. This is the disk watermark cascade: a self-reinforcing loop where one full node triggers relocations that make other nodes full, eventually leaving the cluster with no legal allocation target and, if flood stage is hit, read-only indices.</p>Elasticsearch ILM stuck: indices not rolling over, shrinking, or deletinghttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-ilm-stuck/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-ilm-stuck/<p>Disk usage climbs steadily. Old indices that should have been deleted remain. Shard count grows, and the cluster approaches <code>cluster.max_shards_per_node</code>. In ILM, indices are stuck in one phase for hours or days. This is the ILM stuck pattern: silent accumulation that becomes a disk watermark crisis, heap pressure, or unassigned shard storm when the cluster runs out of room.</p> <p>ILM polls every ten minutes by default. When an index cannot advance, it sits. Because the failure is gradual, it rarely pages until a secondary limit is breached. Detect the stuck state early and fix the root cause before accumulation triggers cascading failures.</p>Elasticsearch indexing rate dropped to zero: where the write path stallshttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-indexing-rate-dropped/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-indexing-rate-dropped/<p>Your ingestion pipeline reports healthy connections, but Elasticsearch stopped accepting writes. The <code>index_total</code> counter is flat, upstream queues are building, and documents are erroring or disappearing. Because <code>index_total</code> increments for every document, update, delete, and individual bulk item, a sustained rate of zero means the write path is stalled. The cluster may still report green health, nodes may still respond to pings, and search may still work, but the pipeline is backed up.</p>Elasticsearch JVM heap usage high: reading the sawtooth and the post-GC floorhttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-jvm-heap-high/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-jvm-heap-high/<p>Your Elasticsearch alert fires: <code>jvm.mem.heap_used_percent</code> has crossed 75 percent and is holding there. You pull up the graph and see a jagged sawtooth climbing toward the ceiling. The first instinct is to add heap or restart the node. Both are usually wrong.</p> <p>The sawtooth is normal. Elasticsearch runs on the JVM with a young generation that fills with short-lived objects and empties on young garbage collections. The peak of the tooth is noise. The signal that matters is the post-GC floor: the minimum heap used immediately after a collection. In a healthy node, the floor stays between roughly 30 and 50 percent of max heap, and young GC dominates. When the floor trends upward, old generation objects are accumulating. Old GC pauses stop the world, and once a pause exceeds the cluster fault detection timeout, the master removes the node and triggers shard reallocation. That reallocation places more heap pressure on the survivors, beginning a death spiral.</p>Elasticsearch Limit of total fields [1000] in index has been exceeded — mapping explosionhttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-limit-of-total-fields-exceeded/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-limit-of-total-fields-exceeded/<p>Every write suddenly returns <code>illegal_argument_exception: Limit of total fields [1000] in index [X] has been exceeded</code>. Indexing stops. The temptation is to raise <code>index.mapping.total_fields.limit</code> and move on. Do not. This is a mapping explosion: dynamic mapping creates a new field for every unique key in your documents. The 1000-field limit is a guardrail, not the root cause. Runaway mappings bloat the cluster state, inflate heap on every node, and eventually destabilize the master. Diagnose the source, relieve pressure safely, and fix the data shape so it does not recur.</p>Elasticsearch long GC pauses: old-generation stop-the-world and node dropshttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-old-gc-long-pauses/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-old-gc-long-pauses/<p>In Elasticsearch 8.x, nodes can drop out of the cluster without logging errors. The master logs <code>node-left</code> with reason <code>disconnected</code>, while the departed node shows no ERROR entries because its JVM was frozen in an old-generation stop-the-world GC pause. A single pause longer than 10 seconds fails a fault-detection check; roughly 30 seconds of total unresponsiveness triggers removal. Once the master reallocates shards, remaining nodes face additional heap pressure and the cascade continues.</p>Elasticsearch mapper_parsing_exception: type conflicts and failed document indexinghttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-mapper-parsing-exception/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-mapper-parsing-exception/<p>Document counts do not match what your pipeline sent. The <code>_bulk</code> endpoint returns HTTP 200, yet documents are missing from queries. In the Elasticsearch logs you see <code>mapper_parsing_exception</code> with messages like <code>failed to parse field [fieldname] of type [typename] in document with id [id]</code>. The <code>indices.indexing.index_failed</code> counter is climbing. This is a per-document schema rejection, not a cluster outage, and it silently drops data.</p> <p>The error means the primary shard refused a document because a field value does not match the mapping declared for that field, or because the index uses <code>dynamic: strict</code> and the document contains an unknown field. The document is rejected in its entirety; other fields in the same document are not indexed. The bulk API returns HTTP 200 whenever the request body is valid NDJSON, so failures hide inside the per-item response array.</p>Elasticsearch mapping explosion: dynamic mapping, cluster state bloat, and master pressurehttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-mapping-explosion-dynamic-mapping/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-mapping-explosion-dynamic-mapping/<p>When an Elasticsearch cluster ingesting unstructured JSON starts accumulating thousands of mapped fields per index, every node pays for it in heap. Mappings are part of the cluster state, which the elected master serializes and publishes to every node on each change. An index mapping with tens of thousands of fields means a larger cluster state blob resident in every node&rsquo;s JVM heap, longer publication times, and mounting pressure on the master.</p>Elasticsearch master instability: frequent elections and metadata overloadhttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-master-instability-flapping/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-master-instability-flapping/<p>Index creation requests time out. <code>_cluster/health</code> hangs or returns timeouts. The node listed by <code>_cat/master</code> changes every few minutes outside planned maintenance. Shard allocation stalls, and new indices stay red or unassigned even though all data nodes are reachable. These symptoms indicate a master node that cannot keep up with cluster state updates, triggering repeated elections and leaving the cluster without stable coordination.</p> <p>This is metadata overload. The elected master maintains the cluster state: a heap-resident data structure describing every index, shard, mapping, alias, pipeline, and node. On every change, the master serializes and publishes the state to all nodes. Updates are processed serially, so any delay in serialization, heap allocation, or node acknowledgment blocks subsequent metadata operations. When metadata churn is high or the state is oversized, the master falls behind, pending tasks accumulate, and if the master misses enough heartbeat checks, remaining master-eligible nodes trigger a new election. Until a stable master converges, writes, allocations, and administrative operations stall.</p>Elasticsearch master_not_discovered_exception: no elected master and stalled writeshttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-no-master-not-discovered/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-no-master-not-discovered/<p>HTTP 503 and <code>master_not_discovered_exception</code> mean bulk indexing, index creation, mapping updates, and shard allocation checks are being rejected. The cluster cannot process writes or administrative work. The data nodes may be healthy, but without an elected master, the cluster cannot update shard routing, publish state changes, or acknowledge document writes. The root cause is usually one of four problems inside the master-eligible cohort.</p> <p>Elasticsearch 7.0 and later use a consensus protocol called Zen2 for master election. Only master-eligible nodes vote. The elected master maintains the cluster state, which describes every index, shard, mapping, alias, and node. That state is serialized and published to all nodes on every change. Without a master, state updates halt and the default <code>cluster.no_master_block</code> (<code>write</code>) rejects write and metadata operations until election completes; read requests continue against the last known cluster state.</p>Elasticsearch merge storms: segment explosion, I/O saturation, and refresh tuninghttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-merge-storms/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-merge-storms/<p>Search latency climbs, indexing slows, and heap usage rises while cluster health stays green. The cause is often a merge storm. Background Lucene segment consolidation has fallen behind, leaving nodes with hundreds or thousands of small segments. Each extra segment adds search overhead, consumes file descriptors, and increases memory pressure. This guide covers how merge storms develop, how to confirm the diagnosis, and how to fix them without making things worse.</p>Elasticsearch Monitoringhttps://www.netdata.cloud/monitoring-101/elasticsearch-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/elasticsearch-monitoring/<h2 id="elasticsearch-monitoring">Elasticsearch Monitoring</h2> <h3 id="what-is-elasticsearch">What Is Elasticsearch?</h3> <p><a href="https://www.elastic.co/elasticsearch/">Elasticsearch</a> is a powerful search and analytics engine designed to quickly query large volumes of data, supporting use cases such as log and event data analytics, full-text searches, and more.</p> <h3 id="monitoring-elasticsearch-with-netdata">Monitoring Elasticsearch With Netdata</h3> <p>To effectively monitor Elasticsearch, leveraging a comprehensive and dynamic monitoring tool is essential. Netdata offers a robust <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/elasticsearch/?utm_source=website&amp;utm_content=monitoring101">Elasticsearch monitoring tool</a>, providing real-time insights into Elasticsearch&rsquo;s performance and health. Netdata&rsquo;s agent continuously collects key metrics, presenting them in interactive dashboards, which helps diagnose issues efficiently.</p>Elasticsearch monitoring checklist: the signals every production cluster needshttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-monitoring-checklist/<p>Elasticsearch failures cascade. A long GC pause on one node causes it to miss fault detection checks; the master removes it. Shards relocate to survivors, increasing heap pressure and thread pool load. If disk is near the high watermark, relocation I/O pushes other nodes toward flood stage, which sets indices to read-only and blocks writes. By the time <code>GET /_cluster/health</code> returns red, the leading indicators fired minutes ago.</p> <p>Cluster health is a lagging indicator. It tells you damage is done, not that it is coming. This checklist organizes signals into four levels. Use it to audit coverage or build instrumentation. Start with survival, but build dashboards that show all four levels so correlations are obvious.</p>Elasticsearch node left the cluster: fault detection, reallocation, and recoveryhttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-node-left-cluster/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-node-left-cluster/<p>Your cluster health turned yellow and <code>number_of_nodes</code> dropped by one. The master logs the node removal (<code>removed ... from the cluster, reason: ...</code>), shards are unassigned, and the remaining nodes absorb extra load. In the next minute, the allocator decides whether to move data. Misread the cause and a transient restart becomes an expensive reallocation storm, or a genuine hardware failure goes unaddressed while replicas rebalance.</p> <p>This guide covers how Elasticsearch decides a node is gone, what happens to its shards, and how to recover without deepening the incident.</p>Elasticsearch node OOM-killed: heap ceiling, page cache, and container limitshttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-out-of-memory-oom-killed/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-out-of-memory-oom-killed/<p>An Elasticsearch node leaves the cluster, restarts seconds later via systemd or a supervisor, and is killed again. Kernel logs show the OOM-killer terminated the Java process. <code>heap.percent</code> often looks reasonable right up until the kill.</p> <p>The JVM heap is only one component of resident set size. Off-heap allocations, memory-mapped Lucene segments, and co-located processes all compete for the same memory budget. In containers, the cgroup limit is the hard boundary, not the host&rsquo;s physical RAM.</p>Elasticsearch this action would add too many shards: max_shards_per_node limithttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-max-shards-per-node-exceeded/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-max-shards-per-node-exceeded/<p>Creating an index or rolling over a data stream returns HTTP 400 <code>validation_exception</code>: &ldquo;this action would add [N] shards, but this cluster currently has [X]/[Y] maximum normal shards open&rdquo;. The cluster has hit <code>cluster.max_shards_per_node</code>, which defaults to 1000 open shards per non-frozen data node. Raising the limit via <code>_cluster/settings</code> unblocks writes but postpones the outage. The durable fix is consolidation.</p> <h2 id="what-this-means">What this means</h2> <p>Every shard is a Lucene index. Each consumes file descriptors, heap for segment metadata, and cluster state entries that the master publishes to every node on every change. <code>cluster.max_shards_per_node</code> guards against over-sharding, where excessive shard counts slow cluster state updates and pressure master and data node heap. When the limit is reached, the allocator refuses new shards. Existing indices remain searchable, but index creation, rollovers, and some reallocations are blocked.</p>Elasticsearch unassigned shards: reading allocation explain and fixing each reasonhttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-unassigned-shards/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-unassigned-shards/<p>Yellow or red cluster health with <code>unassigned_shards &gt; 0</code> means the allocator cannot place one or more shard copies on any node. Missing primaries block queries and risk data loss; missing replicas only cost redundancy. Do not guess from the cluster color. The allocator already knows why it rejected every node. Ask it.</p> <h2 id="what-this-means">What this means</h2> <p>Unassigned primaries make their data unreachable. Affected indices return partial results or fail. Unassigned replicas remove redundancy; a second failure on those primaries drops the data. The master allocator evaluates every node through a chain of deciders: disk watermarks, allocation filters, awareness attributes, the same-shard rule, and retry limits. When every node is rejected, the shard stays <code>UNASSIGNED</code> until the blocking condition clears or you intervene.</p>Elgato Key Light Monitoringhttps://www.netdata.cloud/monitoring-101/elgato_keylight-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/elgato_keylight-monitoring/<h2 id="elgato-key-light-monitoring">Elgato Key Light Monitoring</h2> <h3 id="what-is-elgato-key-light">What Is Elgato Key Light?</h3> <p>Elgato Key Light devices are high-quality lighting solutions that offer advanced controls for content creators, videographers, and professionals. These devices ensure optimal lighting conditions and are integral to achieving the perfect visual setup with ease. By intelligently managing your lighting environment, Elgato Key Light ensures consistent quality outputs in your video productions or live streams.</p> <h3 id="monitoring-elgato-key-light-with-netdata">Monitoring Elgato Key Light With Netdata</h3> <p>To monitor Elgato Key Light devices, Netdata utilizes an OpenMetrics (Prometheus) exporter. This allows users to gather valuable metrics by periodically sending HTTP requests to the <a href="https://github.com/mdlayher/keylight_exporter">Elgato Key Light exporter</a>. Netdata excels in ingesting data from any Prometheus exporter, providing automated dashboards, alerts, and more, without requiring a Prometheus server or Grafana. This seamless integration enables you to keep track of lighting metrics in real-time, enhancing control and management of your environment.</p>Energi Core Wallet Monitoringhttps://www.netdata.cloud/monitoring-101/energid-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/energid-monitoring/<h2 id="what-is-energi-core-wallet">What is Energi Core Wallet?</h2> <p>Energi is a cryptocurrency that is built on the Ethereum blockchain. It is designed to be a self-funding and self-governing cryptocurrency that uses a hybrid Proof-of-Stake (PoS) and Proof-of-Work (PoW) consensus model to improve scalability and security. The Energi Core Wallet is the official wallet software for Energi. It is a software application that allows users to securely store, send and receive Energi coins. The wallet also includes advanced features such as staking, Masternode setup, and coin control.</p>Envoy Monitoringhttps://www.netdata.cloud/monitoring-101/envoy-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/envoy-monitoring/<h2 id="envoy-monitoring">Envoy Monitoring</h2> <h3 id="what-is-envoy">What Is Envoy?</h3> <p>Envoy is an open-source edge and service proxy, designed for cloud-native applications and microservices architectures. It plays a pivotal role in managing ingress and egress traffic between microservices, thus ensuring seamless communications within distributed systems. As a Layer 7 proxy, it provides advanced load balancing, traffic management, and observability features, crucial for high-availability applications.</p> <h3 id="monitoring-envoy-with-netdata">Monitoring Envoy With Netdata</h3> <p>When it comes to monitoring Envoy proxies, the Netdata monitoring tool provides comprehensive insights into various metrics that are key to maintaining optimal performance. Netdata&rsquo;s real-time monitoring capabilities allow you to track the health of your Envoy instances, detect anomalies, and troubleshoot issues promptly. With its ease of configuration and powerful visualization features, Netdata is an ideal solution for monitoring Envoy.</p>EOS Monitoringhttps://www.netdata.cloud/monitoring-101/eos_web-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/eos_web-monitoring/<h2 id="eos-monitoring">EOS Monitoring</h2> <h3 id="what-is-eos">What Is EOS?</h3> <p>EOS is a high-performance, scalable storage service developed by CERN. It is primarily used for managing massive volumes of scientific data, providing a reliable and efficient storage solution that ensures data integrity and accessibility.</p> <h3 id="monitoring-eos-with-netdata">Monitoring EOS With Netdata</h3> <p>To ensure optimal performance and reliability of EOS, monitoring it with Netdata can provide real-time insights into system metrics and help troubleshoot issues proactively. Netdata uses an openmetrics (Prometheus) exporter to collect EOS metrics efficiently. With Netdata, you can ingest data from any Prometheus exporter, offering you automated dashboards and alerts without the need for a Prometheus server or Grafana. This makes Netdata an ideal EOS monitoring tool that simplifies the monitoring process while delivering comprehensive metrics insights.</p>etcd Monitoringhttps://www.netdata.cloud/monitoring-101/etcd-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/etcd-monitoring/<h2 id="etcd-monitoring">etcd Monitoring</h2> <h3 id="what-is-etcd">What Is etcd?</h3> <p>etcd, a distributed key-value store, is a critical component for service discovery and storing all of a cluster&rsquo;s data reliably. It ensures that the systems in production environments are available and consistent. etcd is often implemented in environments requiring fault tolerance, distributed networking, or consensus building. <a href="https://etcd.io/">Learn more about etcd.</a></p> <h3 id="monitoring-etcd-with-netdata">Monitoring etcd With Netdata</h3> <p>When it comes to monitoring etcd, Netdata stands out as a powerful tool. Netdata leverages an OpenMetrics (Prometheus) exporter to monitor etcd, facilitating effortless integration. This capability permits Netdata to ingest metrics from any Prometheus exporter, delivering dynamic dashboards, alerts, and comprehensive insights that require neither a dedicated Prometheus server nor Grafana setup.</p>Exim Monitoringhttps://www.netdata.cloud/monitoring-101/exim-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/exim-monitoring/<h2 id="exim-monitoring">Exim Monitoring</h2> <h3 id="what-is-exim">What Is Exim?</h3> <p>Exim is a mail transfer agent (MTA) used on Unix-like operating systems. It is highly configurable and can handle email routing, spam control, and address verification. For more details, you can visit the <a href="https://www.exim.org/">Exim website</a>.</p> <h3 id="monitoring-exim-with-netdata">Monitoring Exim With Netdata</h3> <p>Monitoring Exim&rsquo;s performance is crucial to ensure the optimal operation of the mail server. With Netdata, you can monitor Exim effortlessly using the go.d.plugin, which tracks the Exim mail queue. This integration provides real-time insights, helping you troubleshoot and maintain reliable email service. Learn more in the <a href="https://www.netdata.cloud/integrations/data-collection/applications/exim/">Exim collector documentation</a>.</p>Fail2ban Monitoringhttps://www.netdata.cloud/monitoring-101/fail2ban-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/fail2ban-monitoring/<h2 id="fail2ban-monitoring">Fail2ban Monitoring</h2> <h3 id="what-is-fail2ban">What Is Fail2ban?</h3> <p>Fail2ban is an open-source intrusion prevention software framework that protects servers from brute-force attacks. It monitors log files and bans IPs that exhibit malicious behavior, such as too many failed login attempts, by modifying firewall rules.</p> <h3 id="monitoring-fail2ban-with-netdata">Monitoring Fail2ban With Netdata</h3> <p>Netdata is a powerful monitoring solution that offers real-time insights into the performance and security of your systems. With Netdata, you can monitor Fail2ban, ensuring your servers remain secured from unwanted access. <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">Check out the Live Demo</a> to see Netdata&rsquo;s capabilities in action.</p>Fair Usage Policyhttps://www.netdata.cloud/fair-usage-policy/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/fair-usage-policy/Fastd Monitoringhttps://www.netdata.cloud/monitoring-101/fastd-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/fastd-monitoring/<h2 id="fastd-monitoring">Fastd Monitoring</h2> <h3 id="what-is-fastd">What Is Fastd?</h3> <p>Fastd, or Fast and Secure Tunneling Daemon, is a VPN solution renowned for its simplicity and flexibility. It&rsquo;s widely used in various network environments, particularly in community wireless networks. Fastd enables encrypted internet connections and is known for its efficient resource usage and adaptability across different platforms.</p> <h3 id="monitoring-fastd-with-netdata">Monitoring Fastd With Netdata</h3> <p>To monitor Fastd, Netdata employs an <a href="https://github.com/freifunk-darmstadt/fastd-exporter">openmetrics (Prometheus) exporter</a>. With Netdata, you can ingest data from any Prometheus exporter, offering automated dashboards, real-time alerts, and more, without the need for a Prometheus server or Grafana. This seamless integration makes it a powerful Fastd monitoring tool, providing comprehensive insights into your VPN&rsquo;s performance and health.</p>Files and Directories Monitoringhttps://www.netdata.cloud/monitoring-101/filecheck-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/filecheck-monitoring/<h2 id="files-and-directories-monitoring">Files and Directories Monitoring</h2> <h3 id="what-is-files-and-directories-monitoring">What Is Files and Directories Monitoring?</h3> <p>Files and directories are integral components of any computing system. Monitoring these elements involves keeping track of their existence, modification times, sizes, and other changes. Effective monitoring ensures data integrity, improves security, and supports efficient system maintenance.</p> <h3 id="monitoring-files-and-directories-with-netdata">Monitoring Files and Directories With Netdata</h3> <p>Netdata provides an intuitive and powerful files monitoring tool leveraging its <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/filecheck/?utm_source=website&amp;utm_content=monitoring101">Filecheck module</a>. This tool simplifies the process of gathering key metrics in real time. With Netdata, you can visualize data from multiple files and directories across different servers, offering a comprehensive view of your infrastructure.</p>Fix Elasticsearch CircuitBreakingException Errorshttps://www.netdata.cloud/guides/elasticsearch/elasticsearch-circuitbreakingexception-parent-data-too-large/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/elasticsearch/elasticsearch-circuitbreakingexception-parent-data-too-large/<p>When a search or indexing request returns HTTP 429 with <code>CircuitBreakingException: [parent] Data too large, data for [&lt;http_request&gt;] would be [X], which is larger than the limit of [Y]</code>, the parent circuit breaker has rejected the operation. This is Elasticsearch protecting the JVM from an out-of-memory kill, not a client-side rate limit.</p> <p>Since version 7.0, the parent breaker tracks real memory usage by default. It can trip even when individual child breakers are within limits. The node is under genuine heap pressure. Determine quickly whether the cause is a single abusive query or structural memory exhaustion.</p>Fluentd Monitoringhttps://www.netdata.cloud/monitoring-101/fluentd-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/fluentd-monitoring/<h2 id="fluentd-monitoring">Fluentd Monitoring</h2> <h3 id="what-is-fluentd">What Is Fluentd?</h3> <p><a href="https://www.fluentd.org/">Fluentd</a> is a powerful open-source data collector that allows you to unify the collection and consumption of data streams. It helps streamline log data management and enables real-time data processing.</p> <h3 id="monitoring-fluentd-with-netdata">Monitoring Fluentd With Netdata</h3> <p>Using Netdata as your Fluentd monitoring tool provides an efficient, real-time overview of the performance and health of your Fluentd instances. Netdata&rsquo;s lightweight but comprehensive monitoring capabilities make it a preferred choice for DevOps and IT professionals.</p>FreeBSD Monitoringhttps://www.netdata.cloud/monitoring-101/freebsd-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/freebsd-monitoring/<h2 id="why-freebsd">Why FreeBSD?</h2> <p><a href="https://www.freebsd.org/">FreeBSD</a> is a free and open source Unix-like operating system descended from the Berkeley Software Distribution (BSD). FreeBSD is the most widely used open source BSD distribution. It is used by companies such as Netflix, Baidu, the United States Department of Defense, and the European Organization for Nuclear Research (CERN).</p> <p>FreeBSD is a high-quality, stable, and secure operating system used in a wide variety of applications. FreeBSD is developed by a large and passionate community of volunteers and is an excellent choice if you are looking for a high-quality, stable, and secure operating system.</p>FreeBSD NFS Monitoringhttps://www.netdata.cloud/monitoring-101/freebsd_nfs-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/freebsd_nfs-monitoring/<h2 id="freebsd-nfs-monitoring">FreeBSD NFS Monitoring</h2> <h3 id="what-is-freebsd-nfs">What Is FreeBSD NFS?</h3> <p>FreeBSD Network File System (NFS) is a protocol that allows file and directory sharing across different systems over a network. Designed for efficient, streamlined connections, FreeBSD NFS is a reliable choice for environments requiring seamless file sharing capabilities.</p> <h3 id="monitoring-freebsd-nfs-with-netdata">Monitoring FreeBSD NFS With Netdata</h3> <p>Monitoring FreeBSD NFS efficiently is crucial to ensure optimal performance and reliability across networked systems. Netdata offers an effective FreeBSD NFS monitoring tool that leverages an OpenMetrics (Prometheus) exporter. Netdata can ingest data from any Prometheus exporter, meaning users can enjoy automated dashboards, alerts, and more without the need for running a full Prometheus server or Grafana setup. Simply connect to the <a href="https://github.com/Axcient/freebsd-nfs-exporter">FreeBSD NFS Exporter</a>, and Netdata takes care of the rest, from data collection to visualization and alerting.</p>FreeBSD RCTL-RACCT Monitoringhttps://www.netdata.cloud/monitoring-101/freebsd_rctl-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/freebsd_rctl-monitoring/<h2 id="freebsd-rctl-racct-monitoring">FreeBSD RCTL-RACCT Monitoring</h2> <h3 id="what-is-freebsd-rctl-racct">What Is FreeBSD RCTL-RACCT?</h3> <p>FreeBSD RCTL-RACCT provides an intricate framework for resource consumption accounting and control on machines running the FreeBSD operating system. It enables precise monitoring and limiting of resource usage, which is vital for maintaining optimal system performance. Key tasks include controlling CPU, memory, and other resource utilizations across different processes and users.</p> <h3 id="monitoring-freebsd-rctl-racct-with-netdata">Monitoring FreeBSD RCTL-RACCT With Netdata</h3> <p>To monitor FreeBSD RCTL-RACCT, Netdata employs an openmetrics (Prometheus) exporter. Users can rely on the <a href="https://github.com/yo000/rctl_exporter">FreeBSD RCTL Exporter</a> to gather crucial metrics seamlessly. Netdata excels in ingesting data from any Prometheus exporter, generating automated dashboards, real-time alerts, and more without necessitating a separate Prometheus server or Grafana setup. This streamlined approach leverages robust open-source technology to ensure comprehensive observability of your FreeBSD resources.</p>FreeRADIUS Monitoringhttps://www.netdata.cloud/monitoring-101/freeradius-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/freeradius-monitoring/<h2 id="freeradius-monitoring">FreeRADIUS Monitoring</h2> <h3 id="what-is-freeradius">What Is FreeRADIUS?</h3> <p><a href="https://freeradius.org/">FreeRADIUS</a> is an open-source implementation of the RADIUS protocol aimed at providing centralized Authentication, Authorization, and Accounting (AAA) services for networked applications. Its broad adoption and flexible configuration options make it a preferred choice for ISPs and enterprises looking to manage network access efficiently.</p> <h3 id="monitoring-freeradius-with-netdata">Monitoring FreeRADIUS With Netdata</h3> <p>Monitoring FreeRADIUS is crucial for maintaining the reliability and performance of your network services. With Netdata&rsquo;s FreeRADIUS monitoring tool, you can achieve real-time observability, receive timely alerts, and access detailed visualizations of your FreeRADIUS servers&rsquo; performance. Netdata&rsquo;s collector gathers comprehensive metrics, allowing you to keep a keen eye on the health of your RADIUS server in a single dashboard.</p>Freifunk Network Monitoringhttps://www.netdata.cloud/monitoring-101/freifunk-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/freifunk-monitoring/<h2 id="freifunk-network-monitoring">Freifunk Network Monitoring</h2> <h3 id="what-is-freifunk">What Is Freifunk?</h3> <p>Freifunk is a grassroots initiative to create free and open wireless community networks. It enables various communities to contribute and connect using decentralized technology. The Freifunk network operates on the principle of crowd-sourced internet, where each node in the network can communicate with others, facilitating a global mesh of connections.</p> <h3 id="monitoring-freifunk-networks-with-netdata">Monitoring Freifunk Networks With Netdata</h3> <p>Monitoring the Freifunk network is crucial for maintaining seamless connectivity and optimizing network performance. With Netdata, this task becomes efficient and manageable. By leveraging an openmetrics (Prometheus) exporter such as the <a href="https://github.com/xperimental/freifunk-exporter">Freifunk Exporter</a>, Netdata can ingest valuable data to provide real-time insights. Notably, Netdata does not require a Prometheus server or Grafana to operate. The platform offers automated dashboards and alerts, significantly easing the monitoring process. Learn more about how <a href="https://learn.netdata.cloud/docs/collecting-metrics/generic-collecting-metrics/prometheus-endpoint/?utm_source=website&amp;utm_content=monitoring101">Netdata can ingest data from any Prometheus exporter</a>.</p>FRRouting Monitoringhttps://www.netdata.cloud/monitoring-101/frrouting-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/frrouting-monitoring/<h2 id="frrouting-monitoring">FRRouting Monitoring</h2> <h3 id="what-is-frrouting">What Is FRRouting?</h3> <p>FRRouting (FRR) is a robust, high-performance suite for software-based routing on Linux and Unix systems. It offers a comprehensive set of tools aimed at providing scalability and flexibility, allowing networks to handle both small and large network infrastructures effectively. With FRR, network administrators can ensure optimal routing protocols are in place for efficient network traffic management.</p> <h3 id="monitoring-frrouting-with-netdata">Monitoring FRRouting With Netdata</h3> <p>Monitoring FRRouting with Netdata is simplified by utilizing the openmetrics (Prometheus) exporter. Netdata has streamlined the process, allowing users to easily ingest data from any Prometheus exporter. This functionality ensures automated dashboards, alerts, and insights without necessitating a standalone Prometheus server or Grafana. You can <a href="https://github.com/tynany/frr_exporter">get the community exporter here</a>.</p>GCP GCE Monitoringhttps://www.netdata.cloud/monitoring-101/gcp_gce-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/gcp_gce-monitoring/<h2 id="gcp-gce-monitoring">GCP GCE Monitoring</h2> <h3 id="what-is-gcp-gce">What Is GCP GCE?</h3> <p>Google Cloud Platform&rsquo;s Compute Engine (GCE) is a robust cloud service that provides scalable virtual machines on demand. GCE is designed to be flexible, offering many choices in terms of operating systems, resource configurations, and networking, making it an ideal choice for developers and enterprises looking to leverage Google&rsquo;s infrastructure for building, testing, and deploying applications.</p> <h3 id="monitoring-gcp-gce-with-netdata">Monitoring GCP GCE With Netdata</h3> <p>To effectively monitor GCP GCE, Netdata leverages a Prometheus-based approach through an openmetrics exporter specifically designed for Google Cloud. The <a href="https://github.com/O1ahmad/gcp-gce-exporter">GCP GCE Exporter</a> collects rich and detailed metrics, enabling seamless cloud resource management and enhanced performance monitoring. Netdata can ingest data from any Prometheus exporter, providing automated dashboards and alerts without the need for a standalone Prometheus server or Grafana. This capability ensures that monitoring your cloud infrastructure is as efficient and real-time as possible.</p>Gearman Monitoringhttps://www.netdata.cloud/monitoring-101/gearman-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/gearman-monitoring/<h2 id="gearman-monitoring">Gearman Monitoring</h2> <h3 id="what-is-gearman">What is Gearman?</h3> <p><a href="https://gearman.org/">Gearman</a> is a distributed job processing system that allows applications to farm out work to other machines or processes that are better suited to do it. It consists of clients, workers, and a Gearman server to queue tasks. This decouples the workload from the tasks, helping in distributing various tasks in a wide set of machines or processes.</p> <h3 id="monitoring-gearman-with-netdata">Monitoring Gearman With Netdata</h3> <p>Monitor Gearman effectively using the Netdata monitoring tool, designed to keep an eye on your Gearman instances in real-time. Netdata provides significant insight into jobs&rsquo; activity, priority, and available workers through its advanced monitoring solutions. This helps in maintaining an optimal work balance and swiftly addressing potential issues.</p>Generic storage enclosure tool Monitoringhttps://www.netdata.cloud/monitoring-101/enclosure-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/enclosure-monitoring/<h2 id="generic-storage-enclosure-tool-monitoring">Generic storage enclosure tool Monitoring</h2> <h3 id="what-is-generic-storage-enclosure-tool">What Is Generic storage enclosure tool?</h3> <p>The Generic storage enclosure tool, accessible from its <a href="https://github.com/Gandi/jbod-rs">GitHub repository</a>, is a pivotal utility for managing storage enclosure metrics. It aids in effective management and performance evaluation of storage devices. Specifically created for IT infrastructures heavily relying on storage, it ensures your IT assets are running smoothly and efficiently by tracking critical metrics.</p> <h3 id="monitoring-generic-storage-enclosure-tool-with-netdata">Monitoring Generic storage enclosure tool With Netdata</h3> <p>Monitoring your storage environment is crucial and Netdata offers a comprehensive solution for it. Using Netdata, you can monitor the Generic storage enclosure tool without needing complex setups like a full Prometheus server or Grafana. Netdata uses an openmetrics (Prometheus) exporter to pull metrics, automatically generating dashboards and alerts for a seamless monitoring experience. Netdata can ingest data effortlessly from any Prometheus exporter, offering profound insights and easy setup.</p>Get support!https://www.netdata.cloud/support/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/support/GitHub API Rate Limit Monitoringhttps://www.netdata.cloud/monitoring-101/github_ratelimit-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/github_ratelimit-monitoring/<h2 id="github-api-rate-limit-monitoring">GitHub API Rate Limit Monitoring</h2> <h3 id="what-is-github-api-rate-limit">What Is GitHub API Rate Limit?</h3> <p>GitHub API rate limits are set thresholds that guide the number of requests a user can make within a certain time frame using the GitHub API. Monitoring these limits ensures that your applications and services make efficient use of API calls without exceeding the permitted usage, preventing disruptions and maintaining performance reliability.</p> <h3 id="monitoring-github-api-rate-limit-with-netdata">Monitoring GitHub API Rate Limit With Netdata</h3> <p>Netdata provides a seamless approach to monitor GitHub API rate limits using an openmetrics (Prometheus) exporter. The <a href="https://github.com/lunarway/github-ratelimit-exporter">GitHub API rate limit Exporter</a> efficiently gathers metrics on rate limits, allowing you to gain insights into your API usage. Netdata can ingest data from any Prometheus exporter, delivering automated dashboards and alerts without the need for a Prometheus server or Grafana setup. This unique capability sets Netdata apart, simplifying the process of tracking API consumption in real-time and enhancing your operational insights.</p>GitHub Repository Monitoringhttps://www.netdata.cloud/monitoring-101/github_repo-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/github_repo-monitoring/<h2 id="github-repository-monitoring">GitHub Repository Monitoring</h2> <h3 id="what-is-github-repository-monitoring">What Is GitHub Repository Monitoring?</h3> <p>GitHub repository monitoring involves tracking a plethora of metrics essential for maintaining robust and high-performing code repositories. As various developers contribute code, issues may arise that affect performance and reliability. Monitoring these aspects is crucial for ensuring smooth DevOps processes. A well-rounded approach to monitoring examines pull requests, commits, issues, and broader analytics related to repository activity.</p> <h3 id="monitoring-github-repository-with-netdata">Monitoring GitHub Repository With Netdata</h3> <p>Netdata provides a seamless path to monitor GitHub repositories. To monitor GitHub repositories, Netdata uses an openmetrics (Prometheus) exporter, the <a href="https://github.com/githubexporter/github-exporter">GitHub Exporter</a>. Netdata is designed to ingest data from any Prometheus exporter, allowing you to benefit from automated dashboards, alerts, and real-time insights without requiring standalone Prometheus servers or Grafana dashboards. This streamlined approach facilitates effective monitoring while saving overhead on setting up intricate monitoring systems.</p>GitLab Runner Monitoringhttps://www.netdata.cloud/monitoring-101/gitlab_runner-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/gitlab_runner-monitoring/<h2 id="gitlab-runner-monitoring">GitLab Runner Monitoring</h2> <h3 id="what-is-gitlab-runner">What Is GitLab Runner?</h3> <p>GitLab Runner is an open-source project that is used to run your jobs and send the results back to GitLab. It is a key component in GitLab&rsquo;s CI/CD pipeline, responsible for executing code and providing continuous feedback. GitLab Runner supports multiple platforms, cloud-native applications, and many advanced configuration options, making it versatile and essential for developers looking to automate their CI/CD processes.</p> <h3 id="monitoring-gitlab-runner-with-netdata">Monitoring GitLab Runner With Netdata</h3> <p>Netdata is a powerful tool to monitor GitLab Runner. Using a Prometheus exporter, Netdata collects detailed metrics from GitLab Runner without the need for a Prometheus server or Grafana installation. This setup enables users to access automated dashboards and real-time alerts which significantly ease the process of monitoring your CI/CD environment. Moreover, Netdata is capable of ingesting data from any Prometheus exporter, providing flexibility and scalability for growing operations.</p>Go-ethereum Monitoringhttps://www.netdata.cloud/monitoring-101/geth-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/geth-monitoring/<h2 id="go-ethereum-monitoring">Go-ethereum Monitoring</h2> <h3 id="what-is-go-ethereum">What Is Go-ethereum?</h3> <p>Go-ethereum, often abbreviated as Geth, is one of the most popular implementations of the Ethereum protocol. Written in Go, it enables developers and enthusiasts to run a full Ethereum node, providing functionalities such as mining, creating contracts, and deploying DApps on the Ethereum blockchain. Go-ethereum is a fundamental tool within the blockchain ecosystem and is highly valued for its robustness and performance.</p> <h3 id="monitoring-go-ethereum-with-netdata">Monitoring Go-ethereum With Netdata</h3> <p>For anyone invested in the blockchain landscape, ensuring optimal performance and reliability of Go-ethereum nodes is crucial. With Netdata, a highly efficient monitoring solution, you can keep an eye on the performance and health of your Go-ethereum instances in real-time. As a powerful Go-ethereum monitoring tool, Netdata offers deep insights into blockchain operations, facilitating rapid troubleshooting and ensuring seamless operations.</p>Gobetween Monitoringhttps://www.netdata.cloud/monitoring-101/gobetween-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/gobetween-monitoring/<h2 id="gobetween-monitoring">Gobetween Monitoring</h2> <h3 id="what-is-gobetween">What Is Gobetween?</h3> <p>Gobetween is a high-performance, protocol-agnostic load balancer designed for distributed network traffic management. As an open-source solution, it allows for the efficient routing of requests between multiple servers, offering improved performance, scalability, and reliability for modern web applications.</p> <h3 id="monitoring-gobetween-with-netdata">Monitoring Gobetween With Netdata</h3> <p>Monitor Gobetween effectively using Netdata&rsquo;s robust monitoring capabilities. Netdata enhances the $name monitoring tool by utilizing an openmetrics (prometheus) exporter, which allows for seamless data collection without the need for a Prometheus server or Grafana setup. With Netdata, users can ingest data from any Prometheus exporter and gain access to automated dashboards, real-time alerts, and a wealth of metrics that facilitate optimized network traffic management and performance analysis.</p>Google Cloud Platform Monitoringhttps://www.netdata.cloud/monitoring-101/gcp-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/gcp-monitoring/<h2 id="google-cloud-platform-monitoring">Google Cloud Platform Monitoring</h2> <h3 id="what-is-google-cloud-platform">What Is Google Cloud Platform?</h3> <p>Google Cloud Platform (GCP) is a suite of cloud computing services provided by Google. It offers a wide range of services including computing power, storage, and machine learning capabilities, all of which are scalable to meet business needs. Whether you are deploying applications in Kubernetes, analyzing big data, or developing AI/ML models, GCP provides the infrastructure and tools to do so efficiently.</p>Google Colab Monitoringhttps://www.netdata.cloud/monitoring-101/colab-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/colab-monitoring/<p>Google Colab offers an exceptional platform for running Notebooks, developing machine learning models, and conducting various data science and analytics tasks. To optimize your experience, it is crucial to understand the performance of your Colab instance.</p> <h2 id="why-monitor-colab">Why monitor Colab?</h2> <p>Monitoring your Google Colab instance provides vital insights into its performance, enabling you to optimize your work and make the most of available resources. The benefits of monitoring your Colab instance include:</p>Google Pagespeed Monitoringhttps://www.netdata.cloud/monitoring-101/google_pagespeed-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/google_pagespeed-monitoring/<h2 id="google-pagespeed-monitoring">Google Pagespeed Monitoring</h2> <h3 id="what-is-google-pagespeed">What Is Google Pagespeed?</h3> <p>Google Pagespeed is a widely-utilized performance tool that offers valuable insights into the speed and optimization of web pages. It&rsquo;s an essential service in the realm of cloud computing, providing metrics that help ensure efficient website performance and user experience.</p> <h3 id="monitoring-google-pagespeed-with-netdata">Monitoring Google Pagespeed With Netdata</h3> <p>Monitor Google Pagespeed effectively with Netdata, using the robust capabilities of Netdata&rsquo;s openmetrics (Prometheus) exporter. Netdata allows you to seamlessly ingest data from any Prometheus exporter, including Google Pagespeed, providing automated dashboards, alerts, and more. This toolkit eliminates the need for a Prometheus server or Grafana, streamlining your monitoring setup and enabling real-time insights.</p>Google Stackdriver Monitoringhttps://www.netdata.cloud/monitoring-101/gcp_stackdriver-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/gcp_stackdriver-monitoring/<h2 id="google-stackdriver-monitoring">Google Stackdriver Monitoring</h2> <h3 id="what-is-google-stackdriver">What Is Google Stackdriver?</h3> <p>Google Stackdriver, now part of Google Cloud&rsquo;s operations suite, provides powerful monitoring, logging, and diagnostics services for applications hosted on Google Cloud Platform (GCP) and Amazon Web Services (AWS). With Stackdriver, you can proactively identify and troubleshoot issues across cloud services to ensure optimal performance and reliability.</p> <h3 id="monitoring-google-stackdriver-with-netdata">Monitoring Google Stackdriver With Netdata</h3> <p>To monitor Google Stackdriver, Netdata employs an openmetrics (prometheus) exporter, allowing users to gather diverse metrics without needing a Prometheus server or Grafana. The integration seamlessly ingests data, providing automated dashboards, alerts, and insights for real-time monitoring. You can explore the community-supported <a href="https://github.com/prometheus-community/stackdriver_exporter">Google Stackdriver exporter</a> to start monitoring with accuracy and efficiency.</p>GPSD Monitoringhttps://www.netdata.cloud/monitoring-101/gpsd-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/gpsd-monitoring/<h2 id="gpsd-monitoring">GPSD Monitoring</h2> <h3 id="what-is-gpsd">What Is GPSD?</h3> <p>GPSD (GPS Daemon) is a service daemon that monitors one or more GPS or AIS receivers, which share data with various applications. It manages the communication between GPS devices and client applications, ensuring that all connected applications receive accurate and timely positional and navigational data.</p> <h3 id="monitoring-gpsd-with-netdata">Monitoring GPSD With Netdata</h3> <p>Netdata offers robust solutions for monitoring GPSD by leveraging the <a href="https://github.com/natesales/gpsd-exporter">gpsd-exporter</a>. This tool uses openmetrics (Prometheus) to collect data seamlessly. With Netdata, you can ingest this data without the need for a dedicated Prometheus server or custom Grafana dashboards. Netdata automates dashboards, alerts, and allows you to keep a finger on the pulse of your GPS data systems effortlessly.</p>Grafana Monitoringhttps://www.netdata.cloud/monitoring-101/grafana-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/grafana-monitoring/<h2 id="grafana-monitoring">Grafana Monitoring</h2> <h3 id="what-is-grafana">What Is Grafana?</h3> <p>Grafana is a powerful open-source platform for monitoring and observability that allows you to query, visualize, and alert on your metrics. By enabling diverse data visualization options, Grafana helps DevOps, SREs, and IT admins understand complex datasets in real-time, which makes it an invaluable tool in modern IT environments.</p> <h3 id="monitoring-grafana-with-netdata">Monitoring Grafana With Netdata</h3> <p>Monitoring Grafana effectively is crucial for leveraging its full capabilities in visualizing data. Netdata offers a comprehensive solution to monitor Grafana using its OpenMetrics (Prometheus) exporter. Unlike traditional setups where a Prometheus server and Grafana dashboard need to be maintained separately, Netdata simplifies the process by allowing direct ingestion of Prometheus metrics, offering automated dashboards, alerts, and more without the need for additional server infrastructure.</p>Graylog Server Monitoringhttps://www.netdata.cloud/monitoring-101/graylog-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/graylog-monitoring/<h2 id="graylog-server-monitoring">Graylog Server Monitoring</h2> <h3 id="what-is-graylog-server">What Is Graylog Server?</h3> <p>Graylog Server is a powerful open-source log management platform designed to aggregate and analyze log data effectively. It centralizes log data from across an infrastructure, providing DevOps, SREs, developers, IT admins, and engineers with valuable insights for operational intelligence and security.</p> <h3 id="monitoring-graylog-server-with-netdata">Monitoring Graylog Server With Netdata</h3> <p>To monitor Graylog Server, Netdata uses an openmetrics exporter, commonly known as a Prometheus exporter. Netdata seamlessly integrates with any Prometheus exporter, allowing you to get instantaneous access to automated dashboards and alerts, without the need for a complete Prometheus setup or Grafana. This ease of use makes Netdata an excellent choice for tools for monitoring Graylog Server, ensuring efficient log management and analysis.</p>Hadoop Distributed File System (HDFS) Monitoringhttps://www.netdata.cloud/monitoring-101/hdfs-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/hdfs-monitoring/<h2 id="hadoop-distributed-file-system-hdfs-monitoring">Hadoop Distributed File System (HDFS) Monitoring</h2> <h3 id="what-is-hdfs">What Is HDFS?</h3> <p>The <a href="https://hadoop.apache.org/docs/r1.2.1/hdfs_design.html">Hadoop Distributed File System (HDFS)</a> is the primary data storage system used by Hadoop applications. It&rsquo;s designed to store very large data sets reliably and to stream those data sets at high bandwidth to user applications.</p> <h3 id="monitoring-hdfs-with-netdata">Monitoring HDFS With Netdata</h3> <p>Monitoring HDFS is pivotal for ensuring data reliability and system performance. Netdata&rsquo;s HDFS monitoring tool provides deep insights by efficiently gathering metrics via JMX from HDFS daemons. This ensures that any anomaly within HDFS is quickly detected and addressed.</p>Halon Monitoringhttps://www.netdata.cloud/monitoring-101/halon-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/halon-monitoring/<h2 id="halon-monitoring">Halon Monitoring</h2> <h3 id="what-is-halon">What Is Halon?</h3> <p>Halon is a high-performance email security and delivery platform designed to streamline email management and enhance protection against spam and malicious content. Halon offers a modular environment whereby organizations can tailor configurations to address specific email handling and security needs effectively.</p> <h3 id="monitoring-halon-with-netdata">Monitoring Halon With Netdata</h3> <p>Monitoring Halon is crucial to ensure seamless email operations and security. With Netdata, you can monitor Halon using the powerful openmetrics (Prometheus) exporter. Netdata can ingest data from any Prometheus exporter, enabling automated dashboards, alerts, and more without the need for setting up a separate Prometheus server or Grafana. This integration streamlines the monitoring process and delivers real-time insights on Halon&rsquo;s performance and health.</p>HANA Monitoringhttps://www.netdata.cloud/monitoring-101/hana-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/hana-monitoring/<h2 id="hana-monitoring">HANA Monitoring</h2> <h3 id="what-is-hana">What Is HANA?</h3> <p>SAP HANA is an in-memory, column-oriented, relational database management system designed to handle both high transaction rates and complex query processing. As a powerful database server, it&rsquo;s essential to monitor HANA to ensure efficient data storage and quick query performance.</p> <h3 id="monitoring-hana-with-netdata">Monitoring HANA With Netdata</h3> <p>To monitor HANA, Netdata leverages an openmetrics (Prometheus) exporter. By integrating with <a href="https://github.com/jenningsloy318/hana_exporter">HANA Exporter</a>, Netdata collects and visualizes key metrics from your HANA database. One of the standout benefits of using Netdata is that it can ingest data from any Prometheus exporter, providing automated dashboards, alerts, and insights into your system&rsquo;s performance—without the need for a Prometheus server or Grafana setup.</p>HAProxy 400 And 408 Request Errors: How To Fixhttps://www.netdata.cloud/guides/haproxy/haproxy-400-408-request-errors/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-400-408-request-errors/<p>Your frontend <code>hrsp_4xx</code> counter just doubled, and it is not 404s. The spike is 400s and 408s, which means HAProxy itself is rejecting or timing out requests before they reach a backend. Unlike backend-generated 4xx, these errors say something about the bytes arriving at your frontend: malformed requests, protocol mismatches, oversized headers, or clients that open connections and never finish the request.</p> <p>Split the two codes before doing anything else. A 400 means HAProxy tried to parse the request and failed. A 408 means <code>timeout http-request</code> fired because the client never sent a complete request in time. One is a parsing problem, the other is a timing problem, and they point at very different fixes.</p>HAProxy 502 Bad Gateway: Causes And Fixeshttps://www.netdata.cloud/guides/haproxy/haproxy-502-bad-gateway/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-502-bad-gateway/<p>Clients are getting 502 Bad Gateway from HAProxy. The backend may look healthy, health checks may be green, and yet some fraction of requests comes back with a 502 the application never logged. That is the signature: a 502 from HAProxy is usually generated by HAProxy itself, not passed through from the backend.</p> <p>HAProxy emits a 502 in two situations. First, it could not establish or use a connection to the backend server at all. Second, it connected fine, but the server sent an invalid, truncated, or incomplete response, or closed the connection mid-response. These are different failure modes with different fixes, and the fastest path to resolution is separating them before touching anything.</p>HAProxy 503 Service Unavailable: no server is available to handle this requesthttps://www.netdata.cloud/guides/haproxy/haproxy-503-service-unavailable/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-503-service-unavailable/<p>Clients are getting <code>503 Service Unavailable</code> with the message <code>no server is available to handle this request</code>. HAProxy generated this error. Unlike a 500 from your application or a 502 from a broken backend response, a 503 with this message never touched a backend server. HAProxy looked at its own state, concluded it had nowhere to send the request, and answered on its own.</p> <p>That narrows the diagnostic question to: why did HAProxy believe no server was available? The honest answers are a short list. Every server in the backend is DOWN or in MAINT. The request waited in queue too long and expired. The queue overflowed. The frontend had no matching backend at all. Or connection admission was saturated and the request was rejected before dispatch.</p>HAProxy 504 Gateway Timeout: timeout server and the backend timeout cascadehttps://www.netdata.cloud/guides/haproxy/haproxy-504-gateway-timeout/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-504-gateway-timeout/<p>Your frontend error rate jumps. Clients report &ldquo;504 Gateway Timeout.&rdquo; HAProxy looks alive: the process is running, servers are UP, health checks are green. Yet requests are dying on a timer.</p> <p>This is the backend timeout cascade, and the 504 is its final symptom. The servers are reachable (TCP accepts succeed), but the application behind them has slowed past the <code>timeout server</code> budget. HAProxy holds the client connection, waits, gives up, and generates a 504 itself.</p>HAProxy 5xx delta: telling HAProxy-generated errors from backend errorshttps://www.netdata.cloud/guides/haproxy/haproxy-frontend-backend-5xx-delta/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-frontend-backend-5xx-delta/<p>Your frontend <code>hrsp_5xx</code> counter is climbing and users are seeing errors. The first question that decides the next hour of your incident response: is HAProxy generating these errors, or is it passing through errors your backend servers produced?</p> <p>HAProxy counts 5xx responses in both places. Frontend rows count every 5xx the client saw, including responses HAProxy fabricated itself. Backend and server rows count only 5xx responses that actually came back from a server. The difference between the two answers &ldquo;is the backend failing or is HAProxy failing?&rdquo; without walking every backend one by one.</p>HAProxy backend losing servers: active server count and cascade riskhttps://www.netdata.cloud/guides/haproxy/haproxy-backend-losing-servers-capacity/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-backend-losing-servers-capacity/<p>A backend can lose half its servers and HAProxy will still report the BACKEND aggregate row as UP. As long as one server is available, the rollup status says traffic is being served, and status-based dashboards stay green. Meanwhile the surviving servers are absorbing redistributed load, their session counts are climbing, and you are one health check failure away from a full 503 outage for that backend.</p> <p>This is the leading edge of the backend collapse cascade: initial server failure, traffic redistribution, survivor overload, survivor health check failures, more redistribution, total collapse. The operators who catch it early are watching the active server count and the load on survivors, not the aggregate status.</p>HAProxy backend queue building (qcur): requests waiting for a free server slothttps://www.netdata.cloud/guides/haproxy/haproxy-backend-queue-building-qcur/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-backend-queue-building-qcur/<p>You are looking at HAProxy stats and <code>qcur</code> is nonzero on a backend, or worse, climbing. Clients have not seen errors yet, but latency is drifting up. That instinct that something is wrong is correct: <code>qcur</code> is the earliest signal that backend capacity is exhausted, and it shows up before any error counter moves.</p> <p><code>qcur</code> is the instantaneous count of connections sitting in a queue because every server that could take them is already at its <code>maxconn</code> limit. Those requests are not being served. They are parked, consuming their client&rsquo;s timeout budget, waiting for a slot to free up. If the queue grows faster than slots free up, the outcome is queue timeouts and 503s.</p>HAProxy connection errors (econ): backend connections refused, timed out, or resethttps://www.netdata.cloud/guides/haproxy/haproxy-connection-errors-econ/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-connection-errors-econ/<p>Your HAProxy backend shows a rising <code>econ</code> counter. Clients may not see errors yet, because HAProxy retries failed connections and redispatches to other servers, but the counter means HAProxy is trying to open TCP connections to a backend server and failing. The connection is being refused, timing out, or getting reset.</p> <p><code>econ</code> is one of the highest-signal error counters HAProxy exposes, and one of the most misread. It is cumulative, it only increments on new connection attempts (so connection reuse can mask a real problem for hours), and it lumps three very different failure modes into one number. Telling &ldquo;the server process is dead&rdquo; apart from &ldquo;a firewall is silently dropping SYNs&rdquo; requires correlating <code>econ</code> with <code>ctime</code> and a few other signals.</p>HAProxy DNS resolver failure: stale IPs and silently misrouted traffichttps://www.netdata.cloud/guides/haproxy/haproxy-dns-resolver-failure/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-dns-resolver-failure/<p>Your backend servers report UP. Health checks pass. The stats page is green. And traffic is going to IP addresses that belong to pods deleted an hour ago, or to a node that now runs something else entirely.</p> <p>This is the HAProxy DNS resolver failure mode, and it only bites deployments that resolve backends dynamically: <code>server-template</code> with Consul DNS, Kubernetes headless services, SRV records, or any setup where server addresses come from DNS instead of static config lines. When the resolver times out or a TTL expires without a successful re-resolution, HAProxy keeps routing to the last IPs it knew about. There is no stats CSV counter for this. <code>show resolvers</code> is the only direct view into it, and most teams never look.</p>HAProxy ephemeral port exhaustion: TIME_WAIT and backend connection churnhttps://www.netdata.cloud/guides/haproxy/haproxy-ephemeral-port-exhaustion/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-ephemeral-port-exhaustion/<p>Your backends are healthy. Every server is UP, health checks pass, the application team sees nothing wrong on their side. Yet HAProxy is logging failed backend connections, <code>econ</code> counters are climbing, and clients see intermittent 502s or stalls. On the HAProxy host, tens of thousands of sockets sit in TIME_WAIT.</p> <p>This is ephemeral port exhaustion on the backend-facing side of HAProxy. Every new TCP connection from HAProxy to a backend consumes one local ephemeral port. When the connection closes, that port is held in TIME_WAIT for 60 seconds before it can be reused. If the rate of new backend connections is high enough, the port range empties and <code>connect()</code> starts failing with <code>EADDRNOTAVAIL</code>. HAProxy reports these as connection errors even though nothing is wrong with the backend.</p>HAProxy health check L4TOUT and L4CON: server marked DOWN and unreachablehttps://www.netdata.cloud/guides/haproxy/haproxy-health-check-l4tout-l4con/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-health-check-l4tout-l4con/<p>You look at the HAProxy stats page (or your monitoring) and a server row is red. The <code>check_status</code> field says <code>L4TOUT</code> or <code>L4CON</code>, <code>status</code> says <code>DOWN</code>, and HAProxy has stopped routing traffic to that server. Both codes mean the failure happened before any HTTP, before any application code, at the plain TCP layer.</p> <p><code>L4TOUT</code> means HAProxy opened a socket and the TCP connect did not complete within the check timeout. <code>L4CON</code> means the connect attempt failed immediately with an error, typically &ldquo;Connection refused&rdquo; (TCP RST) or &ldquo;No route to host&rdquo; (ICMP). The server is unreachable at the TCP layer, and after <code>fall</code> consecutive failures (default 3), HAProxy marks it DOWN and redistributes its traffic.</p>HAProxy health check L7STS: server DOWN on the wrong HTTP statushttps://www.netdata.cloud/guides/haproxy/haproxy-health-check-l7sts/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-health-check-l7sts/<p>A backend server flips to DOWN in the stats page, <code>last_chk</code> shows <code>L7STS</code>, and the log line says something like <code>Layer7 wrong status, code: 503, info: &quot;Service Unavailable&quot;</code>. The server process is running. The port is open. You can curl it by hand and get a response. But HAProxy has pulled it out of rotation and traffic is concentrating on the survivors.</p> <p>L7STS means: the TCP connection worked, the HTTP response arrived in time, and the status code was not the one the health check expects. The failure is at the application layer, not the network layer. That narrows the search space considerably, but only if you know what status HAProxy was actually expecting.</p>HAProxy health checks green but the application is broken: when UP does not mean healthyhttps://www.netdata.cloud/guides/haproxy/haproxy-health-check-green-app-broken/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-health-check-green-app-broken/<p>Every server in the backend shows UP. Health checks are passing. And users are getting 500s. This is one of the most common HAProxy postmortem findings: &ldquo;health checks said everything was fine.&rdquo;</p> <p>The failure is conceptual, not a bug. HAProxy&rsquo;s health check engine runs independently of traffic and only proves that the specific probe you configured succeeds. A TCP check proves the port accepts connections. An HTTP check to <code>/health</code> proves that one URL returns the expected status. Neither proves that real requests, which exercise the database, auth, and downstream dependencies, actually work.</p>HAProxy Idle_pct dropping: event-loop CPU saturation and the busy-polling traphttps://www.netdata.cloud/guides/haproxy/haproxy-idle-pct-low/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-idle-pct-low/<p>Your HAProxy latency is climbing, nothing is queuing on the backends, and the one metric that looks wrong is <code>Idle_pct</code> sliding toward zero. Or worse: <code>Idle_pct</code> has been pinned at zero for weeks and you only just noticed because someone finally asked what it meant. Both situations are common, and they have very different explanations.</p> <p><code>Idle_pct</code> is HAProxy&rsquo;s self-reported measure of event-loop headroom: the share of time the loop spends waiting in <code>poll()</code> versus processing events. It measures HAProxy CPU headroom, not system CPU. A host at 50% system CPU with <code>Idle_pct</code> at 80% is fine. A host at 50% system CPU with <code>Idle_pct</code> at 10% means HAProxy itself is saturated. That distinction is the entire point of the metric, and it is also where the traps live.</p>HAProxy kernel accept-queue overflow: silent SYN drops and somaxconnhttps://www.netdata.cloud/guides/haproxy/haproxy-listen-queue-overflow-somaxconn/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-listen-queue-overflow-somaxconn/<p>Clients report connection timeouts. You open the HAProxy stats page and everything looks fine: session rate is normal, no 5xx spike, servers are UP, Idle_pct is healthy. The network team sees nothing. The clients insist the load balancer is dropping them.</p> <p>Both sides are right. The kernel is silently dropping SYN packets in the accept queue before they ever reach HAProxy&rsquo;s event loop. From HAProxy&rsquo;s perspective, those connections never existed. There is no log line, no error counter, no stat field that increments. The only evidence lives in two kernel counters, <code>ListenOverflows</code> and <code>ListenDrops</code>, that almost nobody graphs.</p>HAProxy maxconn reached: new connections queued and rejectedhttps://www.netdata.cloud/guides/haproxy/haproxy-maxconn-reached/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-maxconn-reached/<p>HAProxy is refusing work. Clients see connection timeouts or resets, load tests fail at a suspiciously round concurrency number, and yet the HAProxy process looks healthy: CPU is fine, memory is fine, the process is up, health checks pass. The stats tell the real story: <code>CurrConns</code> is flat at <code>Maxconn</code>, or <code>scur</code> is pinned at <code>slim</code> on a frontend, and it does not move.</p> <p>The global or per-frontend <code>maxconn</code> limit has been reached, so HAProxy stops accepting new connections. Those connections pile up in the kernel&rsquo;s listen backlog, and once the backlog fills, SYNs are dropped silently. From HAProxy&rsquo;s perspective nothing is wrong, because the connections never reached user space. From the client&rsquo;s perspective the service is down.</p>HAProxy Monitoringhttps://www.netdata.cloud/monitoring-101/haproxy-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/haproxy-monitoring/<h2 id="haproxy-monitoring">HAProxy Monitoring</h2> <h3 id="what-is-haproxy">What Is HAProxy?</h3> <p>HAProxy, short for High Availability Proxy, is a popular open-source software widely used for load balancing and proxying for TCP and HTTP-based applications. It is known for its reliability, performance, and feature-rich nature, making it a staple in server infrastructure for distributing workloads efficiently.</p> <h3 id="monitoring-haproxy-with-netdata">Monitoring HAProxy With Netdata</h3> <p>Monitoring HAProxy is crucial for ensuring your application infrastructure performs optimally and remains highly reliable. <a href="https://www.netdata.cloud/">Netdata</a> offers comprehensive and real-time monitoring of HAProxy, delivering rich visualization of health and performance metrics. By leveraging such a tool, you can observe metrics like response times, session rates, and network throughput in a live, interactive interface. You can get started by <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">checking out the Live Demo</a> or <a href="https://app.netdata.cloud/?utm_source=website&amp;utm_content=monitoring101">signing up for a free trial</a>.</p>HAProxy monitoring checklist: the signals every production proxy needshttps://www.netdata.cloud/guides/haproxy/haproxy-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-monitoring-checklist/<p>Most HAProxy outages are visible in its own stats long before users notice. The problem is that the stats socket exposes dozens of fields, and teams usually wire up the five metrics their dashboard template shipped with and stop there. Then a reload storm, a retry storm, or a silent stick-table overflow teaches them what they were missing.</p> <p>This checklist organizes the signals that catch production failures into four maturity levels: survival, operational, mature, and expert. Each level builds on the previous one. You do not need to reach expert on day one, but you should know which level you are at, because that determines which failure modes are invisible to you.</p>HAProxy scur approaching slim: the concurrent-session saturation signalhttps://www.netdata.cloud/guides/haproxy/haproxy-current-sessions-near-maxconn/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-current-sessions-near-maxconn/<p>Your alert says <code>scur</code> is at 85% of <code>slim</code> on a frontend, or <code>CurrConns</code> is closing on <code>Maxconn</code> in <code>show info</code>. HAProxy is still up. Traffic is still flowing. But you are running out of concurrent-session headroom, and what happens next depends entirely on which of the four independent limits you are about to hit.</p> <p>The danger is that the system still appears responsive: HAProxy is alive and healthy, but clients are about to see queuing delays or 503 rejections. The scur/slim ratio is the warning, if you read it correctly.</p>HAProxy SSL certificate expired: total TLS failure and how to catch it firsthttps://www.netdata.cloud/guides/haproxy/haproxy-ssl-certificate-expired/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-ssl-certificate-expired/<p>Every client connecting to the affected frontend gets a TLS handshake failure. Not a percentage of clients, not a slow degradation: all of them, immediately, from the moment the certificate&rsquo;s <code>notAfter</code> timestamp passes. Browsers show <code>NET::ERR_CERT_DATE_INVALID</code>, API clients throw certificate validation errors, and HAProxy itself is perfectly healthy, running, and passing every process-liveness check you have.</p> <p>The mechanism is trivial, the blast radius is total, and HAProxy gives you no built-in metric, counter, or log warning that a certificate is about to expire. If you are reading this during an incident, skip to Quick checks and Fixes. If you are reading it afterward, the Prevention section is the part that matters.</p>HAProxy Too many open files: file descriptor exhaustion and refused connectionshttps://www.netdata.cloud/guides/haproxy/haproxy-too-many-open-files/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/haproxy/haproxy-too-many-open-files/<p>HAProxy is refusing new connections. Clients see connection timeouts or resets, health checks start failing for no application reason, and the logs show <code>Too many open files</code>. The process is alive and CPU looks fine, which makes this confusing the first time you hit it: nothing is overloaded in the usual sense. The proxy has run out of file descriptors.</p> <p>FD exhaustion is a hard cliff. When the process hits its limit, <code>accept()</code> fails immediately with <code>EMFILE</code>. There is no queue, no graceful degradation, no backpressure. New connections are dropped at the syscall boundary. At the same time, HAProxy can no longer open backend sockets, health check sockets, or log sockets, so the failure spreads well beyond new client connections.</p>HDD Temperature Monitoringhttps://www.netdata.cloud/monitoring-101/hddtemp-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/hddtemp-monitoring/<h2 id="hdd-temperature-monitoring">HDD Temperature Monitoring</h2> <h3 id="what-is-hdd-temperature">What Is HDD Temperature?</h3> <p>HDD temperature refers to the heat emitted by your hard disk drive during its operation. Monitoring the HDD temperature can prevent overheating, which could compromise data integrity and hardware stability. Using an efficient HDD temperature monitoring tool is crucial for maintaining your system’s overall health.</p> <h3 id="monitoring-hdd-temperature-with-netdata">Monitoring HDD Temperature With Netdata</h3> <p>Netdata provides a comprehensive HDD temperature monitoring solution. This open-source platform leverages the hddtemp daemon to collect and display real-time temperature data across all your disks, ensuring you stay informed about any potential overheating issues. With <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">Netdata&rsquo;s live demo</a>, you can see Netdata&rsquo;s monitoring capabilities in action.</p>Hitron CODA Cable Modem Monitoringhttps://www.netdata.cloud/monitoring-101/hitron_coda-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/hitron_coda-monitoring/<h2 id="hitron-coda-cable-modem-monitoring">Hitron CODA Cable Modem Monitoring</h2> <h3 id="what-is-hitron-coda-cable-modem">What Is Hitron CODA Cable Modem?</h3> <p>The Hitron CODA Cable Modem is a device that facilitates high-speed internet connectivity, often used in homes and businesses. This modem is designed to enhance internet performance through efficient data management and superior networking capabilities. Monitoring is crucial for maintaining optimal performance and troubleshooting any connectivity issues that may arise.</p> <h3 id="monitoring-hitron-coda-cable-modem-with-netdata">Monitoring Hitron CODA Cable Modem With Netdata</h3> <p>To monitor the Hitron CODA Cable Modem, Netdata utilizes an openmetrics (Prometheus) exporter <a href="https://github.com/hairyhenderson/hitron_coda_exporter">developed by the community</a>. This integration allows Netdata to ingest data from any Prometheus exporter, offering users automated dashboards, alerts, and more—without the need for setting up a complex Prometheus server or Grafana. The seamless integration with Netdata means you get actionable insights with minimal setup.</p>Homebridge Monitoringhttps://www.netdata.cloud/monitoring-101/homebridge-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/homebridge-monitoring/<h2 id="homebridge-monitoring">Homebridge Monitoring</h2> <h3 id="what-is-homebridge">What Is Homebridge?</h3> <p>Homebridge is a lightweight Node.js server that emulates the iOS HomeKit API. It allows you to connect all your smart home devices, which may not natively support HomeKit, to the Apple ecosystem. By integrating a wide array of home automation devices from various brands into a single cohesive environment, Homebridge plays a pivotal role in efficient home automation management.</p> <h3 id="monitoring-homebridge-with-netdata">Monitoring Homebridge With Netdata</h3> <p>To monitor Homebridge effectively, utilizing the <a href="https://github.com/lstrojny/homebridge-prometheus-exporter">Homebridge Prometheus Exporter</a>, Netdata provides a comprehensive solution. Netdata uses an openmetrics (Prometheus) exporter approach, capable of ingesting data from any Prometheus exporter, offering you automated dashboards, alerts, and more—all without the need for a separate Prometheus server or Grafana. This streamlined, powerful integration makes Homebridge monitoring seamless and highly efficient.</p>Homey Monitoringhttps://www.netdata.cloud/monitoring-101/homey-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/homey-monitoring/<h2 id="homey-monitoring">Homey Monitoring</h2> <h3 id="what-is-homey">What Is Homey?</h3> <p>Homey is a smart home controller that allows users to manage and automate their home appliances and devices, offering a seamless and integrated smart living experience. Its user-friendly interface and compatibility with a wide range of smart devices make it a popular choice for home automation enthusiasts.</p> <h3 id="monitoring-homey-with-netdata">Monitoring Homey With Netdata</h3> <p>Netdata provides a comprehensive and efficient way to monitor Homey using the Homey Prometheus Exporter. By leveraging an openmetrics (Prometheus) exporter, Netdata enables the ingestion of data from any Prometheus exporter. This means you can monitor Homey efficiently without the need for a Prometheus server or Grafana. Netdata offers automated dashboards, alerts, and detailed real-time monitoring, making it an essential tool for maintaining the optimal performance of your smart home setup.</p>Honeypot Monitoringhttps://www.netdata.cloud/monitoring-101/honeypot-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/honeypot-monitoring/<h2 id="honeypot-monitoring">Honeypot Monitoring</h2> <h3 id="what-is-honeypot">What Is Honeypot?</h3> <p>A honeypot is a security mechanism that creates a virtual trap to entice cyber attackers. It essentially offers an isolated and controlled environment where malicious activities can be detected and studied without compromising real systems. Used prominently in cybersecurity, a honeypot mimics a legitimate system to lure hackers, allowing organizations to analyze attack techniques and enhance system defenses.</p> <h3 id="monitoring-honeypot-with-netdata">Monitoring Honeypot With Netdata</h3> <p>Monitoring Honeypot with Netdata leverages the <a href="https://github.com/Intrinsec/honeypot_exporter">Intrinsec honeypot_exporter</a> using an openmetrics (Prometheus) exporter. Netdata excels by ingesting data from any Prometheus exporter, providing users automated dashboards, alerts, and insights without the need for a Prometheus server or Grafana. This seamless integration enables real-time visibility into Honeypot metrics, facilitating efficient threat detection and management.</p>How To Fix CockroachDB Admission Control Throttlinghttps://www.netdata.cloud/guides/cockroachdb/cockroachdb-admission-control-throttling/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/cockroachdb/cockroachdb-admission-control-throttling/<p>When admission control starts queuing requests, p99 latency climbs while throughput stays flat or degrades. The cluster hasn&rsquo;t crashed, disks aren&rsquo;t full, and CPU may not be saturated. An internal flow-control system decided the node or store is at capacity and started holding work back to protect itself.</p> <p>Admission control (v21.2+, enabled by default since v22.1) regulates work through five queues: <code>kv</code>, <code>sql-kv-response</code>, <code>sql-sql-response</code>, <code>elastic-cpu</code>, and <code>store-write</code>. Each gates a different class of work with distinct triggers. Knowing which queue is deep and why is the difference between a five-minute diagnosis and a multi-hour investigation into &ldquo;why is the database slow.&rdquo;</p>How To Tune ClickHouse Async Inserts: Key Settingshttps://www.netdata.cloud/guides/clickhouse/clickhouse-async-inserts-tuning/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/clickhouse/clickhouse-async-inserts-tuning/<p>Async inserts move batching responsibility from the client to the ClickHouse server. The server buffers rows and flushes them as larger blocks instead of persisting every INSERT as a separate part. When the root cause is an unbatchable client, this stops the small-inserts anti-pattern from flooding the merge pool. When the root cause is high-cardinality partitioning or sustained over-ingestion, async inserts relocate the crisis into an in-memory buffer that loses data on crash and hides backpressure from the application.</p>HPE Smart Arrays Monitoringhttps://www.netdata.cloud/monitoring-101/hpssa-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/hpssa-monitoring/<h2 id="hpe-smart-arrays-monitoring">HPE Smart Arrays Monitoring</h2> <h3 id="what-is-hpe-smart-arrays">What Is HPE Smart Arrays?</h3> <p>HPE Smart Arrays are hardware RAID controllers from Hewlett Packard Enterprise designed to manage data storage that is highly reliable and enhances system performance. These controllers are integral for businesses that require robust and scalable storage systems, often used in server environments to support critical applications.</p> <h3 id="monitoring-hpe-smart-arrays-with-netdata">Monitoring HPE Smart Arrays With Netdata</h3> <p>Netdata provides a comprehensive monitoring tool specifically designed for HPE Smart Arrays, which allows real-time insights into the health and performance of your storage systems. By leveraging the HPE Smart Arrays monitoring tool, you can stay informed about any potential issues or performance bottlenecks before they impact your operations.</p>HTTP Endpoints Monitoringhttps://www.netdata.cloud/monitoring-101/http-endpoints-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/http-endpoints-monitoring/<p>The <a href="https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol">HTTP protocol</a> has become the de facto standard application layer protocol of the internet. From publicly available web sites and APIs to “inter-process” communications in REST based microservice architectures or large <a href="https://en.wikipedia.org/wiki/Service-oriented_architecture">Service Oriented Architectures</a> based on <a href="https://en.wikipedia.org/wiki/SOAP">SOAP</a>, you find HTTP being used again and again, due to its simplicity and our familiarity with it. How many protocols can you name that have <a href="https://imgur.com/gallery/4KqWq">memes</a> for their status codes? Of course, such a popular protocol has endless pages written about how to properly monitor the services that rely on it, with many options specific to every use case. What you will learn here is how to get your basics done in monitoring HTTP endpoints, so you can be up and running in a few minutes, monitoring all HTTP services in your entire infrastructure.</p>HTTP Endpoints Monitoringhttps://www.netdata.cloud/monitoring-101/httpcheck-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/httpcheck-monitoring/<h2 id="http-endpoints-monitoring">HTTP Endpoints Monitoring</h2> <h3 id="what-is-http-endpoints">What Is HTTP Endpoints?</h3> <p>HTTP Endpoints are specific URLs or web services that applications or users interact with. Monitoring these endpoints involves tracking their availability, response times, and reliability to ensure smooth and efficient operation of web services.</p> <h3 id="monitoring-http-endpoints-with-netdata">Monitoring HTTP Endpoints With Netdata</h3> <p>Netdata offers a comprehensive HTTP Endpoints monitoring tool, designed to provide real-time insights into your web services. With Netdata, you can monitor HTTP Endpoints to identify issues like increased response times or server connectivity problems before they impact user experience. You can <a href="https://app.netdata.cloud/?utm_source=website&amp;utm_content=monitoring101">sign up for a free trial</a> or check out a <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">live demo</a> to see how it works.</p>Hubble Monitoringhttps://www.netdata.cloud/monitoring-101/hubble-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/hubble-monitoring/<h2 id="hubble-monitoring">Hubble Monitoring</h2> <h3 id="what-is-hubble">What Is Hubble?</h3> <p>Hubble is an advanced, open-source network observability tool that provides detailed telemetry and security observability for cloud-native environments. By leveraging Hubble, DevOps engineers and IT professionals can gain deep insights into the network traffic and infrastructure within their Kubernetes clusters, powered by the Cilium network plugin.</p> <h3 id="monitoring-hubble-with-netdata">Monitoring Hubble With Netdata</h3> <p>Monitoring Hubble with Netdata allows you to leverage its openmetrics (Prometheus) exporter capabilities. Netdata seamlessly ingests data from any Prometheus exporter, allowing you to monitor Hubble efficiently. With Netdata, users benefit from automated dashboards and smart alerting systems without the need for setting up a Prometheus server or Grafana. This streamlined approach facilitates a faster and more efficient workflow, enabling SREs and IT admins to focus on responding to the alerts and insights rather than setting up and maintaining complex systems.</p>IBM AIX Systems Njmon Monitoringhttps://www.netdata.cloud/monitoring-101/ibm_aix_njmon-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/ibm_aix_njmon-monitoring/<h2 id="ibm-aix-systems-njmon-monitoring">IBM AIX Systems Njmon Monitoring</h2> <h3 id="what-is-ibm-aix-systems-njmon">What Is IBM AIX Systems Njmon?</h3> <p>IBM AIX systems Njmon is a state-of-the-art tool designed for performance monitoring and management of IBM AIX operating environments. It effectively provides insights into system health and performance metrics, ensuring smooth IT infrastructure operation. With Njmon, you can seamlessly monitor data collection in real time without impacting system performance.</p> <h3 id="monitoring-ibm-aix-systems-njmon-with-netdata">Monitoring IBM AIX Systems Njmon With Netdata</h3> <p>To monitor IBM AIX Systems Njmon efficiently, Netdata provides a robust solution utilizing an openmetrics (Prometheus) exporter. This integration allows users to ingest data directly from any Prometheus endpoint without needing a dedicated Prometheus server or Grafana setup. With Netdata, you gain access to automated dashboards, alerts, and insights, drastically simplifying the process of monitoring complex systems like IBM AIX.</p>IBM CryptoExpress (CEX) Monitoringhttps://www.netdata.cloud/monitoring-101/ibm_cex-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/ibm_cex-monitoring/<h2 id="ibm-cryptoexpress-cex-monitoring">IBM CryptoExpress (CEX) Monitoring</h2> <h3 id="what-is-ibm-cryptoexpress-cex">What Is IBM CryptoExpress (CEX)?</h3> <p>IBM CryptoExpress (CEX) cards are specialized hardware devices used in IBM systems for cryptographic operations, providing secure encryption and decryption services. These cards are crucial for businesses that require high-security standards for their data transactions and management.</p> <h3 id="monitoring-ibm-cryptoexpress-cex-with-netdata">Monitoring IBM CryptoExpress (CEX) With Netdata</h3> <p>To efficiently monitor IBM CryptoExpress (CEX), Netdata utilizes the openmetrics (Prometheus) exporter available for these cards. This allows Netdata to seamlessly integrate with any existing Prometheus exporter to collect vital metrics that give insights into cryptographic performance and management. With Netdata, automated dashboards and alerts are readily available without the need for setting up a separate Prometheus server or Grafana, simplifying the monitoring process.</p>IBM MQ Monitoringhttps://www.netdata.cloud/monitoring-101/ibm_mq-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/ibm_mq-monitoring/<h2 id="ibm-mq-monitoring">IBM MQ Monitoring</h2> <h3 id="what-is-ibm-mq">What Is IBM MQ?</h3> <p>IBM MQ is a powerful messaging middleware designed to simplify, accelerate, and facilitate the transport of messages between different platforms and applications. It allows for secure and reliable message transfer, ensuring that businesses can integrate multiple complex systems seamlessly.</p> <h3 id="monitoring-ibm-mq-with-netdata">Monitoring IBM MQ With Netdata</h3> <p>To monitor IBM MQ effectively, Netdata provides a comprehensive solution using the <a href="https://github.com/agebhar1/mq_exporter">MQ Exporter</a>, which is an openmetrics (prometheus) exporter. With Netdata, you can effortlessly ingest data from any Prometheus exporter without the need for a Prometheus server or Grafana for visualizations. This means you can access automated dashboards, receive intelligent alerts, and enjoy rich visual insights into your IBM MQ metrics—all integrated seamlessly within the Netdata platform.</p>IBM Spectrum Monitoringhttps://www.netdata.cloud/monitoring-101/ibm_spectrum-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/ibm_spectrum-monitoring/<h2 id="ibm-spectrum-monitoring">IBM Spectrum Monitoring</h2> <h3 id="what-is-ibm-spectrum">What Is IBM Spectrum?</h3> <p>IBM Spectrum is a suite of data management software from IBM, designed to manage storage resources as efficiently and cost-effectively as possible. With solutions that optimize analytics, data protection, and storage, IBM Spectrum is essential for organizations that rely on large-scale data environments.</p> <h3 id="monitoring-ibm-spectrum-with-netdata">Monitoring IBM Spectrum With Netdata</h3> <p>To monitor IBM Spectrum, Netdata leverages an openmetrics, specifically a Prometheus exporter, known as the <a href="https://github.com/topine/ibm-spectrum-exporter">IBM Spectrum Exporter</a>. Netdata’s integration provides dynamic monitoring capabilities, turning data collected from IBM Spectrum into insightful analytics. Netdata is unique in its ability to ingest data from any Prometheus exporter, and users benefit from automated dashboards, real-time alerts, and more—all without needing a separate Prometheus server or Grafana.</p>IBM Spectrum Virtualize Monitoringhttps://www.netdata.cloud/monitoring-101/ibm_spectrum_virtualize-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/ibm_spectrum_virtualize-monitoring/<h2 id="ibm-spectrum-virtualize-monitoring">IBM Spectrum Virtualize Monitoring</h2> <h3 id="what-is-ibm-spectrum-virtualize">What Is IBM Spectrum Virtualize?</h3> <p>IBM Spectrum Virtualize is a sophisticated software that enables efficient storage virtualization, streamlining storage management and enhancing performance. It is widely utilized in various IT environments to manage storage resources, boosting performance and scalability across different platforms.</p> <h3 id="monitoring-ibm-spectrum-virtualize-with-netdata">Monitoring IBM Spectrum Virtualize With Netdata</h3> <p>Monitoring IBM Spectrum Virtualize becomes seamless and highly efficient with Netdata. By using an openmetrics (Prometheus) exporter, specifically the <a href="https://github.com/bluecmd/spectrum_virtualize_exporter">spectrum_virtualize_exporter</a>, Netdata can effortlessly ingest data from any Prometheus exporter. This functionality allows users to access automated dashboards, receive real-time alerts, and gain deep insights without requiring a Prometheus server or Grafana. The integration facilitates comprehensive visibility into your storage virtualization metrics, ensuring optimal performance and resource utilization.</p>IBM Z Hardware Management Console Monitoringhttps://www.netdata.cloud/monitoring-101/ibm_zhmc-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/ibm_zhmc-monitoring/<h2 id="ibm-z-hardware-management-console-monitoring">IBM Z Hardware Management Console Monitoring</h2> <h3 id="what-is-ibm-z-hardware-management-console">What Is IBM Z Hardware Management Console?</h3> <p>The IBM Z Hardware Management Console (HMC) is a critical component for managing enterprise-class mainframe systems. It provides an interface for controlling hardware, managing partitions, and configuring features of IBM Z servers, enabling efficient mainframe management.</p> <h3 id="monitoring-ibm-z-hardware-management-console-with-netdata">Monitoring IBM Z Hardware Management Console With Netdata</h3> <p>To optimize performance and ensure reliable operation, monitoring the IBM Z HMC is crucial. Netdata provides a robust solution for this task by using an openmetrics (Prometheus) exporter, specifically the <a href="https://github.com/zhmcclient/zhmc-prometheus-exporter">IBM Z HMC Exporter</a>. This enables seamless integration with Netdata&rsquo;s monitoring platform, allowing users to ingest metrics without needing a standalone Prometheus server or Grafana setup.</p>Icecast Monitoringhttps://www.netdata.cloud/monitoring-101/icecast-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/icecast-monitoring/<h2 id="icecast-monitoring">Icecast Monitoring</h2> <h3 id="what-is-icecast">What Is Icecast?</h3> <p>Icecast is a free and open-source streaming media server which supports various streaming formats, including MP3. It&rsquo;s widely used for setting up online radio stations and creating or distributing online audio content. For more information, visit the <a href="https://icecast.org/">Icecast official website</a>.</p> <h3 id="monitoring-icecast-with-netdata">Monitoring Icecast With Netdata</h3> <p>Netdata offers an unparalleled solution for monitoring Icecast, providing real-time insights and detailed metrics to optimize performance. As a comprehensive Icecast monitoring tool, Netdata allows you to track listener counts, server performance, and more, ensuring your streaming server operates at its best.</p>InfluxDB Monitoringhttps://www.netdata.cloud/monitoring-101/influxdb-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/influxdb-monitoring/<h2 id="influxdb-monitoring">InfluxDB Monitoring</h2> <h3 id="what-is-influxdb">What Is InfluxDB?</h3> <p>InfluxDB is a high-performance time series database designed for storing and analyzing time-stamped data. Used extensively for monitoring, it offers powerful data retention, querying, and analytics features that make it a popular choice for real-time applications. If you&rsquo;re working with metrics, logs, or any form of timestamped data, understanding how to effectively monitor InfluxDB can significantly enhance your infrastructure&rsquo;s performance.</p> <h3 id="monitoring-influxdb-with-netdata">Monitoring InfluxDB With Netdata</h3> <p>To monitor InfluxDB seamlessly, Netdata utilizes an openmetrics (Prometheus) exporter. The flexibility of Netdata allows it to ingest data from any Prometheus exporter. This means you can access automated dashboards, receive alerts, and more, without the need for a dedicated Prometheus server or Grafana. By leveraging the <a href="https://github.com/prometheus/influxdb_exporter">InfluxDB exporter</a>, Netdata provides comprehensive visibility into your InfluxDB instances, enabling you to optimize performance efficiently.</p>Integrationshttps://www.netdata.cloud/integrations/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/integrations/Intel GPU Monitoringhttps://www.netdata.cloud/monitoring-101/intelgpu-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/intelgpu-monitoring/<h2 id="intel-gpu-monitoring">Intel GPU Monitoring</h2> <h3 id="what-is-intel-gpu">What Is Intel GPU?</h3> <p>Intel Graphics Processing Units (GPUs) are integrated into Intel CPUs, offering powerful graphics capabilities for a variety of applications. These GPUs are particularly important for managing graphics-intensive workloads and improving the overall performance of systems using Intel-based hardware.</p> <h3 id="monitoring-intel-gpu-with-netdata">Monitoring Intel GPU With Netdata</h3> <p>Netdata&rsquo;s Intel GPU monitoring tool provides real-time, insightful data that allows you to track the performance and health of your Intel GPU seamlessly. With Netdata, you can monitor Intel GPU metrics like frequency, power consumption, and engine utilization without compromising system security or performance.</p>Interface discards with low utilization: diagnosing ifInDiscards/ifOutDiscardshttps://www.netdata.cloud/guides/network/network-interface-discards/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-interface-discards/<p>ifOutDiscards is climbing on a critical uplink. Utilization sits at 35%. No CRC errors, no input errors, no physical-layer alarms. The link is up and passing traffic, but something is silently dropping packets, and your averaged utilization metrics are not telling you why.</p> <p>The gap between what the counters show and what the silicon is doing comes down to two things: the averaging window on utilization, and the fact that discards happen at buffer-queue granularity, not at link-rate granularity.</p>Interface flapping: link up/down storms and their blast radiushttps://www.netdata.cloud/guides/network/network-interface-flapping/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-interface-flapping/<p>Interface flapping is when a network interface oscillates rapidly between up and down states. Each transition generates a linkDown/linkUp trap pair, syslog entries, and an STP topology change notification. At low rates this is operational noise. At high rates it becomes a multi-layer failure: the trap receiver overflows, the syslog pipeline saturates, STP reconvergence flushes MAC tables across the VLAN, and the monitoring platform reports misleading availability because the poll interval is slower than the flap cadence.</p>Interface input/output errors: finding the bad link with ifInErrors/ifOutErrorshttps://www.netdata.cloud/guides/network/network-interface-errors/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-interface-errors/<p>A switch port reports 47,000 input errors and climbing. The interface is up and traffic is flowing. Your monitoring fired an alert on ifInErrors crossing threshold. Now you need to determine whether this is a dirty fiber, a dying SFP, a duplex mismatch, buffer exhaustion, or a counter artifact from an interface flap.</p> <p>ifInErrors (.1.3.6.1.2.1.2.2.1.14) and ifOutErrors (.1.3.6.1.2.1.2.2.1.20) are aggregate counters. They tell you something is wrong, but not what. The counter is a sum of multiple error types: CRC, alignment, runts, giants, overruns, frame errors, and on some platforms, input drops. A frame that arrives with both a CRC error and a runt condition increments ifInErrors by exactly 1, not 2. You cannot reconcile the sub-counters against the aggregate by simple addition.</p>Internet Information Services (IIS) Monitoringhttps://www.netdata.cloud/monitoring-101/iis-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/iis-monitoring/<h2 id="iis-internet-information-services">IIS (Internet Information Services)</h2> <p>IIS stands for Internet Information Services, which is a web server software package designed for Windows Server. IIS can host static or dynamic websites, and serve content such as HTML, JavaScript, or media files to a user’s browser. IIS is versatile and stable, and it has been widely used in production for many years.</p> <p>IIS is composed of the following basic components:</p> <ul> <li><strong>Web Server</strong> <ul> <li>The most common use-case IIS is used for is to host websites and ASP.NET web applications.</li> </ul> </li> <li><strong>Security</strong> <ul> <li>IIS provides robust security through Windows authentication, and is capable of filtering requests, and management of TLS certificates, so that you can enable HTTPS or SFTP on your web server.</li> </ul> </li> <li><strong>Management</strong> <ul> <li>IIS can be managed locally or remotely through the Console, CLI, PowerShell and other tools</li> </ul> </li> </ul> <h2 id="iis-monitoring">IIS Monitoring</h2> <p>To holistically monitor IIS, you need to track various aspects of its performance, such as:</p>IPFS Monitoringhttps://www.netdata.cloud/monitoring-101/ipfs-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/ipfs-monitoring/<h2 id="ipfs-monitoring">IPFS Monitoring</h2> <h3 id="what-is-ipfs">What Is IPFS?</h3> <p><a href="https://ipfs.tech/">IPFS (InterPlanetary File System)</a> is a protocol and peer-to-peer network for storing and sharing data in a distributed file system. IPFS allows users to host and receive content in a decentralized manner, making it well-suited for distributed and resilient applications.</p> <h3 id="monitoring-ipfs-with-netdata">Monitoring IPFS With Netdata</h3> <p>To effectively monitor IPFS, you need a robust tool that provides real-time insights into network activity, file storage, and other critical metrics. Netdata&rsquo;s IPFS monitoring tool offers comprehensive visibility, enabling you to ensure the stability and performance of your IPFS nodes.</p>ISC DHCP Monitoringhttps://www.netdata.cloud/monitoring-101/isc_dhcpd-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/isc_dhcpd-monitoring/<h2 id="isc-dhcp-monitoring">ISC DHCP Monitoring</h2> <h3 id="what-is-isc-dhcp">What Is ISC DHCP?</h3> <p><a href="https://www.isc.org/dhcp/">ISC DHCP</a> is a widely used open-source DHCP server software that automates the assignment and management of IP addresses, enabling efficient network management. It is capable of serving both IPv4 and IPv6 clients and supports various network topologies.</p> <h3 id="monitoring-isc-dhcp-with-netdata">Monitoring ISC DHCP With Netdata</h3> <p>Monitoring ISC DHCP efficiently is crucial for ensuring network reliability and performance. With Netdata, a leading ISC DHCP monitoring tool, you gain real-time insights into DHCP lease usage and pool utilization. Netdata provides comprehensive data visualization to help you track key metrics and quickly diagnose any issues in your DHCP environment.</p>ISC DHCPd Monitoringhttps://www.netdata.cloud/monitoring-101/isc-dhcpd-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/isc-dhcpd-monitoring/<h2 id="what-is-isc-dhcpd">What is ISC DHCPd?</h2> <p>ISC DHCP is a DHCP server that supports both IPv4 and IPv6, and is suitable for use in high-volume and high-reliability applications.</p> <h2 id="monitoring-isc-dhcpd-with-netdata">Monitoring ISC DHCPd with Netdata</h2> <p>The prerequisites for monitoring ISC DHCPd with Netdata are to have ISC DHCPd and <a href="https://learn.netdata.cloud/docs/cloud/get-started/">Netdata installed</a> on your system.</p> <p>Netdata auto discovers hundreds of services, and for those it doesn&rsquo;t turning on manual discovery is a one line configuration. For more information on configuring Netdata for ISC DHCPd monitoring please read the collector <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/isc_dhcpd/">documentation</a>.</p>ISCBind (RNDC) Monitoringhttps://www.netdata.cloud/monitoring-101/iscbind-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/iscbind-monitoring/<h2 id="what-is-iscbind-rndc">What is ISCBind (RNDC)?</h2> <h2 id="monitoring-iscbind-rndc-with-netdata">Monitoring ISCBind (RNDC) with Netdata</h2> <p>The prerequisites for monitoring ISCBind with Netdata are to have ISCBind and <a href="https://learn.netdata.cloud/docs/cloud/get-started/">Netdata installed</a> on your system.</p> <p>Netdata auto discovers hundreds of services, and for those it doesn&rsquo;t turning on manual discovery is a one line configuration. For more information on configuring Netdata for ISCBind monitoring please read the collector <a href="https://learn.netdata.cloud/docs/agent/collectors/python.d.plugin/bind_rndc/">documentation</a>.</p> <p>You should now see the ISCBind section on the Overview tab in Netdata Cloud already populated with charts about all the metrics you care about.</p>Jarvis Standing Desk Monitoringhttps://www.netdata.cloud/monitoring-101/jarvis-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/jarvis-monitoring/<h2 id="jarvis-standing-desk-monitoring">Jarvis Standing Desk Monitoring</h2> <h3 id="what-is-jarvis-standing-desk">What Is Jarvis Standing Desk?</h3> <p>The Jarvis Standing Desk is an ergonomic workspace solution designed to promote better posture and flexibility in the office or home environment. Its ability to adjust height with ease helps users to maintain productive and healthy working conditions. With the increasing need for workspace ergonomics, monitoring the usage of standing desks like Jarvis becomes crucial to ensure optimal usage and benefit from the ergonomic advantages they offer.</p>Java Springboot Applications Monitoringhttps://www.netdata.cloud/monitoring-101/springboot2-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/springboot2-monitoring/<h2 id="what-is-java-springboot2">What is Java Springboot2?</h2> <p>Java Springboot2 is an open source Java-based framework used to create web applications. It is based on the Spring framework and provides a range of features such as enhanced dependency injection, abstract data access layers, and a powerful configuration system. Springboot2 also enables developers to quickly create and deploy applications and services. It can be used to rapidly develop applications and services that are cloud-native and highly secure.</p>Jenkins Monitoringhttps://www.netdata.cloud/monitoring-101/jenkins-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/jenkins-monitoring/<h2 id="jenkins-monitoring">Jenkins Monitoring</h2> <h3 id="what-is-jenkins">What Is Jenkins?</h3> <p><a href="https://www.jenkins.io/">Jenkins</a> is an open-source automation server that is used to automate the process of building, testing, and deploying software. It is a continuous integration tool that enables developers to continually test and integrate their codebase. It supports a range of plugins for building and deploying applications.</p> <h3 id="monitoring-jenkins-with-netdata">Monitoring Jenkins With Netdata</h3> <p>To effectively monitor Jenkins, Netdata employs a robust methodology using an openmetrics (Prometheus) exporter. This integration is seamless as Netdata can ingest data from any Prometheus exporter. It saves users from having to maintain separate Prometheus server and Grafana dashboard setups. With Netdata, automated dashboards and alerts become instantly accessible, providing real-time insights and alerting on critical metrics.</p>JMX Monitoringhttps://www.netdata.cloud/monitoring-101/jmx-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/jmx-monitoring/<h2 id="jmx-monitoring">JMX Monitoring</h2> <h3 id="what-is-jmx">What Is JMX?</h3> <p>Java Management Extensions (JMX) is a technology that facilitates the management and monitoring of Java applications. It provides crucial insights into application performance through MBeans (Managed Beans), which represent resources such as applications or any device that needs to be managed.</p> <h3 id="monitoring-jmx-with-netdata">Monitoring JMX With Netdata</h3> <p>Leveraging Netdata for JMX monitoring adds a powerful dimension to your DevOps toolkit. With Netdata, you can monitor JMX seamlessly by using an OpenMetrics (Prometheus) exporter. Netdata can ingest data from any Prometheus exporter, offering automated dashboards, alerts, and more, without requiring a Prometheus server or Grafana. This means you can have real-time visibility into JMX metrics with minimal setup.</p>Journald Monitoringhttps://www.netdata.cloud/monitoring-101/journald-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/journald-monitoring/<h2 id="journald-monitoring">Journald Monitoring</h2> <h3 id="what-is-journald">What Is Journald?</h3> <p>Journald is a component of the systemd suite that manages and facilitates logging within Linux systems. It collects and stores logs in a structured manner, offering a unified logging system to better manage system events and logs. Understanding the intricacies of journald is essential for system administrators and developers who rely on consistent and efficient log management.</p> <h3 id="monitoring-journald-with-netdata">Monitoring Journald With Netdata</h3> <p>To monitor journald, Netdata employs an openmetrics (Prometheus) exporter, specifically the <a href="https://github.com/dead-claudia/journald-exporter">journald-exporter</a>. This approach allows Netdata to ingest data from any Prometheus exporter, providing users with automated dashboards and alerts without the need for a Prometheus server or Grafana. This capability makes Netdata an excellent journald monitoring tool due to its simplicity and efficiency in onboarding and dashboard automation.</p>K8s Kubelet Monitoringhttps://www.netdata.cloud/monitoring-101/kubelet-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/kubelet-monitoring/<h2 id="what-is-k8s-kubelet">What is K8s Kubelet?</h2> <p><a href="https://kubernetes.io/docs/concepts/architecture/#kubelet"><code>Kubelet</code></a> is an agent that runs on each node in the cluster. It makes sure that containers are running in a pod.</p> <h2 id="monitoring-k8s-kubelet-with-netdata">Monitoring K8s Kubelet with Netdata</h2> <p>The prerequisite for monitoring K8s Kubelet with Netdata is to <a href="https://learn.netdata.cloud/docs/cloud/get-started/">Netdata installed</a> on your system.</p> <p>Netdata auto discovers hundreds of services, and for those it doesn&rsquo;t turning on manual discovery is a one line configuration. For more information on configuring Netdata for K8s Kubelet monitoring please read the collector <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/k8s_kubelet/">documentation</a>.</p>Kafka __consumer_offsets growing huge: compaction failure on the offsets topichttps://www.netdata.cloud/guides/kafka/kafka-consumer-offsets-topic-growing/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-consumer-offsets-topic-growing/<p>One broker&rsquo;s disk is climbing faster than its peers, or <code>__consumer_offsets</code> has grown to multiple gigabytes while producer traffic is flat. This internal topic is compacted by default; its size should stay roughly proportional to active consumer groups and partitions. Unbounded growth means the log cleaner has stalled or crashed. The failure is silent: producers and consumers keep working, but every offset commit appends a record that compaction will never remove. Growth is not evenly distributed: <code>__consumer_offsets</code> is partitioned by <code>group.id</code> hash, so a stalled cleaner on one broker affects only the partitions in that broker&rsquo;s <code>log.dirs</code>. Eventually the log directory fills, and the broker may mark it offline.</p>Kafka ActiveControllerCount not equal to 1: no controller or split brainhttps://www.netdata.cloud/guides/kafka/kafka-no-active-controller/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-no-active-controller/<p>When the cluster-wide sum of <code>kafka.controller:type=KafkaController,name=ActiveControllerCount</code> is not 1, the cluster has either no active controller or multiple active controllers. A sum of 0 means no broker is steering metadata. A sum greater than 1 means split brain. Either way, this is a control-plane failure. Existing partition leaders usually keep serving produce and fetch requests, so the data plane may look healthy at first. Any broker failure, partition reassignment, or topic operation will stall because there is no controller to process it, or multiple controllers are processing conflicting operations.</p>Kafka Broker May Not Be Available: How To Fix Ithttps://www.netdata.cloud/guides/kafka/kafka-broker-may-not-be-available/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-broker-may-not-be-available/<p>Client logs show a warning like this:</p> <pre tabindex="0"><code>WARN [Producer clientId=...] Connection to node -1 could not be established. Broker may not be available. </code></pre><p>Python clients may raise <code>kafka.errors.NoBrokersAvailable</code>, while librdkafka-based clients report <code>Connection refused</code> against the broker address. The bootstrap server is often reachable; ping and telnet succeed, yet the client still fails. This happens because Kafka clients use the bootstrap connection only to fetch metadata. After that, they disconnect and try to open fresh TCP connections to the host:port pairs advertised in the metadata response. If those endpoints are unreachable, misconfigured, or secured differently than the client expects, the connection fails even though the bootstrap succeeded.</p>Kafka Broker Out Of Disk: How To Fix Ithttps://www.netdata.cloud/guides/kafka/kafka-broker-out-of-disk/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-broker-out-of-disk/<p>When a Kafka broker exhausts disk space on a log directory, it does not throttle. It marks that directory offline or crashes entirely. Partitions on the failed directory become unavailable immediately. If all <code>log.dirs</code> fail, the broker exits. You may see under-replicated partitions or producer timeouts seconds before failure, but often the first sign is a hard process exit with <code>No space left on device</code>.</p> <p>Kafka assigns new partitions round-robin across <code>log.dirs</code>, but existing partitions never move automatically. One mount can hit 100% while others sit at 50%, so host-level disk alerts are misleading. Recovery is not a simple matter of freeing a few gigabytes: an unclean shutdown forces hours of segment scanning and index rebuild on restart.</p>Kafka CommitFailedException: rebalanced-out consumers and poll loop timeoutshttps://www.netdata.cloud/guides/kafka/kafka-commit-failed-exception/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-commit-failed-exception/<p><code>CommitFailedException</code> with the message that the group has already rebalanced and assigned the partitions to another member means the time between <code>poll()</code> calls exceeded <code>max.poll.interval.ms</code>. The coordinator evicted the consumer and rejected the in-flight offset commit.</p> <p>When one consumer is evicted, the group rebalances. If other consumers are also slow, or if the rebalance itself takes long enough that healthy consumers miss the same deadline, the group enters a rebalance storm: it oscillates between <code>JoinGroup</code> and <code>SyncGroup</code> without stabilizing, and lag grows without bound.</p>Kafka consumer group lag growing: detection, lag-as-time, and root causeshttps://www.netdata.cloud/guides/kafka/kafka-consumer-group-lag-growing/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-consumer-group-lag-growing/<p>When a consumer group falls behind, lag climbs monotonically. If the committed offset crosses the retention boundary, consumers hit <code>OffsetOutOfRangeException</code> and must reset to earliest or latest, reprocessing or skipping data. Restarting the consumer is a common first reaction, but broker-side fetch latency, page cache eviction, and network saturation are equally common culprits. Detect lag accurately, convert it to time, and trace the root cause without guessing.</p> <h2 id="what-this-means">What this means</h2> <p>Consumer lag is <code>log-end-offset</code> minus the last committed offset for each partition in a group. Monotonic growth means the consumer is not keeping up with the production rate. The immediate risk is committed offset falling behind log retention, forcing a reset to earliest or latest.</p>Kafka consumer group rebalancing too often: heartbeats, session timeout, and assignorshttps://www.netdata.cloud/guides/kafka/kafka-consumer-group-rebalancing-frequently/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-consumer-group-rebalancing-frequently/<p>Consumer group lag is growing, application logs are full of <code>JoinGroup</code> and <code>SyncGroup</code> messages, and <code>kafka-consumer-groups.sh</code> shows the group flipping between <code>Stable</code> and <code>PreparingRebalance</code>. Healthy groups rebalance only during membership changes and planned deployments. More than two or three rebalances per hour for a stable group signals instability. The usual cause is a mismatch between processing latency and one of three timeouts: <code>session.timeout.ms</code>, <code>heartbeat.interval.ms</code>, or <code>max.poll.interval.ms</code>. The assignor strategy and static membership configuration determine how painful each rebalance is.</p>Kafka Consumer Lag Monitoringhttps://www.netdata.cloud/monitoring-101/kafka_consumer_lag-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/kafka_consumer_lag-monitoring/<h2 id="kafka-consumer-lag-monitoring">Kafka Consumer Lag Monitoring</h2> <h3 id="what-is-kafka-consumer-lag">What Is Kafka Consumer Lag?</h3> <p>Kafka Consumer Lag represents the difference between the latest offset of a partition and the offset of the consumer group. It is a crucial metric within Kafka&rsquo;s architecture as it indicates the latency for messages consumed by consumers in a Kafka topic. Properly monitoring Kafka Consumer Lag ensures efficient message queue management and prevents bottlenecks in your streaming applications.</p> <h3 id="monitoring-kafka-consumer-lag-with-netdata">Monitoring Kafka Consumer Lag With Netdata</h3> <p>To monitor Kafka Consumer Lag, Netdata uses an openmetrics (Prometheus) exporter. Netdata&rsquo;s $name monitoring tool allows you to ingest data from any Prometheus exporter seamlessly, offering automatic dashboards, alerts, and comprehensive insights without requiring a Prometheus server or Grafana. By leveraging Netdata&rsquo;s dashboards, DevOps and IT teams can effectively track Kafka performance, ensuring real-time data processing stays smooth and efficient.</p>Kafka consumer rebalance storm: stuck in PreparingRebalance and max.poll.interval.mshttps://www.netdata.cloud/guides/kafka/kafka-consumer-rebalance-storm/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-consumer-rebalance-storm/<p>Consumer group lag climbs while brokers report zero under-replicated partitions, normal produce and fetch latency, and normal request handler idle percent. The consumer group oscillates between Stable, PreparingRebalance, and CompletingRebalance without settling long enough to make progress. Every rebalance cycle pauses consumption; lag grows because time spent rebalancing dwarfs time spent fetching. This is a consumer rebalance storm. It is almost always a client-side timeout or processing issue. Look for CommitFailedException or max.poll.interval.ms exceeded in consumer logs.</p>Kafka controller event queue backing up: overwhelmed controller and stalled metadatahttps://www.netdata.cloud/guides/kafka/kafka-controller-event-queue-backup/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-controller-event-queue-backup/<p>You see <code>NOT_LEADER_FOR_PARTITION</code> errors spike in client logs. Leader elections stop completing. The active controller&rsquo;s event queue grows and does not drain. Partitions that need new leaders stay offline. The single thread processing partition state changes cannot keep up, and metadata operations stall.</p> <p>In ZooKeeper mode, each event writes to ZooKeeper. In KRaft mode, each event appends to the Raft metadata log. The active controller processes them sequentially. When the queue backs up, the control plane slows. The data plane may continue serving existing leaders, but any failure requiring a state change gets stuck.</p>Kafka disk I/O latency high: await, LocalTimeMs, and the slow-disk brokerhttps://www.netdata.cloud/guides/kafka/kafka-disk-io-latency-high/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-disk-io-latency-high/<p><code>iostat</code> shows <code>await</code> climbing, maybe a disk alert fired. But <code>await</code> alone is not a pageable event. On SSDs and RAID arrays, <code>%util</code> hits 100% under modest load because it measures device busy time, not saturation. What matters is <code>await</code>, the average time for I/O requests to be served. At the Kafka layer, the mirror image is <code>LocalTimeMs</code> in the request latency breakdown. Both spike during normal operations &ndash; broker restart with cold page cache, log compaction, and partition reassignment all drive up disk latency without indicating hardware fault. This guide shows how to distinguish a transient spike from a slow disk that will shrink your ISR and block produce requests.</p>Kafka FailedProduceRequestsPerSec rising: the single best 'producers are hurting' signalhttps://www.netdata.cloud/guides/kafka/kafka-failed-produce-requests/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-failed-produce-requests/<p><code>FailedProduceRequestsPerSec</code> rising is broker-side confirmation that producers are actively being rejected. Unlike client-side timeouts from network blips or producer memory pressure, it only increments when the broker receives a produce request and fails to complete it. The MBean <code>kafka.server:type=BrokerTopicMetrics,name=FailedProduceRequestsPerSec</code> rolls up server-side produce failures into a single rate: <code>NotEnoughReplicasException</code>, <code>NotLeaderOrFollowerException</code>, <code>CorruptRecordException</code>, and others. A sustained nonzero rate means data is not being accepted, and the window for data loss or unavailability is open.</p>Kafka fetch request latency high: FetchConsumer vs FetchFollower and page cache misseshttps://www.netdata.cloud/guides/kafka/kafka-fetch-request-latency-high/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-fetch-request-latency-high/<p>Your tail consumers are lagging, or your under-replicated partition count is climbing. On the broker, <code>kafka.network:type=RequestMetrics,name=TotalTimeMs,request=FetchConsumer</code> or <code>FetchFollower</code> is elevated. Raw fetch latency is a poor signal: consumer long-polling means <code>TotalTimeMs</code> routinely includes the full <code>fetch.max.wait.ms</code> wait even on an idle topic, and follower fetches are paced by the leader&rsquo;s ability to serve segments. The actionable metric is <code>LocalTimeMs</code>, the time the leader spends reading the log. When <code>FetchConsumer</code> <code>LocalTimeMs</code> spikes, the data was not in the OS page cache. When <code>FetchFollower</code> <code>LocalTimeMs</code> spikes, the leader is slow to serve replication reads and ISR shrinks will follow. The sections below show how to tell the two apart, confirm page cache misses, and fix the root cause.</p>Kafka ISR shrinking: IsrShrinksPerSec, flapping, and the cascade to offlinehttps://www.netdata.cloud/guides/kafka/kafka-isr-shrink-storm/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-isr-shrink-storm/<p><code>IsrShrinksPerSec</code> is climbing on your leaders and <code>UnderReplicatedPartitions</code> is no longer zero. If it is flapping &ndash; shrinks followed by expands every few minutes &ndash; the path ends with <code>OfflinePartitionsCount</code> rising and <code>acks=all</code> producers throwing <code>NotEnoughReplicasException</code>. This guide covers that path: how a lagging follower becomes a cluster-wide problem, how to separate flapping from one-way degradation, and how to stop the cascade before partitions go offline.</p> <h2 id="what-this-means">What this means</h2> <p>Kafka leaders maintain an In-Sync Replica set (ISR): followers that have fetched within <code>replica.lag.time.max.ms</code> (default 30 seconds since Kafka 2.5.0; 10 seconds before 2.5.0). When a follower stops fetching or falls behind beyond that window, the leader removes it. <code>IsrShrinksPerSec</code> measures the velocity of these removals. <code>IsrExpandsPerSec</code> measures replicas catching up and rejoining.</p>Kafka JVM heap and Full GC pauses: ISR drops, session timeouts, and right-sizing the heaphttps://www.netdata.cloud/guides/kafka/kafka-jvm-heap-full-gc-pauses/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-jvm-heap-full-gc-pauses/<p>Sporadic <code>UnderReplicatedPartitions</code> and ISR shrinks that do not correlate with disk I/O or network faults, combined with consumer rebalances and <code>NotEnoughReplicasException</code> from producers using <code>acks=all</code>, point to broker JVM heap pressure. Check broker logs for GC pauses in the Old Generation lasting several seconds.</p> <p>Brokers use the JVM heap for metadata, request buffers, and message format conversion. They do not store messages on the heap; the OS page cache handles that. When the heap is misconfigured or under pressure, garbage collection pauses can freeze a broker long enough to trigger ZooKeeper session expirations, follower lag, and cascading availability issues. Full GC pauses exceeding five seconds are the common threshold where these symptoms begin.</p>Kafka KRaft quorum has no leader: current-leader = -1 and frozen metadatahttps://www.netdata.cloud/guides/kafka/kafka-kraft-quorum-no-leader/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-kraft-quorum-no-leader/<p>Topic creation hangs. Partition reassignments stall. Broker logs show metadata operations timing out. On controller nodes, JMX reports <code>kafka.server:type=raft-metrics,attribute=current-leader</code> with value <code>-1</code>, and the quorum state is frozen. Existing producers and consumers continue to read and write, but the control plane is stuck.</p> <h2 id="what-this-means">What this means</h2> <p>The quorum leader acts as the active controller. When <code>current-leader</code> is <code>-1</code>, the local controller has not discovered a leader, which means no node in the quorum can commit new entries to the metadata log. Topic creation, deletion, configuration updates, reassignments, and ISR changes are blocked. Leader elections for partitions that lose their broker also cannot proceed.</p>Kafka LEADER_NOT_AVAILABLE: causes during elections, restarts, and topic creationhttps://www.netdata.cloud/guides/kafka/kafka-leader-not-available/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-leader-not-available/<p><code>LEADER_NOT_AVAILABLE</code> means a client asked a broker to produce or fetch from a partition that has no assigned leader. In healthy clusters this is brief during rolling restarts, controller elections, or topic creation. Persistent errors correlate with <code>OfflinePartitionsCount &gt; 0</code> and indicate the data plane is broken for those partitions. Distinguish this from <code>NOT_LEADER_FOR_PARTITION</code>, which means a leader exists but the client contacted the wrong broker and needs a metadata refresh.</p>Kafka log compaction falling behind: the dead cleaner thread and unbounded disk growthhttps://www.netdata.cloud/guides/kafka/kafka-log-compaction-falling-behind/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-log-compaction-falling-behind/<p>Disk utilization climbs steadily on one or more brokers while producer traffic stays flat. <code>__consumer_offsets</code> balloons from a few gigabytes to hundreds. Under-replicated partitions are at zero, producers show no errors, and standard Kafka alerts are silent. The usual culprit is a dead log cleaner thread: it hit a corrupt record or an OOM during compaction, crashed, and never restarted. Every compacted topic now accumulates records without bound.</p> <p>This failure is silent by design. Kafka has no built-in alert for a dead cleaner thread. Without cleaner-specific JMX metrics, the first sign is a disk space ticket or a broker taking its log directory offline.</p>Kafka Log directory failed / OfflineLogDirectoryCount > 0: disk errors and JBOD recoveryhttps://www.netdata.cloud/guides/kafka/kafka-log-directory-failed-offline/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-log-directory-failed-offline/<h2 id="what-this-means">What this means</h2> <p>When Kafka catches an IOException on a <code>log.dirs</code> path, it marks that log directory offline. The broker increments <code>kafka.log:type=LogManager,name=OfflineLogDirectoryCount</code> and logs the failure. Partitions with replicas on the failed directory lose those replicas. If the partition leader was on that directory and <code>unclean.leader.election.enable=false</code>, the partition becomes unavailable until the controller elects a new leader from the remaining ISR. Producers with <code>acks=all</code> see <code>NotEnoughReplicasException</code> when the surviving ISR drops below <code>min.insync.replicas</code>.</p>Kafka min.insync.replicas and acks: configuring durability you actually havehttps://www.netdata.cloud/guides/kafka/kafka-min-insync-replicas-misconfigured/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-min-insync-replicas-misconfigured/<p>Most operators set producers to <code>acks=all</code> and assume the cluster acks only when every replica has the message. It does not. With <code>acks=all</code>, the broker waits only for the current in-sync replica set (ISR). Because the ISR shrinks dynamically when followers lag, a partition with replication factor three can have an ISR of one &ndash; the leader itself. Without raising <code>min.insync.replicas</code> from its default, the leader acks with zero followers caught up. Your durability guarantee collapses to leader-only persistence, and you only find out when the leader dies and data is missing.</p>Kafka Monitoringhttps://www.netdata.cloud/monitoring-101/kafka-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/kafka-monitoring/<h2 id="kafka-monitoring">Kafka Monitoring</h2> <h3 id="what-is-kafka">What Is Kafka?</h3> <p>Apache Kafka is a distributed event streaming platform capable of handling trillions of events a day. It is used by thousands of companies for streaming analytics, data integration, and data pipelines. As a <strong>message broker</strong>, Kafka is crucial for managing big data and ensuring real-time data streaming operations. Monitoring Kafka is vital to ensure that it operates efficiently and to prevent costly downtime or data loss.</p>Kafka monitoring checklist: the signals every production cluster needshttps://www.netdata.cloud/guides/kafka/kafka-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-monitoring-checklist/<p>Kafka failures follow predictable paths: an ISR shrinks, a controller queue backs up, a disk fills while the cleaner thread hangs, or a consumer rebalance storm hides behind healthy broker metrics. You need to know which signals matter and when they justify a 3 AM page.</p> <p>This checklist organizes broker-side signals into four levels. Each builds on the last: Level 1 prevents data loss. Level 2 prevents surprises. Level 3 exposes leading indicators. Level 4 catches silent killers. Use it to audit dashboards, tune alert severity, and justify instrumentation.</p>Kafka NetworkProcessorAvgIdlePercent low: network thread saturation and TLS overheadhttps://www.netdata.cloud/guides/kafka/kafka-network-processor-idle-percent-low/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-network-processor-idle-percent-low/<p>NetworkProcessorAvgIdlePercent drops on one or more brokers. A ticket may fire when the value falls below 0.3, or producers and consumers may timeout while broker CPU looks fine and I/O threads are not obviously saturated. Network thread saturation blocks all socket activity, including metadata requests, so every client suffers. With the default num.network.threads set to 3, brokers running TLS and dense client pools are especially vulnerable. Sustained values below 0.1 make the broker effectively unreachable even though the process is still running.</p>Kafka NOT_LEADER_FOR_PARTITION: stale metadata, controller lag, and client retrieshttps://www.netdata.cloud/guides/kafka/kafka-not-leader-for-partition/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-not-leader-for-partition/<p>Producers and consumers log <code>NOT_LEADER_FOR_PARTITION</code>. Broker response metrics show spikes in failed produce or fetch requests. The cluster usually self-heals within seconds as clients refresh metadata. When the error persists for minutes, or flaps across many partitions, the root cause is typically a controller that cannot keep up with leadership changes. Distinguishing a routine leader election from a controller queue backup that blocks metadata propagation is the first step.</p> <h2 id="what-this-means">What this means</h2> <p>Kafka clients cache partition leadership metadata. When a leader moves (rolling restart, broker failure, preferred replica election), a client with a stale view sends requests to the previous leader. That broker returns <code>NOT_LEADER_FOR_PARTITION</code>. The Java client treats this as a retriable error and refreshes metadata eagerly. A short spike during a restart is normal and usually clears immediately.</p>Kafka NotEnoughReplicasException: acks=all writes rejected below min.insync.replicashttps://www.netdata.cloud/guides/kafka/kafka-not-enough-replicas-exception/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-not-enough-replicas-exception/<p>Producers are throwing <code>org.apache.kafka.common.errors.NotEnoughReplicasException</code> or <code>NotEnoughReplicasAfterAppendException</code>, and <code>acks=all</code> writes are failing while <code>acks=1</code> or <code>acks=0</code> writes may still succeed. The affected partitions no longer have enough in-sync replicas to satisfy <code>min.insync.replicas</code>. The immediate operational question is whether the ISR shrink is a transient recovery blip or a sustained degradation that will block writes until you fix the follower.</p> <h2 id="what-this-means">What this means</h2> <p>The leader tracks followers caught up within <code>replica.lag.time.max.ms</code> (default 30s, changed from 10s in Kafka 2.5.0) in the In-Sync Replica set (ISR). For <code>acks=all</code>, the leader waits for all current ISR members before acknowledging the producer. If the ISR size drops below <code>min.insync.replicas</code>, the leader rejects the produce request. The broker-level default for <code>min.insync.replicas</code> is 1, so a lone leader can acknowledge alone. In practice, with <code>replication.factor=3</code> and <code>acks=all</code>, set <code>min.insync.replicas=2</code> so a single follower loss blocks writes instead of silently weakening durability.</p>Kafka OfflinePartitionsCount > 0: partitions with no leader and how to recoverhttps://www.netdata.cloud/guides/kafka/kafka-offline-partitions-count/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-offline-partitions-count/<p>When <code>kafka.controller:type=KafkaController,name=OfflinePartitionsCount</code> is nonzero, at least one partition has no active leader. Those partitions are completely unavailable: producers receive errors, consumers stall, and no data is written or read until a leader is elected. This is a data-plane outage.</p> <p>This metric is only meaningful on the active controller. Non-controller brokers always report zero. If the controller itself is down, the metric may be stale or unreachable at the exact moment you need it. Brief spikes can occur during controller re-election or ungraceful broker shutdown, but any sustained nonzero value past 60 seconds is an active incident that requires immediate intervention.</p>Kafka OffsetOutOfRangeException: when retention deletes data before the consumer reads ithttps://www.netdata.cloud/guides/kafka/kafka-offset-out-of-range-exception/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-offset-out-of-range-exception/<p><code>OffsetOutOfRangeException</code> means the consumer requested an offset the broker no longer holds. The log segment containing the consumer&rsquo;s committed position was deleted by retention before the consumer caught up. This is not a transient fetch error; it is data loss, and the outcome depends entirely on <code>auto.offset.reset</code>. Many clients default to <code>latest</code>, which turns this exception into silent skipping.</p> <p>This is a lag problem wearing a fetch error. The consumer was too slow, paused too long, or was offline longer than the topic&rsquo;s <code>retention.ms</code>. Once the log start offset moves past the committed offset, every subsequent fetch fails.</p>Kafka RecordTooLargeException / MESSAGE_TOO_LARGE: message size limits across the pathhttps://www.netdata.cloud/guides/kafka/kafka-message-too-large-error/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-message-too-large-error/<p>Two errors surface: the producer client throws <code>RecordTooLargeException</code> before the request hits the wire, or the broker returns <code>MESSAGE_TOO_LARGE</code> in the produce response. Both mean a record batch exceeds a limit somewhere in the path, but the fix depends on exactly which limit and where the size is measured. These settings are not a single knob: <code>max.request.size</code>, <code>message.max.bytes</code>, <code>max.message.bytes</code>, <code>replica.fetch.max.bytes</code>, <code>fetch.max.bytes</code>, <code>max.partition.fetch.bytes</code>, and <code>socket.request.max.bytes</code> must all align. Raise one limit without raising the others and you will wedge replication, strand consumers, or silently lose data on the next large message.</p>Kafka replica MaxLag growing: slow followers and replica fetcher healthhttps://www.netdata.cloud/guides/kafka/kafka-replica-fetcher-max-lag/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-replica-fetcher-max-lag/<p>When <code>kafka.server:type=ReplicaFetcherManager,name=MaxLag,clientId=Replica</code> climbs on a broker, the worst follower is failing to replicate fast enough. This metric is the maximum offset distance between a leader and its most lagging follower. In a healthy cluster it stays near zero. If the gap persists longer than <code>replica.lag.time.max.ms</code>, the leader removes the follower from the ISR. Once enough replicas drop, partitions can fall below <code>min.insync.replicas</code>, and producers using <code>acks=all</code> hit <code>NotEnoughReplicasException</code>.</p> <p>This guide separates follower-side, network, and leader-side bottlenecks, and stops the lag before it forces a full rebuild.</p>Kafka REQUEST_TIMED_OUT: produce requests that expire before replication completeshttps://www.netdata.cloud/guides/kafka/kafka-request-timed-out-error/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-request-timed-out-error/<p>Producers using <code>acks=all</code> throw <code>TimeoutException</code> (error code <code>REQUEST_TIMED_OUT</code>) when the broker accepts a produce request but cannot complete replication before <code>request.timeout.ms</code> expires. The leader appends the record to its local log and waits in purgatory for acknowledgments from all in-sync replicas. If the ISR ack does not arrive before the client deadline, the request expires client-side and the producer surfaces the error. The broker may still finish the write, but the producer has already moved on, creating a hidden replication backlog and a potential retry storm.</p>Kafka Too many open files: file descriptor exhaustion from segments and connectionshttps://www.netdata.cloud/guides/kafka/kafka-too-many-open-files/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-too-many-open-files/<p>Producers time out, consumers disconnect, and the broker log shows <code>java.io.IOException: Too many open files</code>. The broker may still run, but it cannot open new log segments or accept additional TCP connections. File descriptor exhaustion is a cliff-edge failure: the broker operates normally until it hits the hard limit, then the data path stops.</p> <p>Kafka brokers hold a file descriptor for every log segment and every network connection. Each partition maintains an active segment and older retained segments. A broker with thousands of partitions and tens of segments each, plus hundreds of client connections, can hold tens of thousands of open file descriptors. The default Linux per-process limit of 1024 is far below production requirements.</p>Kafka UncleanLeaderElectionsPerSec > 0: confirmed silent data losshttps://www.netdata.cloud/guides/kafka/kafka-unclean-leader-election/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-unclean-leader-election/<p>Your <code>UncleanLeaderElectionsPerSec</code> alert fired. The JMX metric <code>kafka.controller:type=ControllerStats,name=UncleanLeaderElectionsPerSec</code> shows <code>OneMinuteRate &gt; 0</code>, or <code>Count</code> has incremented since your last check. This is confirmed data loss: a partition leader was elected from outside the ISR, and acknowledged records that the new leader does not possess are silently truncated.</p> <p>Producers that received acks for those records were given a durability guarantee the cluster just broke. Stop additional loss, understand scope, and fix the conditions that allowed it.</p>Kafka UnderMinIsrPartitionCount: confirming the write path is blockedhttps://www.netdata.cloud/guides/kafka/kafka-under-min-isr-partition-count/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-under-min-isr-partition-count/<p><code>UnderMinIsrPartitionCount</code> is the Kafka metric that confirms active write-path impact. When <code>UnderReplicatedPartitions</code> (URP) is nonzero, the cluster&rsquo;s durability window is open but writes may still be succeeding. When <code>UnderMinIsrPartitionCount</code> is nonzero, producers using <code>acks=all</code> are actively receiving <code>NotEnoughReplicasException</code> and their produce requests are being rejected at the broker.</p> <p>This distinction matters for alerting. URP fires constantly during normal operations: rolling restarts, partition reassignment, transient GC pauses, brief network blips. Most of these are not worth paging someone at 3 a.m. <code>UnderMinIsrPartitionCount</code> only fires when ISR membership has dropped below <code>min.insync.replicas</code>, meaning the write durability guarantee you configured cannot be met. That is direct, measurable user impact.</p>Kafka UnderReplicatedPartitions > 0: the most important metric and how to clear ithttps://www.netdata.cloud/guides/kafka/kafka-under-replicated-partitions/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kafka/kafka-under-replicated-partitions/<p>UnderReplicatedPartitions climbing above zero means a follower has fallen behind, the ISR has shrunk, and the cluster&rsquo;s durability guarantee is degraded. One more failure on the wrong broker could make partitions unavailable or cause <code>acks=all</code> writes to be rejected. Determine whether this is a transient blip from maintenance or the start of a cascading replication failure.</p> <h2 id="what-this-means">What this means</h2> <p>The JMX MBean <code>kafka.server:type=ReplicaManager,name=UnderReplicatedPartitions</code> reports the number of partitions where this broker is the leader and the ISR count is below the configured replication factor. It is a per-broker gauge. A broker without leadership always reports zero, even when the cluster is degraded, so aggregate across all brokers to see the full picture.</p>Kafka ZooKeeper Monitoringhttps://www.netdata.cloud/monitoring-101/kafka_zookeeper-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/kafka_zookeeper-monitoring/<h2 id="kafka-zookeeper-monitoring">Kafka ZooKeeper Monitoring</h2> <h3 id="what-is-kafka-zookeeper">What Is Kafka ZooKeeper?</h3> <p>Kafka ZooKeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. It is a critical component in the architecture of distributed systems, especially for managing and coordinating services like Apache Kafka.</p> <h3 id="monitoring-kafka-zookeeper-with-netdata">Monitoring Kafka ZooKeeper With Netdata</h3> <p>Monitoring Kafka ZooKeeper with Netdata offers a comprehensive view of the system’s performance and health. To monitor Kafka ZooKeeper, Netdata uses an openmetrics (Prometheus) exporter called the <a href="https://github.com/cloudflare/kafka_zookeeper_exporter">Kafka ZooKeeper Exporter</a>. This allows Netdata to ingest data from any Prometheus exporter efficiently. With Netdata, you get automated dashboards, alerts, and more without the need for a Prometheus server or Grafana. This streamlined approach with the Netdata $name monitoring tool ensures ease of use and rapid insights into your Kafka ZooKeeper instances.</p>Kannel Monitoringhttps://www.netdata.cloud/monitoring-101/kannel-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/kannel-monitoring/<h2 id="kannel-monitoring">Kannel Monitoring</h2> <h3 id="what-is-kannel">What Is Kannel?</h3> <p>Kannel is an open-source WAP and SMS gateway used widely for mobile communication gateways. It enables applications to send and receive SMS messages and connect to mobile network carriers. Given its crucial role in mobile communication, oversight of its operational metrics is paramount.</p> <h3 id="monitoring-kannel-with-netdata">Monitoring Kannel With Netdata</h3> <p>To effectively monitor Kannel, Netdata offers an intuitive solution that employs an openmetrics (Prometheus) exporter. This integration does not require a standalone Prometheus server or Grafana setup. Netdata strives as a comprehensive Kannel monitoring tool by allowing users to visualize data in real time with automated dashboards and alerts across various metrics provided by any compatible Prometheus exporter. To get started, you can use the <a href="https://github.com/apostvav/kannel_exporter">Kannel Exporter</a>.</p>Keepalived Monitoringhttps://www.netdata.cloud/monitoring-101/keepalived-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/keepalived-monitoring/<h2 id="keepalived-monitoring">Keepalived Monitoring</h2> <h3 id="what-is-keepalived">What Is Keepalived?</h3> <p>Keepalived is a robust software used primarily for high-availability and load-balancing on Linux systems. It leverages VRRP (Virtual Router Redundancy Protocol) to increase network uptime by offering failover protocols. By monitoring network interfaces, Keepalived helps in ensuring that servers are capable of handling traffic efficiently.</p> <h3 id="monitoring-keepalived-with-netdata">Monitoring Keepalived With Netdata</h3> <p>Monitoring Keepalived with Netdata is a seamless process that ensures you have real-time insights into the performance and availability of your network infrastructure. Netdata uses an <strong>openmetrics (Prometheus) exporter</strong> to retrieve Keepalived metrics. This means that, to monitor Keepalived, Netdata can accept data from any Prometheus exporter, allowing you to benefit from automated dashboards and alerts without needing a dedicated Prometheus server or Grafana. This integration allows for comprehensive monitoring of Keepalived metrics, ensuring your high-availability setup runs smoothly.</p>Kernel Same-page Merging (KSM) Monitoringhttps://www.netdata.cloud/monitoring-101/ksm-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/ksm-monitoring/<h2 id="kernel-same-page-merging-ksm">Kernel Same-page Merging (KSM)?</h2> <p>Linux kernels store memory in <strong>pages</strong> which are moved in and out of memory as a single block. On most Linux architectures pages are 4096 bytes. <strong>KSM</strong> (Kernel Same-page Merging) is a kernel feature that scans memory looking for pages with identical content, and then de-duplicates them. The most common use-case where such duplicate pages occur is on hosts running multiple virtual machines (VMs).</p> <p>KSM can greatly reduce the amount of memory used by VMs. When it finds two or more identical pages, it replaces them with a single page that is shared by all VMs that are using it.</p>Kube-proxy Monitoringhttps://www.netdata.cloud/monitoring-101/kubeproxy-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/kubeproxy-monitoring/<h2 id="what-is-kube-proxy">What is Kube-proxy?</h2> <p><a href="https://kubernetes.io/docs/concepts/architecture/#kube-proxy"><code>Kube-proxy</code></a> is a network proxy that runs on each node in your cluster, implementing part of the Kubernetes Service.</p> <h2 id="monitoring-kube-proxy-with-netdata">Monitoring Kube-proxy with Netdata</h2> <p>The prerequisites for monitoring Kube-proxy with Netdata are to have Kube-proxy and <a href="https://learn.netdata.cloud/docs/cloud/get-started/">Netdata installed</a> on your system.</p> <p>Netdata auto discovers hundreds of services, and for those it doesn&rsquo;t turning on manual discovery is a one line configuration. For more information on configuring Netdata for Kube-proxy monitoring please read the collector <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/k8s_kubeproxy/">documentation</a>.</p>Kubelet Monitoringhttps://www.netdata.cloud/monitoring-101/k8s_kubelet-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/k8s_kubelet-monitoring/<h2 id="kubelet-monitoring">Kubelet Monitoring</h2> <p>In today&rsquo;s fast-paced DevOps environments, monitoring the <a href="https://kubernetes.io/docs/concepts/architecture/#kubelet">Kubelet</a> effectively is crucial for maintaining healthy Kubernetes clusters. Understanding its metrics allows teams to ensure high availability and performance efficiency for their applications.</p> <h3 id="what-is-kubelet">What Is Kubelet?</h3> <p>Kubelet is a core component of Kubernetes that runs on each node in the cluster. It ensures that containers are running as expected, watching for changes in Pod specifications and reporting back to the Kubernetes API server.</p>Kubeproxy Monitoringhttps://www.netdata.cloud/monitoring-101/k8s_kubeproxy-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/k8s_kubeproxy-monitoring/<h2 id="kubeproxy-monitoring">Kubeproxy Monitoring</h2> <h3 id="what-is-kubeproxy">What Is Kubeproxy?</h3> <p>Kubeproxy is a critical component of the Kubernetes ecosystem, acting as a network proxy that runs on each node in your cluster. It manages the IP table rules and forwards traffic to correct Pod IP addresses, playing a vital role in facilitating seamless communication within your Kubernetes deployment. Its efficient operation is crucial to maintaining healthy network traffic in Kubernetes environments.</p> <h3 id="monitoring-kubeproxy-with-netdata">Monitoring Kubeproxy With Netdata</h3> <p>Netdata provides a comprehensive Kubernetes monitoring tool that allows you to monitor Kubeproxy in real-time. By harnessing the <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/k8s_kubeproxy/">Kubeproxy collector</a>, you can gather pivotal metrics that give insights into your cluster&rsquo;s network performance. These metrics help in diagnosing issues swiftly and ensuring optimal Kubeproxy operations. You can even <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">check out the live demo here</a> to see these monitoring capabilities in action.</p>Kubernetes API Server etcd Latency: How To Fix Ithttps://www.netdata.cloud/guides/kubernetes/kubernetes-api-server-etcd-latency/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-api-server-etcd-latency/<p>When etcd slows down, the entire control plane slows with it. A few extra milliseconds on disk fsync turns into hung kubectl commands, backed-up controller queues, and eventually a cluster that cannot schedule pods or update endpoints. Detect the etcd latency cascade, confirm whether storage is the root cause, and break the feedback loop before the cluster becomes effectively read-only.</p> <h2 id="what-this-means">What This Means</h2> <p>etcd serializes every Kubernetes mutation. Every API server write becomes a Raft proposal that must fsync to the WAL before etcd acknowledges it. When the disk under etcd is slow, every fsync waits longer. The API server holds mutating requests open until etcd responds. Requests pile up in the inflight queue. Once the queue hits the limit, the API server returns 429 Too Many Requests. Controllers that depend on writes (scheduler, replica set controller, and others) fall behind and retry. Retries generate more write load. The result is a feedback loop: slow disk -&gt; slow etcd -&gt; slow API server -&gt; retry storm -&gt; amplified etcd load.</p>Kubernetes API Server Rate Limited: How To Fix Ithttps://www.netdata.cloud/guides/kubernetes/kubernetes-api-server-rate-limited/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-api-server-rate-limited/<p>Your API server is running. <code>/healthz</code> returns 200. <code>/readyz</code> passes. Yet nodes drop to <code>NotReady</code>, the scheduler stops placing pods, and controller logs fill with <code>context deadline exceeded</code>. The cluster is not down, but it is frozen. This pattern often points to API Priority and Fairness (APF) starvation: low-priority traffic consumes the API server&rsquo;s concurrency budget, and critical control plane requests queue or get rejected.</p> <p>APF is enabled by default in Kubernetes 1.20+. It classifies every API request into a priority level via FlowSchema rules, then schedules requests against a per-level concurrency limit. When a priority level exhausts its seats, requests queue. If the queue fills, the server returns HTTP 429. When the queue grows in <code>system</code> or <code>leader-election</code>, kubelets cannot renew leases, controllers cannot write status, and the cluster degrades from the inside out. This guide shows how to confirm APF starvation, identify the culprit, and fix the allocation without turning the API server into a free-for-all.</p>Kubernetes API Server Slow Or Unresponsive: Causes & Fixeshttps://www.netdata.cloud/guides/kubernetes/kubernetes-api-server-slow/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-api-server-slow/<p>When <code>kubectl</code> hangs, controllers log <code>context deadline exceeded</code>, and deployments stall, the Kubernetes API server is usually the bottleneck. It is the single funnel for every read and write to cluster state. Slowness propagates to scheduling, pod lifecycle, service discovery, and external automation.</p> <p>This article covers operational causes and gives a step-by-step diagnostic flow to run during an incident. Use it to distinguish etcd latency, <a >admission webhook</a> stalls, request saturation, and memory pressure.</p>Kubernetes Cluster State Monitoringhttps://www.netdata.cloud/monitoring-101/k8s_state-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/k8s_state-monitoring/<h2 id="kubernetes-cluster-state-monitoring">Kubernetes Cluster State Monitoring</h2> <h3 id="what-is-kubernetes-cluster-state">What Is Kubernetes Cluster State?</h3> <p>Kubernetes Cluster State refers to the real-time condition or the status of your Kubernetes cluster, including nodes, pods, and containers. Monitoring these elements ensures that your clusters are operating at optimal capacity and helps in rapidly identifying any discrepancies or issues.</p> <h3 id="monitoring-kubernetes-cluster-state-with-netdata">Monitoring Kubernetes Cluster State With Netdata</h3> <p>Netdata provides a comprehensive Kubernetes Cluster State monitoring tool that allows you to effortlessly oversee node and pod metrics. The integration with the go.d.plugin module makes it simple for you to garner insights into the dynamic environment of Kubernetes.</p>Kubernetes conntrack exhaustion: dropped connections under loadhttps://www.netdata.cloud/guides/kubernetes/kubernetes-conntrack-exhaustion/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-conntrack-exhaustion/<p>Intermittent connection timeouts under load in Kubernetes often trace to a full nf_conntrack table on the node. Existing TCP sessions stay open, but new connections fail silently. DNS resolution becomes unreliable. Application logs show timeouts to healthy dependencies. The root cause is usually not the application, network policy, or CNI, but kernel connection tracking exhaustion.</p> <p>Every connection that traverses kube-proxy NAT rules creates an entry in the node&rsquo;s nf_conntrack table. This finite, node-level table is shared by all workloads and invisible to most application monitoring. When it fills, the kernel drops new connection attempts without sending a TCP reset or ICMP error. The application sees a timeout.</p>Kubernetes Controller-Manager Leader Election Failureshttps://www.netdata.cloud/guides/kubernetes/kubernetes-controller-manager-leader-election/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-controller-manager-leader-election/<p>Your Deployment has stopped scaling. Nodes cordoned hours ago are still draining. Garbage collection is paused, and orphaned volumes are not being cleaned up. The kube-controller-manager runs these reconciliation loops, and in an HA cluster only the leader performs work. When leader election fails, the controller-manager exits, and the control plane stops acting on desired state. Existing workloads keep running, but nothing new is managed.</p> <p>The kube-controller-manager coordinates through a Lease object in the <code>coordination.k8s.io</code> API group. The leader must renew the lease before <code>--leader-elect-renew-deadline</code> (default 10 seconds) elapses. The lease itself expires after <code>--leader-elect-lease-duration</code> (default 15 seconds). Renewal is attempted every <code>--leader-elect-retry-period</code> (default 2 seconds). If a write to etcd is too slow, if the API server is saturated, if RBAC is stripped, or if the election timing is misconfigured, the leader loses the lock, logs <code>leaderelection lost</code>, and exits. During the gap, no instance holds a valid lease, so controllers stop reconciling.</p>Kubernetes DNS resolution failures inside podshttps://www.netdata.cloud/guides/kubernetes/kubernetes-dns-failures/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-dns-failures/<p>DNS failures inside pods break service discovery. A single overloaded CoreDNS replica or saturated conntrack table on one node can look like a multi-service outage. Before fixing, determine whether the failure is cluster-wide, node-specific, or workload-specific.</p> <h2 id="what-this-means">What this means</h2> <p>Kubernetes injects an <code>/etc/resolv.conf</code> into every pod that points to the cluster DNS service, typically CoreDNS. CoreDNS resolves cluster-internal names via the kubernetes plugin and forwards external queries to an upstream resolver. A failure at any point produces the same symptom: the name cannot be resolved.</p>Kubernetes eviction cascade: when one node failure takes down the clusterhttps://www.netdata.cloud/guides/kubernetes/kubernetes-eviction-cascade/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-eviction-cascade/<p>You see pods entering Evicted status across multiple nodes. Nodes flap between Ready and MemoryPressure or DiskPressure. The scheduler keeps placing replacements, but the new pods are evicted again before they become ready. Workloads never stabilize, and every remediation attempt seems to make the cluster more volatile.</p> <p>This is a node-pressure eviction cascade. It happens when the scheduler&rsquo;s view of capacity diverges from the kubelet&rsquo;s view. One node under pressure evicts pods; those pods land on other nodes that are also overcommitted; those nodes tip into pressure and evict more pods. The result is a cluster-wide feedback loop that looks like a resource shortage but is often a scheduling and configuration problem.</p>Kubernetes kube-proxy iptables sync stall: causes and recoveryhttps://www.netdata.cloud/guides/kubernetes/kubernetes-iptables-sync-stall/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-iptables-sync-stall/<p>Pods fail to start. Services intermittently route traffic to dead endpoints. The kube-proxy health endpoint still returns HTTP 200, so the DaemonSet looks healthy, yet rules drift further behind with every sync cycle.</p> <p>An iptables sync stall is not a crash. It is a slowdown or blockage in the control loop that translates Service and EndpointSlice state into kernel NAT rules. When kube-proxy cannot acquire the global xtables lock, when <code>iptables-restore</code> hangs, or when the rule set grows too large to reconcile within the sync period, the node forwards packets using stale rules. New endpoints are invisible. Terminated pods still receive connections. CNI plugins that also need the xtables lock time out, and pod sandbox creation fails.</p>Kubernetes kube-proxy IPVS: stale rules and session affinity issueshttps://www.netdata.cloud/guides/kubernetes/kubernetes-ipvs-stale-rules/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-ipvs-stale-rules/<p>DNS queries start timing out from one node after a CoreDNS rolling update. A UDP Service returns timeouts for some clients but not others. New Services are unreachable from a specific node while older Services continue to work.</p> <p>In IPVS mode, kube-proxy programs the kernel&rsquo;s IPVS table with virtual servers and real servers. The IPVS connection table lives outside kube-proxy&rsquo;s direct control and outside nf_conntrack. That separation creates two IPVS-specific failure modes: stale rules that diverge from EndpointSlice state, and UDP session affinity that sticks to dead backends long after a pod terminates.</p>Kubernetes kubelet certificate expired: detection, rotation, and recoveryhttps://www.netdata.cloud/guides/kubernetes/kubernetes-kubelet-certificate-expired/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-kubelet-certificate-expired/<p>A healthy node suddenly shows NotReady. Pods keep running, but the kubelet stops reporting status. <code>kubectl logs</code> and <code>kubectl exec</code> fail with TLS errors. The cluster event stream is quiet. This is usually an expired kubelet client certificate that failed to rotate.</p> <p>Every kubelet maintains two independent TLS credentials: a client certificate that authenticates it to the kube-apiserver, and a serving certificate that secures the kubelet&rsquo;s own HTTPS endpoints. Both typically have a one-year validity. When the client certificate expires, the kubelet cannot authenticate to the API server. The node goes NotReady. Workloads may continue running, but they are unmanaged: no evictions, no probe execution, no status updates, and no new pod scheduling. When the serving certificate expires, metrics-server, <code>kubectl exec</code>, and <code>kubectl logs</code> break even if the node is otherwise Ready.</p>Kubernetes kubelet memory leak: detection and OOM cyclehttps://www.netdata.cloud/guides/kubernetes/kubernetes-kubelet-memory-leak/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-kubelet-memory-leak/<p>Kubelet memory growth ends one of two ways: the process hits its cgroup limit or the node runs out of memory. The kernel OOM killer sends SIGKILL. Systemd restarts kubelet, but the new process has cold caches and immediately runs a full reconciliation pass: relisting all containers, re-syncing every pod status, and re-attaching every volume. On a busy node, that burst spikes CPU and memory, which can push the fresh kubelet back over the edge and create a Ready/NotReady flap cycle.</p>Kubernetes kubelet not responding: PLEG, runtime, and certificate issueshttps://www.netdata.cloud/guides/kubernetes/kubernetes-kubelet-not-responding/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-kubelet-not-responding/<p><a href="https://www.netdata.cloud/guides/kubernetes/">A Kubernetes node</a> flipping to NotReady while containers keep running is one of the most confusing production failure modes. The kubelet is the node agent that reconciles API server intent with running containers. When it stops responding or reports unhealthy subsystems, the control plane marks the node NotReady and reschedules workloads, even though the data plane may still serve traffic.</p> <p>This guide covers three failure domains: Pod Lifecycle Event Generator (PLEG) stalls, container runtime disconnections, and kubelet certificate expiration or rotation failures. Distinguish these symptoms, run safe targeted diagnostics, and apply fixes without blind node reboots.</p>Kubernetes Monitoring Checklist: The Signals Every Production Cluster Needshttps://www.netdata.cloud/guides/kubernetes/kubernetes-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-monitoring-checklist/<p>This article is a reference checklist for senior engineers who are wiring up, auditing, or hardening monitoring for a production Kubernetes cluster. It assumes you already understand the control plane architecture and focuses on what to collect, where to find it, and which symptoms matter. Use it during greenfield instrumentation, post-incident gap analysis, or routine health audits.</p> <p>The signals are grouped by domain. Each entry leads with a short noun phrase, followed by one sentence explaining why it matters, and a concrete warning sign to alert on. Thresholds are drawn from upstream SLOs, kubelet defaults, and etcd operational limits documented in the Kubernetes source and production playbooks. If you run a managed service such as EKS, GKE, or AKS, treat control-plane metrics as provider-mediated; many etcd and API server internals are opaque in those environments.</p>Kubernetes node CPU saturation: load, throttling, and runqueue depthhttps://www.netdata.cloud/guides/kubernetes/kubernetes-node-cpu-saturation/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-node-cpu-saturation/<p>Application latency climbs and pods slow down. <code>kubectl top nodes</code> reports 70 percent CPU, so you assume headroom exists. It does not. CPU percent is a time-average that masks micro-bursts, runqueue backlog, and CFS throttling. A container can throttle to a crawl while node utilization looks comfortable, and a node can show 50 percent utilization with every runnable thread queued behind a noisy neighbor. Distinguish node-level CPU contention from limit-induced throttling using runqueue depth, CFS bandwidth metrics, and Pressure Stall Information (PSI).</p>Kubernetes node DiskPressure: detection, eviction, and recoveryhttps://www.netdata.cloud/guides/kubernetes/kubernetes-node-disk-pressure/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-node-disk-pressure/<p>A node reporting DiskPressure is actively shedding workloads. The kubelet has detected that nodefs or imagefs has crossed an eviction threshold. It is garbage collecting images, terminating pods, and applying the <code>node.kubernetes.io/disk-pressure</code> taint to block new scheduling. Existing pods may continue running, but any pod requiring disk for logs, emptyDir volumes, or image pulls is at risk.</p> <p>Disk pressure builds predictably, unlike memory pressure. This guide covers how the kubelet evaluates disk pressure, how to distinguish nodefs from imagefs exhaustion, how to find the specific consumer, and how to recover without causing a cascading eviction loop.</p>Kubernetes node MemoryPressure: detection, eviction order, and preventionhttps://www.netdata.cloud/guides/kubernetes/kubernetes-node-memory-pressure/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-node-memory-pressure/<p>Before adding RAM, determine whether kubelet is evicting because workloads are genuinely starving or because memory requests are misaligned with reality.</p> <h2 id="what-this-means">What this means</h2> <p>Kubelet evaluates <code>memory.available</code> against an eviction threshold. On Linux the default hard threshold is <code>memory.available &lt; 100Mi</code>. Kubelet derives this from cgroup stats, not <code>free -m</code>. It measures working-set memory (RSS plus active file-backed pages) and subtracts that from total capacity. When the threshold is crossed, kubelet sets the node condition <code>MemoryPressure=True</code>; the control plane maps that condition to the <code>node.kubernetes.io/memory-pressure:NoSchedule</code> taint. New pods are blocked from scheduling until the condition clears.</p>Kubernetes node NotReady: kubelet, runtime, and network diagnosishttps://www.netdata.cloud/guides/kubernetes/kubernetes-node-not-ready/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-node-not-ready/<p>When <a href="https://www.netdata.cloud/guides/kubernetes/">a Kubernetes node</a> becomes NotReady, existing containers usually keep running, but the cluster stops scheduling new pods, removes endpoints from Services, and eventually evicts workloads after the pod eviction timeout. Root causes fall into three domains: kubelet health, container runtime responsiveness, and CNI or control plane connectivity.</p> <h2 id="what-this-means">What This Means</h2> <p>Kubernetes marks a node NotReady when the kubelet Ready condition is False, or when the node controller has not received a heartbeat within <code>--node-monitor-grace-period</code> (default 50 seconds since Kubernetes 1.32; 40 seconds before). The node receives the <code>node.kubernetes.io/not-ready:NoSchedule</code> taint. If the condition persists longer than the pod eviction timeout (default 5 minutes), the controller manager marks pods on the node for rescheduling.</p>Kubernetes node PIDPressure: detection and remediationhttps://www.netdata.cloud/guides/kubernetes/kubernetes-node-pid-pressure/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-node-pid-pressure/<p>PID exhaustion is a cliff-edge failure: once the kernel cannot fork, containers fail to start, health checks fail, and ssh to the node may hang. Kubernetes surfaces this through the PIDPressure node condition, but many clusters ship without PID-based eviction thresholds. Without them, the first symptom is usually <code>EAGAIN</code> or <code>ENOMEM</code> from fork failures, not a kubelet eviction.</p> <p>This guide shows how to detect PIDPressure before it triggers an outage, distinguish between application leaks, runtime shim accumulation, and kernel limits, and remediate the root cause. You will correlate node-level PID utilization with specific pods, validate kubelet cgroup enforcement, and configure thresholds that provide lead time.</p>Kubernetes PLEG is not healthy: runtime stalls and node degradationhttps://www.netdata.cloud/guides/kubernetes/kubernetes-pleg-not-healthy/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-pleg-not-healthy/<p>A node suddenly flips to NotReady with the message &ldquo;PLEG is not healthy.&rdquo; Containers on the node keep running, but the control plane evicts workloads and reschedules them elsewhere. New pods cannot start, and existing pods run without health checks or status updates. This is one of the most common kubelet failure modes in production.</p> <p>The Pod Lifecycle Event Generator (PLEG) is the kubelet subsystem that polls the container runtime every second and emits events when containers start, stop, or change state. When the runtime becomes slow or unresponsive, the PLEG relist loop stalls. If the elapsed time since the last successful relist exceeds three minutes, kubelet declares PLEG unhealthy, marks the node NotReady, and skips pod synchronization.</p>Kubernetes pod CrashLoopBackOff: causes, diagnosis, and fixeshttps://www.netdata.cloud/guides/kubernetes/kubernetes-pod-crashloopbackoff/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-pod-crashloopbackoff/<p>CrashLoopBackOff means a container in a Pod has terminated after starting, and the kubelet is delaying the next restart with exponential backoff. The status describes behavior, not root cause. Underlying failures include application panics, OOM kills, misconfigured liveness probes, missing secrets, or node-level resource pressure.</p> <p>Use pod status, previous container logs, node conditions, and kubelet events to narrow the cause. Monitor restart rate, node pressure, and probe failures to catch loops before they degrade capacity.</p>Kubernetes pod creation fails: admission, quota, and CRI errorshttps://www.netdata.cloud/guides/kubernetes/kubernetes-pod-creation-fails/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-pod-creation-fails/<p>Pre-scheduling failures happen when the API server or container runtime rejects a Pod before the scheduler assigns it. You apply a Deployment, but <code>kubectl get pods</code> returns nothing. Or a Pod hangs in <code>ImagePullBackOff</code> before <code>ContainerCreating</code>. These cases surface as missing Pods, <code>FailedCreate</code> events on ReplicaSets or Jobs, or explicit API rejections. This guide covers admission control, quota and policy limits, and CRI-level image pull and sandbox failures.</p> <h2 id="what-this-means">What this means</h2> <p>Pod creation is a pipeline. The API server first authenticates and authorizes the request, then runs the Pod spec through admission controllers: mutating webhooks, validating webhooks, LimitRanger, ResourceQuota, and PodSecurity. If any controller rejects the request, the Pod object is never persisted to etcd. If admission succeeds, the object is stored, the scheduler assigns a node, and the kubelet asks the container runtime (via CRI) to create the pod sandbox and pull images. Failures in this guide happen before the pod is running or scheduled.</p>Kubernetes pod Evicted: detection, root cause, and preventionhttps://www.netdata.cloud/guides/kubernetes/kubernetes-pod-evicted/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-pod-evicted/<p>Pods with status <code>Evicted</code> are not application crashes. They are the kubelet&rsquo;s emergency response to node-level resource pressure. When memory, disk, inodes, or PIDs approach exhaustion, the kubelet terminates pods to reclaim resources and protect node availability. The pod phase changes to <code>Failed</code> with reason <code>Evicted</code>, and the node reports conditions such as <code>MemoryPressure</code> or <code>DiskPressure</code>.</p> <p>This guide covers node-pressure eviction triggered by the kubelet, not voluntary disruption from <code>kubectl drain</code> or PodDisruptionBudget enforcement.</p>Kubernetes pod exits immediately: how to diagnose ithttps://www.netdata.cloud/guides/kubernetes/kubernetes-pod-exits-immediately/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-pod-exits-immediately/<p>When a pod shows <code>Completed</code> or <code>Error</code> with zero restarts, the container exited on its first run. The diagnostic evidence lives in termination metadata, not in a growing restart count. This is distinct from <code>CrashLoopBackOff</code>, where the kubelet has already applied exponential backoff after multiple restarts.</p> <p>This guide covers how to distinguish a clean exit, an OOM kill, an application crash, and a configuration error using only the kubelet&rsquo;s reported state and the previous container logs, plus which node-level and control-plane signals to check when the container produced no logs.</p>Kubernetes pod ImagePullBackOff: registry, auth, and network diagnosishttps://www.netdata.cloud/guides/kubernetes/kubernetes-pod-imagepullbackoff/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-pod-imagepullbackoff/<p><code>ImagePullBackOff</code> means the kubelet cannot pull a required image. After each <code>ErrImagePull</code> failure, the kubelet retries with exponential backoff capped at five minutes. When <code>serializeImagePulls</code> is true, a single slow pull blocks every subsequent pull on that node. Read the exact error from the CRI in pod events, test the registry directly from the node, and fix the root cause without blindly recreating pods.</p> <h2 id="what-this-means">What this means</h2> <p>The kubelet asks the container runtime to pull any image not cached locally. The runtime resolves the registry, authenticates, downloads layers, and unpacks them into node storage. A failure at any step returns a CRI error that the kubelet surfaces as a pod event. <code>kubectl get pod</code> shows only the state; the reason lives in the events.</p>Kubernetes pod OOMKilled: cgroup limits, evictions, and fixeshttps://www.netdata.cloud/guides/kubernetes/kubernetes-pod-oomkilled/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-pod-oomkilled/<p>A pod status of <code>OOMKilled</code> means the container restarted after the kernel sent SIGKILL because it could not satisfy a memory allocation. There is no graceful shutdown.</p> <p>Distinguish whether the kill happened at the container cgroup level (a limit you set) or at the node level (a system-wide shortage). Then separate kernel OOM kills from kubelet evictions, identify the correct fix, and prevent recurrence without guessing at memory limits.</p> <h2 id="what-this-means">What this means</h2> <p><code>OOMKilled</code> means the Linux OOM killer selected a process in your container and terminated it with SIGKILL (signal 9). Exit code 137 (128 + 9) often maps to <code>OOMKilled</code>, but the code alone is ambiguous: it can also result from a manual <code>docker kill</code> or an escalated graceful termination. Verify the pod status <code>Reason</code> field.</p>Kubernetes pod stuck ContainerCreating: volume, network, and image issueshttps://www.netdata.cloud/guides/kubernetes/kubernetes-pod-containercreating/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-pod-containercreating/<p>A pod stuck in <code>ContainerCreating</code> never produces logs or readiness events. The kubelet accepted the spec but blocked during initialization after scheduling and before the container runtime starts the user process. The dominant failure domains are volume mount deadlocks, CNI sandbox creation failures, and image pull problems. They all surface the same status but need different fixes. This guide shows how to identify the stuck subsystem and resolve it.</p> <h2 id="what-this-means">What this means</h2> <p><code>ContainerCreating</code> is the phase where the kubelet pulls the image, creates the pod sandbox via CRI, attaches and mounts volumes, injects ConfigMaps and Secrets, and starts the container. These steps run largely synchronously in the pod worker. If a mount hangs, a CNI plugin errors, or the registry rejects the pull, the worker blocks and the pod stays in <code>ContainerCreating</code>. The node condition can remain <code>Ready</code> because the kubelet sync loop and PLEG are still healthy, so cluster monitoring may miss the problem. Identifying whether the block is in storage, network, or images is the first step.</p>Kubernetes pod stuck on volume mount: CSI, permissions, and timeoutshttps://www.netdata.cloud/guides/kubernetes/kubernetes-volume-mount-failures/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-volume-mount-failures/<p>You scale a StatefulSet and the new pods sit in <code>ContainerCreating</code> for ten minutes. The node is <code>Ready</code>. The CSI driver pods are running. <code>kubectl describe</code> shows no <code>FailedMount</code> events, yet the containers never start. The absence of volume events often misleads operators into checking image registries or resource quotas instead of the storage path. The kubelet volume manager is blocked somewhere between attach and mount, and Kubernetes will not retry fast enough to hide the problem.</p>Kubernetes pod stuck Pending: scheduling failures explainedhttps://www.netdata.cloud/guides/kubernetes/kubernetes-pod-pending/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-pod-pending/<p>A Deployment scales up and the new replicas stay Pending. No containers start, no logs appear, and <code>kubectl logs</code> returns nothing because no node is assigned yet. When a pod is stuck in Pending, the scheduler has either not yet evaluated it or has rejected every candidate node. Containers cannot start until the pod is assigned, so this blocks rollouts, autoscaling, and recovery.</p> <p>This guide covers indefinite Pending caused by scheduling failures: the scheduler Filter phase returns zero viable nodes. Read the FailedScheduling event, distinguish capacity shortages from impossible constraints, and fix the root cause without guessing.</p>Kubernetes pod stuck Terminating: finalizers, grace periods, and force deletehttps://www.netdata.cloud/guides/kubernetes/kubernetes-pod-stuck-terminating/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-pod-stuck-terminating/<p>A pod stuck in <code>Terminating</code> stays visible in the <a href="https://www.netdata.cloud/guides/kubernetes/kubernetes-api-server-slow/">API server</a> after <code>kubectl delete</code>, sometimes for minutes or hours. Usually a finalizer blocks removal, a CSI volume is still attached, or the container is ignoring SIGTERM. Force deleting without diagnosis orphans containers and can violate StatefulSet guarantees. Check the signals first, then decide whether to wait, patch a finalizer, or force delete.</p> <h2 id="what-this-means">What This Means</h2> <p>When you delete a pod, the API server sets <code>metadata.deletionTimestamp</code> and starts a graceful deletion window controlled by <code>terminationGracePeriodSeconds</code> (default 30). The kubelet executes any <code>preStop</code> hooks, sends SIGTERM to all containers, and waits up to the grace period before sending SIGKILL.</p>Kubernetes PVC stuck Pending: storage class, provisioner, and quotahttps://www.netdata.cloud/guides/kubernetes/kubernetes-pvc-stuck-pending/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-pvc-stuck-pending/<p>A PersistentVolumeClaim stuck in <code>Pending</code> is a storage-layer failure. Unlike a pod that is <code>Pending</code> due to CPU or memory, a PVC in <code>Pending</code> means the cluster cannot provision the volume. The cause usually sits in one of three layers: the StorageClass and its provisioner, namespace-level ResourceQuota limits, or topology and cloud constraints that prevent volume creation and attachment.</p> <p>When a PVC stays unbound, dependent pods cannot start. StatefulSets stall, rolling updates hang, and storage-dependent applications remain offline.</p>Kubernetes Scheduler Not Scheduling Pods: Queue Depth & Failure Reasonshttps://www.netdata.cloud/guides/kubernetes/kubernetes-scheduler-not-scheduling/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-scheduler-not-scheduling/<p>Pods stay Pending for many reasons, but the scheduler process being down is rarely one. More often, pods accumulate in internal queues because the cluster is out of capacity, a control plane dependency stalls the binding cycle, or a filter plugin rejects every candidate node. Distinguishing &ldquo;unschedulable&rdquo; (no node fits) from &ldquo;not scheduling&rdquo; (the scheduler cannot keep up or the binding cycle is failing) prevents wasted node scaling when the real problem is an <a href="https://www.netdata.cloud/guides/kubernetes/kubernetes-api-server-etcd-latency/">etcd latency</a> spike or a volume affinity conflict.</p>Kubernetes Service Not Reachable: Kube-Proxy, Endpoints & DNShttps://www.netdata.cloud/guides/kubernetes/kubernetes-service-not-reachable/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/kubernetes/kubernetes-service-not-reachable/<p>A Service fails when the chain between the client and backend breaks. That chain depends on EndpointSlices to list healthy pods, kube-proxy to program kernel rules, and cluster DNS to resolve names to ClusterIPs. This guide covers the gap between healthy backend pods and an unreachable Service, focusing on kube-proxy data-plane programming, endpoint state, and DNS dependencies. It does not cover application-level bugs inside the pod.</p> <h2 id="what-this-means">What This Means</h2> <p>Reachability is a control-loop problem. kube-proxy watches Services and EndpointSlices, then programs iptables, IPVS, or nftables rules to DNAT traffic to healthy endpoints. These rules persist in the kernel if kube-proxy crashes, but updates stop until it resumes. DNS resolution targets the CoreDNS ClusterIP, so a kube-proxy failure often appears as a DNS outage before a direct Service timeout.</p>License expiry silently disabling features: monitor days-to-expiryhttps://www.netdata.cloud/guides/network/network-license-expiry-silent-disable/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-license-expiry-silent-disable/<p>Your firewall dashboard shows green. Interfaces are up, CPU and memory are normal, traffic is flowing. But at 09:00, someone reports VPN connections failing, IPS no longer blocking threats, or URL filtering not enforcing policy. A feature license expired at midnight, and the device silently stopped performing the licensed function without raising a visible alarm.</p> <p>The device stays up, counters keep incrementing, throughput looks normal. The license-expiry message in syslog is low severity and gets buried under routine noise. By the time someone notices, the feature has been disabled for hours.</p>Lighttpd Monitoringhttps://www.netdata.cloud/monitoring-101/lighttpd-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/lighttpd-monitoring/<h2 id="lighttpd-monitoring">Lighttpd Monitoring</h2> <p>Welcome to the comprehensive guide on monitoring Lighttpd, a flexible and lightweight web server. This guide will take you through everything you need to know about monitoring Lighttpd using the Netdata platform. From understanding essential metrics to employ advanced performance monitoring techniques, Netdata provides a powerful Lighttpd monitoring tool for all your DevOps, SRE, and IT admin needs.</p> <h3 id="what-is-lighttpd">What Is Lighttpd?</h3> <p><a href="https://www.lighttpd.net/">Lighttpd</a> is an open-source web server optimized for speed-critical environments while maintaining a low memory footprint. Its feature set and performance make it a popular choice for many developers and engineers looking to implement efficient web solutions.</p>Linode Monitoringhttps://www.netdata.cloud/monitoring-101/linode-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/linode-monitoring/<h2 id="linode-monitoring">Linode Monitoring</h2> <h3 id="what-is-linode">What Is Linode?</h3> <p>Linode is a cloud hosting service that provides virtual servers to deploy applications, manage web hosting, and scale infrastructure as demands grow. Known for its simplicity and cost-effectiveness, Linode empowers developers, DevOps teams, and IT Administrators to manage cloud-based services with flexibility and efficiency.</p> <h3 id="monitoring-linode-with-netdata">Monitoring Linode With Netdata</h3> <p>Monitoring Linode is crucial to ensure optimal performance, cost management, and resource allocation. Netdata serves as an effective Linode monitoring tool, leveraging an openmetrics (Prometheus) exporter to collect real-time data without the need for standalone Prometheus or Grafana servers. This integration provides you with automated dashboards, alerts, and comprehensive insights into your Linode instances.</p>Linux Sensors Monitoringhttps://www.netdata.cloud/monitoring-101/sensors-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/sensors-monitoring/<h2 id="linux-sensors-monitoring">Linux Sensors Monitoring</h2> <h3 id="what-is-linux-sensors">What Is Linux Sensors?</h3> <p>Linux Sensors is a comprehensive suite for monitoring hardware sensors in Linux systems, gathering real-time data about temperature, voltage, fan speed, energy consumption, and more. Leveraging the sysfs interface, it provides a robust way for systems and applications to access sensor data, crucial for maintaining optimal server performance and health.</p> <h3 id="monitoring-linux-sensors-with-netdata">Monitoring Linux Sensors With Netdata</h3> <p>Netdata is a powerful, real-time Linux sensors monitoring tool that allows you to effortlessly monitor Linux Sensors. By utilizing the <a href="https://www.kernel.org/doc/Documentation/hwmon/sysfs-interface">sysfs interface</a>, Netdata automatically detects all available sensors on your system, providing you with instant visibility into sensor metrics such as temperature, voltage, current, and power usage.</p>Litespeed Monitoringhttps://www.netdata.cloud/monitoring-101/litespeed-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/litespeed-monitoring/<h2 id="litespeed-monitoring">Litespeed Monitoring</h2> <h3 id="what-is-litespeed">What Is Litespeed?</h3> <p>Litespeed is a powerful web server technology that boosts website speed and security. It is renowned for its high-performance capabilities, delivering superior HTTP/HTTPS content and optimizing traffic handling. Discover more about <a href="https://www.litespeedtech.com/products/litespeed-web-server">Litespeed</a>.</p> <h3 id="monitoring-litespeed-with-netdata">Monitoring Litespeed With Netdata</h3> <p>Utilizing Netdata to monitor Litespeed provides comprehensive insights into your web server&rsquo;s performance. As a real-time, distributed monitoring tool, Netdata captures extensive metrics, ensuring your server operates efficiently and responds proactively to issues. You can begin monitoring Litespeed effortlessly with <a href="https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/litespeed/">Netdata&rsquo;s Litespeed Monitoring Tool</a>.</p>Locating endpoints behind NAT and wireless: the positioning problemhttps://www.netdata.cloud/guides/network/network-endpoint-positioning-nat-wifi/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-endpoint-positioning-nat-wifi/<p>Endpoint positioning maps a MAC address or IP to a specific switch port, access point, or VLAN. It underpins security investigations, access control enforcement, and day-to-day troubleshooting. When the endpoint sits behind a NAT boundary, the Layer 2 and Layer 3 signals that topology engines rely on (FDB entries, ARP tables, flow records) all report the NAT device&rsquo;s identity, not the endpoint behind it. The endpoint becomes operationally invisible upstream.</p>Logstash Monitoringhttps://www.netdata.cloud/monitoring-101/logstash-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/logstash-monitoring/<h2 id="logstash-monitoring">Logstash Monitoring</h2> <h3 id="what-is-logstash">What Is Logstash?</h3> <p>Logstash is a powerful, open-source tool for managing events and logs. It plays a pivotal role in data collection within the <a href="https://www.elastic.co/products/logstash">Elastic Stack</a>, allowing for seamless data transportation from a multitude of sources to your target destinations for further analysis or storage.</p> <h3 id="monitoring-logstash-with-netdata">Monitoring Logstash With Netdata</h3> <p>Netdata provides an effective Logstash monitoring tool that offers real-time insights into Logstash performance. Through the integration with <a href="https://app.netdata.cloud/?utm_source=website&amp;utm_content=monitoring101">Netdata Cloud</a>, DevOps teams can oversee Logstash’s health and quickly identify any anomalies or inefficiencies that could affect their data pipelines. Check out our <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">Live Demo</a> to see Netdata in action.</p>Loki Monitoringhttps://www.netdata.cloud/monitoring-101/loki-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/loki-monitoring/<h2 id="loki-monitoring">Loki Monitoring</h2> <h3 id="what-is-loki">What Is Loki?</h3> <p>Loki is an open-source log aggregation system developed by Grafana Labs. It is designed to manage, aggregate, and analyze log data efficiently. Inspired by Prometheus, it focuses on performance and scalability for search across different log streams. Unlike traditional logging tools, Loki uses dynamic tagging to allow logs to be efficiently stored and accessed, promoting cost-effective log management.</p> <h3 id="monitoring-loki-with-netdata">Monitoring Loki With Netdata</h3> <p>Netdata offers an advanced monitoring solution specifically tailored for Loki. Utilizing an openmetrics Prometheus exporter, Netdata effectively gathers metrics from your Loki instances without the need for a Prometheus server or Grafana setup. This means users can benefit from automated dashboards, real-time alerts, and more. Netdata&rsquo;s integration simplifies the process, allowing you to intensely monitor Loki&rsquo;s performance and health with ease.</p>Lustre Metadata Monitoringhttps://www.netdata.cloud/monitoring-101/lustre-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/lustre-monitoring/<h2 id="lustre-metadata-monitoring">Lustre Metadata Monitoring</h2> <h3 id="what-is-lustre-metadata">What Is Lustre Metadata?</h3> <p>Lustre is a type of parallel distributed file system, widely used for large-scale cluster computing. Originally developed for research and enterprise sectors due to its capacity and high performance, Lustre metadata refers to the internal management data that keeps track of file location, size, and storage attributes. Monitoring Lustre metadata is crucial for maintaining optimal file system operations and ensuring efficient management.</p> <h3 id="monitoring-lustre-metadata-with-netdata">Monitoring Lustre Metadata With Netdata</h3> <p>Monitoring Lustre with Netdata provides seamless tracking of all critical metrics using an openmetrics (prometheus) exporter. To monitor Lustre metadata, Netdata taps into the <a href="https://github.com/GSI-HPC/prometheus-cluster-exporter">Cluster Exporter</a> which is capable of gathering essential data. With Netdata, you can ingest data from any Prometheus exporter; unlocking automated dashboards and alerts without needing a Prometheus server or Grafana. This integration supports efficient Lustre metadata monitoring and ensures constant observability over your cluster&rsquo;s performance.</p>LVM logical volumes Monitoringhttps://www.netdata.cloud/monitoring-101/lvm-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/lvm-monitoring/<h2 id="lvm-logical-volumes-monitoring">LVM logical volumes Monitoring</h2> <h3 id="what-is-lvm">What Is LVM?</h3> <p>LVM, or Logical Volume Manager, is a system for managing logical volumes, or filesystems, in Linux environments. It provides a high level of flexibility, allowing administrators to easily resize, extend, or shrink volumes according to their needs. This flexibility is particularly useful in dynamic and modern data environments.</p> <h3 id="monitoring-lvm-with-netdata">Monitoring LVM With Netdata</h3> <p>Monitoring LVM logical volumes efficiently is where the Netdata monitoring tool excels. With <a href="https://github.com/netdata/netdata">Netdata</a>, you can monitor LVM to ensure each logical volume&rsquo;s health and performance. Netdata leverages the <code>lvs</code> CLI tool securely by using <code>ndsudo</code> to facilitate robust and secure data collection without the need for <code>sudo</code>.</p>Lynis Audit Reports Monitoringhttps://www.netdata.cloud/monitoring-101/lynis-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/lynis-monitoring/<h2 id="lynis-audit-reports-monitoring">Lynis Audit Reports Monitoring</h2> <h3 id="what-is-lynis">What Is Lynis?</h3> <p>Lynis is a renowned security auditing tool designed to perform comprehensive scans and audits on Unix-based systems. Its diverse range of checks helps ensure robust system security and compliance, making it a crucial element in any security-conscious IT infrastructure.</p> <h3 id="monitoring-lynis-with-netdata">Monitoring Lynis With Netdata</h3> <p>To effectively monitor Lynis audit reports, Netdata utilizes an openmetrics (prometheus) exporter. This setup allows Netdata to gather rich metrics by periodically sending HTTP requests to <a href="https://github.com/MauveSoftware/lynis_exporter">lynis_exporter</a>. Netdata is adept at ingesting data from any Prometheus exporter, empowering users to visualize information with automated dashboards and receive instant alerts without needing a separate Prometheus server or Grafana installation.</p>MaxScale Monitoringhttps://www.netdata.cloud/monitoring-101/maxscale-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/maxscale-monitoring/<h2 id="maxscale-monitoring">MaxScale Monitoring</h2> <h3 id="what-is-maxscale">What Is MaxScale?</h3> <p>MaxScale is a database proxy that manages the traffic between client applications and a set of database servers. It is an integral part of the MariaDB ecosystem, coordinating database operations and optimizing performance and scalability for distributed database environments. <a href="https://mariadb.com/kb/en/maxscale/">Learn more about MaxScale.</a></p> <h3 id="monitoring-maxscale-with-netdata">Monitoring MaxScale With Netdata</h3> <p>Netdata provides a comprehensive MaxScale monitoring tool that helps you keep an eye on the performance and health of your MaxScale instances. The Netdata Agent collects real-time metrics from MaxScale, enabling you to monitor MaxScale servers efficiently. With Netdata’s extensive visualizations and intuitive interface, you can diagnose root causes of performance issues swiftly and effectively. For hands-on experience, check out our <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">Live Demo</a> or <a href="https://app.netdata.cloud/?utm_source=website&amp;utm_content=monitoring101">sign up for a free trial</a>.</p>MegaCLI MegaRAID Monitoringhttps://www.netdata.cloud/monitoring-101/megacli-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/megacli-monitoring/<h2 id="megacli-megaraid-monitoring">MegaCLI MegaRAID Monitoring</h2> <h3 id="what-is-megacli-megaraid">What Is MegaCLI MegaRAID?</h3> <p>MegaCLI is a powerful command-line utility from Broadcom, primarily used to manage and monitor MegaRAID storage controllers. <a href="https://wikitech.wikimedia.org/wiki/MegaCli">Learn more</a>.</p> <h3 id="monitoring-megacli-megaraid-with-netdata">Monitoring MegaCLI MegaRAID With Netdata</h3> <p>Using Netdata as your MegaCLI monitoring tool allows you to monitor the health and performance of your RAID adapters, physical drives, and backup batteries seamlessly. Netdata&rsquo;s real-time monitoring capabilities make it one of the most effective tools for monitoring MegaCLI.</p>Meilisearch Monitoringhttps://www.netdata.cloud/monitoring-101/meilisearch-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/meilisearch-monitoring/<h2 id="meilisearch-monitoring">Meilisearch Monitoring</h2> <h3 id="what-is-meilisearch">What Is Meilisearch?</h3> <p>Meilisearch is a powerful, open-source, and real-time search engine designed for swift search interactions across large datasets. Its lightweight design and focus on performance and developer-friendliness make it an ideal choice for modern applications demanding fast and accurate search capabilities.</p> <h3 id="monitoring-meilisearch-with-netdata">Monitoring Meilisearch With Netdata</h3> <p>When it comes to tools for monitoring Meilisearch, Netdata stands out as a performance-efficient solution. Netdata uses an openmetrics (Prometheus) exporter to monitor Meilisearch, such as the <a href="https://github.com/scottaglia/meilisearch_exporter">Meilisearch Exporter</a>, which efficiently gathers search engine metrics. With Netdata, you can ingest data from any Prometheus-compatible exporter, automatically generating on-demand dashboards and alerts without requiring a dedicated Prometheus server or Grafana setup. This streamlined monitoring process ensures you receive real-time insights without the need for extensive infrastructure.</p>Mesos Monitoringhttps://www.netdata.cloud/monitoring-101/mesos-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/mesos-monitoring/<h2 id="mesos-monitoring">Mesos Monitoring</h2> <h3 id="what-is-mesos">What Is Mesos?</h3> <p>Apache Mesos is a powerful cluster manager that simplifies resource management and task scheduling across distributed systems. It&rsquo;s widely used to organize and optimize processing tasks in cloud computing environments, taking the complexity out of managing large scale data centers.</p> <h3 id="monitoring-mesos-with-netdata">Monitoring Mesos With Netdata</h3> <p>To monitor Mesos, Netdata leverages an openmetrics (prometheus) exporter, specifically the <a href="https://github.com/mesosphere/mesos_exporter">Mesos exporter</a>. Netdata stands out by ingesting data from any Prometheus exporter, providing automated dashboards and alerts without the need for a separate Prometheus server or Grafana setup. This integration with Netdata enables users to effortlessly track performance metrics and ensure efficient resource allocation across all running instances. Discover the potential by trying out our <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">Live Demo</a>.</p>Microbursts: catching sub-second congestion that minute averages hidehttps://www.netdata.cloud/guides/network/network-microbursts/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-microbursts/<p>Your switches are dropping packets. The utilization charts say everything is fine. Interface counters show moderate load, error rates are clean, and no congestion alert has fired. But applications report retransmissions, latency spikes, and intermittent connectivity. The problem resolved between polls.</p> <p>A microburst is a short, intense spike of traffic that fills a switch egress queue faster than the queue can drain. The burst may last 50 milliseconds or less, but during that window the queue overflows and packets are tail-dropped. By the time your SNMP poller arrives 60 or 300 seconds later, the burst is over, the queue has drained, and interface utilization has been averaged down to an unremarkable number.</p>Microsoft Exchange Server Monitoringhttps://www.netdata.cloud/monitoring-101/msexchange-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/msexchange-monitoring/<h2 id="microsoft-exchange-server">Microsoft Exchange Server</h2> <p>Microsoft Exchange Server is a <strong>mail server and calendaring server</strong> that runs on Windows Server operating systems. <a href="https://www.microsoft.com/en-gb/microsoft-365/exchange/email">It enables users to send and receive email messages, schedule appointments, store contacts, and access shared mailboxes and calendars within an organization</a>.</p> <h2 id="exchange-server-monitoring">Exchange Server Monitoring</h2> <p>To monitor Microsoft Exchange Server, you need to <strong>collect and analyze various performance metrics</strong> that reflect the health and performance of your server. Some of these metrics include:</p>Microsoft SQL Server (MSSQL) Monitoringhttps://www.netdata.cloud/monitoring-101/mssql-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/mssql-monitoring/<h2 id="microsoft-sql-server">Microsoft SQL Server</h2> <p><a href="https://en.wikipedia.org/wiki/Microsoft_SQL_Server">Microsoft SQL Server</a> is a relational database management system (RDBMS) developed by Microsoft. It is a software product that stores and retrieves data as requested by other software applications. <a href="https://www.microsoft.com/en-us/sql-server/sql-server-downloads">It can run on various platforms, such as Windows, Linux, and Azure</a>.</p> <h2 id="monitoring-microsoft-sql-server">Monitoring Microsoft SQL Server</h2> <p>To holistically monitor Microsoft SQL Server, you need to track various aspects of its performance, health, and availability. Some of the key metrics to monitor include system level metrics about the impact of SQL Server such as:</p>Microsoft SQL Server monitoring checklist: the signals every production instance needshttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-monitoring-checklist/<p>Most SQL Server outages are not exotic. The transaction log fills because a backup job silently stopped. A sleeping session with an open transaction blocks forty other sessions until the worker pool runs dry. TempDB runs out of space and every database on the instance stalls at once. All of these are visible hours or days in advance if you collect the right signals. Most teams do not.</p> <p>This checklist is the minimum set of signals a production SQL Server instance needs, organized so you can audit what you have today and fill the gaps. It targets standalone instances, failover cluster instances, and AlwaysOn AG deployments on-premises or on VMs. Azure SQL Database and Managed Instance share many of the same DMVs but abstract storage and resource governance differently.</p>Minecraft Monitoringhttps://www.netdata.cloud/monitoring-101/minecraft-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/minecraft-monitoring/<h2 id="minecraft-monitoring">Minecraft Monitoring</h2> <h3 id="what-is-minecraft">What Is Minecraft?</h3> <p>Minecraft is a sandbox video game that gained worldwide popularity due to its open-ended nature. It allows players to explore and create in a block-based world, using tools to build structures, gather resources, and craft items. With hundreds of millions of copies sold, Minecraft&rsquo;s appeal spans across all age groups and makes it not just a game but a platform for creativity and learning.</p> <h3 id="monitoring-minecraft-with-netdata">Monitoring Minecraft With Netdata</h3> <p>Monitoring your Minecraft server is essential to ensure smooth gameplay and optimal performance. Netdata provides a robust solution for monitoring Minecraft using the <a href="https://github.com/sladkoff/minecraft-prometheus-exporter">Minecraft Exporter</a>. By leveraging openmetrics, Netdata integrates seamlessly with any Prometheus exporter. This means you get automated dashboards, customizable alerts, and advanced analytics without needing to set up a separate Prometheus server or Grafana. This streamlined approach simplifies the monitoring process, allowing you to focus on what matters most—keeping your players happy.</p>MISCONF Redis is configured to save RDB snapshots - what it means and how to fix ithttps://www.netdata.cloud/guides/redis/redis-misconf-rdb-snapshots/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-misconf-rdb-snapshots/<p>Applications see <code>MISCONF Redis is configured to save RDB snapshots, but it's currently unable to persist to disk</code> (since Redis 7.0; Redis 4.0-6.2 prints <code>MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk</code>) on every write. Reads still work, but <code>SET</code>, <code>HSET</code>, <code>LPUSH</code>, and all mutating commands are rejected.</p> <p>Redis makes itself read-only when the last background save failed and <code>stop-writes-on-bgsave-error</code> is <code>yes</code> (the default). The error persists until a subsequent <code>BGSAVE</code> succeeds. Retrying writes will not help. The instance is protecting you from accepting writes that can never be persisted. To recover, fix the underlying persistence failure and clear the error state with a successful save.</p>Modbus Protocol Monitoringhttps://www.netdata.cloud/monitoring-101/modbus_rtu-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/modbus_rtu-monitoring/<h2 id="modbus-protocol-monitoring">Modbus Protocol Monitoring</h2> <h3 id="what-is-modbus-protocol">What Is Modbus Protocol?</h3> <p>The Modbus protocol is a messaging structure widely utilized in industrial automation systems to transmit data over serial lines between electronic devices. Originally developed in 1979 by Modicon (now Schneider Electric) to communicate with its PLCs, it has evolved to become a de facto standard in industries worldwide due to its simplicity and reliability.</p> <h3 id="monitoring-modbus-protocol-with-netdata">Monitoring Modbus Protocol With Netdata</h3> <p>Effectively monitoring the Modbus protocol is crucial for maintaining the performance and reliability of industrial control systems. Netdata offers an intuitive way to monitor Modbus by integrating with an openmetrics (Prometheus) exporter. Specifically, the <a href="https://github.com/dernasherbrezon/modbusrtu_exporter">modbusrtu_exporter</a> can be leveraged to collect vital metrics seamlessly.</p>MogileFS Monitoringhttps://www.netdata.cloud/monitoring-101/mogilefs-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/mogilefs-monitoring/<h2 id="mogilefs-monitoring">MogileFS Monitoring</h2> <h3 id="what-is-mogilefs">What Is MogileFS?</h3> <p>MogileFS is a distributed file system designed for managing large volumes of files efficiently. It offers reliable file storage across multiple servers, enabling seamless scalability and redundancy. Ideal for infrastructures that require extensive data storage solutions, MogileFS ensures data replication and distribution, making it resilient against server failures.</p> <h3 id="monitoring-mogilefs-with-netdata">Monitoring MogileFS With Netdata</h3> <p>To monitor MogileFS, Netdata utilizes a powerful tool known as an openmetrics (Prometheus) exporter. This mechanism allows Netdata to ingest data from any Prometheus exporter, providing users with automated and dynamic dashboards, notifications, and alerts—without the need for a dedicated Prometheus server or Grafana. The <a href="https://github.com/KKBOX/mogilefs-exporter">MogileFS Exporter</a> is designed specifically to collect metrics that provide insights into the performance and health of MogileFS systems. These metrics are crucial for real-time monitoring, ensuring prompt detection and resolution of any issues.</p>MongoDB Application Thread Evictions: How To Fixhttps://www.netdata.cloud/guides/mongodb/mongodb-application-thread-evictions/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-application-thread-evictions/<p>Query p99 latency doubles or triples, but <code>iostat</code> is not saturated and the slow query log shows no single offender. The signal is in <code>db.serverStatus().wiredTiger.cache</code>: <code>pages evicted by application threads</code> has moved from zero to a sustained nonzero rate.</p> <p>This metric marks the moment when WiredTiger&rsquo;s dedicated eviction workers fall behind and application threads are drafted to do the work. Any sustained nonzero rate is abnormal. Once application threads evict, they perform page reconciliation and disk I/O inline with the request handler thread, directly inflating user-visible latency. The companion counter <code>pages selected for eviction unable to be evicted</code> means eviction is stalled and the cache is effectively frozen.</p>MongoDB Balancer Stuck On Jumbo Chunks: Fix Ithttps://www.netdata.cloud/guides/mongodb/mongodb-balancer-stuck-jumbo-chunks/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-balancer-stuck-jumbo-chunks/<p>One shard is hot while the others idle. <code>sh.status()</code> shows chunk counts skewed more than 20%. The balancer is either stopped or running without closing the gap. Until you fix the root cause, the imbalance persists.</p> <p>Two failure modes cause this. The balancer itself can be disabled, restricted to a narrow window, or blocked by an unhealthy config server. Or the cluster has jumbo chunks: ranges that exceed the configured chunkSize but cannot split because too many documents share the exact same shard key value. MongoDB marks those chunks <code>jumbo</code> in <code>config.chunks</code> and the balancer skips them. That heavy chunk pins load and storage on a single shard and creates a floor on how balanced the cluster can become.</p>MongoDB cache too small: sizing the WiredTiger cache for your working sethttps://www.netdata.cloud/guides/mongodb/mongodb-cache-undersized-working-set/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-cache-undersized-working-set/<p>When MongoDB latency doubles and disk read IOPS climb, operators usually check indexes and the query planner first. If <code>db.currentOp()</code> shows no runaway query and the slow query log is quiet, the culprit is often the WiredTiger cache.</p> <p>WiredTiger maintains its own in-memory cache of uncompressed B-tree pages, separate from the OS page cache. MongoDB defaults the cache to <code>max(0.5 * (RAM - 1 GB), 256 MB)</code>. That default works for a single mongod on a dedicated host, but it breaks down in containers, multi-tenant deployments, and during organic data growth. Once the working set exceeds the cache, reads fault to disk, pages are decompressed, and eviction threads compete with application threads for CPU.</p>MongoDB checkpoint duration climbing: diagnosing slow WiredTiger checkpointshttps://www.netdata.cloud/guides/mongodb/mongodb-checkpoint-duration-high/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-checkpoint-duration-high/<p>You notice <code>transaction checkpoint most recent time (msecs)</code> climbing past 10 seconds, then 30, then 50. It is trending upward, check after check, approaching the 60-second default checkpoint interval. When checkpoint duration meets or exceeds the interval, WiredTiger has no margin left. The next checkpoint starts late, dirty pages accumulate faster than they flush, and the journal can fill to the point where all new writes block until the checkpoint finishes. This is a common production failure mode that starts as a slow climb and ends as a write freeze.</p>MongoDB checkpoint stall write freeze: when all writes stop with no errorhttps://www.netdata.cloud/guides/mongodb/mongodb-checkpoint-stall-write-freeze/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-checkpoint-stall-write-freeze/<p>Writes time out or hang while <code>mongod</code> is running, TCP port 27017 is open, and reads still return results from cache. The MongoDB logs are quiet, but <code>db.serverStatus().opcounters</code> shows write counts frozen. This is a WiredTiger checkpoint stall: the checkpoint process fell behind, dirty pages accumulated, and new writes blocked. The freeze lasts until the current checkpoint completes. If the I/O bottleneck remains, queued writes flood through and the next checkpoint stalls again.</p>MongoDB connection churn: high totalCreated rate and thread creation overheadhttps://www.netdata.cloud/guides/mongodb/mongodb-connection-churn/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-connection-churn/<p><code>db.serverStatus().connections</code> can show low <code>current</code> and a rapidly climbing <code>totalCreated</code>. That mismatch is connection churn: connections open and close rapidly instead of being reused. MongoDB allocates server-side state for every new connection; in thread-per-connection deployments, each cycle costs roughly a megabyte of thread stack, scheduling overhead, and file descriptor work. The result is rising RSS, CPU contention, and latency spikes that do not correlate with the active connection count.</p> <p>For the broader mental model, see <a >How MongoDB actually works in production: a mental model for operators</a>. For the cascade after a failover, see <a href="https://www.netdata.cloud/guides/mongodb/mongodb-connection-storm-spiral/">MongoDB connection storm spiral: reconnection floods after an election or deploy</a>.</p>MongoDB connection refused at maxIncomingConnections: hitting the connection ceilinghttps://www.netdata.cloud/guides/mongodb/mongodb-connection-limit-reached/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-connection-limit-reached/<p>Application logs show connection timeouts. MongoDB logs show <code>connection refused</code> or <code>error accepting new connection</code>. <code>db.serverStatus().connections</code> shows <code>current</code> well below the configured maximum. This disconnect means you are hitting a hard ceiling at the TCP accept layer, not experiencing gradual degradation.</p> <p>MongoDB uses a one-thread-per-connection model. Each accepted connection consumes two file descriptors and a thread stack sized by the OS <code>ulimit -s</code>. While <code>maxIncomingConnections</code> sets the logical inbound cap, the OS file-descriptor limit (<code>ulimit -n</code>) usually enforces the actual ceiling. Rejections happen before the connection handshake completes, so <code>serverStatus().connections.current</code> never counts refused connections. Look at logs, ratios, and OS-level resource counts to find the real limit.</p>MongoDB connection storm spiral: reconnection floods after an election or deployhttps://www.netdata.cloud/guides/mongodb/mongodb-connection-storm-spiral/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-connection-storm-spiral/<p>Connection count on a primary jumps from 200 to 4,000 in under a minute. Resident memory climbs, query latencies double, and application logs fill with timeout errors. The slow query log shows nothing unusual. Individual queries are not the problem. The database is drowning in threads.</p> <p>This is a connection storm spiral. A trigger event, usually a replica set election, application deploy, or network blip, invalidates existing connections across your application fleet. Every driver reconnects at once. Each new connection costs MongoDB a dedicated thread and roughly 1 MB of stack memory. The resulting RSS spike and ticket contention slow down operations already in flight, causing more timeouts, which drives even more reconnections. The feedback loop ends in OOM kill or unresponsiveness.</p>MongoDB disk full: emergency recovery when mongod can't write the journalhttps://www.netdata.cloud/guides/mongodb/mongodb-disk-full/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-disk-full/<p>When the filesystem backing the data or journal directory crosses a critical threshold, WiredTiger cannot allocate new journal extents. If mongod crashes or restarts, recovery replays journal files since the last checkpoint and requires free headroom to create or extend files during that replay. On a full disk, mongod hangs in recovery without binding to port 27017.</p> <p>If the node is a standalone, there is no replica to fail over to. If it is a secondary, cluster redundancy is reduced while the member is down. Recovery is complicated by a counterintuitive storage engine behavior: WiredTiger reclaims space internally after deletes, but does not automatically shrink data files or return bytes to the operating system. A volume that reads 99% full after a massive delete remains 99% full at the filesystem level.</p>MongoDB disk I/O saturation: correlating iostat with WiredTiger signalshttps://www.netdata.cloud/guides/mongodb/mongodb-disk-io-saturation/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-disk-io-saturation/<p>When <code>opLatencies.writes</code> climbs and <code>globalLock.currentQueue</code> grows, <code>db.serverStatus().wiredTiger.transaction</code> often shows the most recent checkpoint took 45 seconds. WiredTiger metrics tell you <em>what</em> is hurting, but they do not tell you <em>why</em>. The next question is whether the disk is actually saturated.</p> <p>Disk I/O saturation surfaces as climbing journal sync latency, checkpoint duration exceeding the 60-second interval, application-thread evictions, and ticket exhaustion. The only way to separate a storage problem from a query problem is to correlate OS-level disk signals (<code>iostat -x</code>) with WiredTiger internal signals in the same time window. This guide shows how to do that safely during an incident.</p>MongoDB exceeded memory limit for $group — aggregation spills and allowDiskUsehttps://www.netdata.cloud/guides/mongodb/mongodb-exceeded-memory-limit-group-sort/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-exceeded-memory-limit-group-sort/<p>Application logs show code 292 (<code>QueryExceededMemoryLimitNoDiskUseAllowed</code>), or an aggregation pipeline slows by an order of magnitude. Eligible blocking aggregation stages are limited to 100 megabytes of RAM. When a stage exceeds this limit and disk spilling is not enabled, the operation fails immediately. If spilling is enabled, MongoDB writes temporary files to disk, which keeps the pipeline alive but adds unpredictable latency and extra I/O load.</p> <p>Before MongoDB 6.0, you had to explicitly opt in to disk spilling with <code>{ allowDiskUse: true }</code>. Starting in 6.0, the <code>allowDiskUseByDefault</code> server parameter is <code>true</code>, so eligible stages spill automatically. That removes the hard failure for many pipelines, but it also makes it easier for heavy workloads to hide behind disk I/O instead of failing fast. The <code>$push</code> and <code>$addToSet</code> accumulators inside <code>$group</code> cannot spill to disk regardless of the setting. <code>$graphLookup</code> can spill when allowed by <code>allowDiskUse</code>; it returns an error only when spilling is prohibited.</p>MongoDB exposed to the internet without authentication: bindIp and the breach scenariohttps://www.netdata.cloud/guides/mongodb/mongodb-exposed-without-auth/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-exposed-without-auth/<p>A <code>mongod</code> process bound to all interfaces with authentication disabled exposes every database to any host that can reach port 27017. If you are responding to a scan, PAGE, or audit, confirm the exposure, measure the blast radius, and eliminate the surface.</p> <h2 id="what-this-means">What this means</h2> <p>MongoDB&rsquo;s <code>net.bindIp</code> controls which interfaces accept connections. Modern packages default <code>bindIp</code> to <code>127.0.0.1</code>; exposure usually follows an explicit override to a wildcard such as <code>0.0.0.0</code> or <code>::</code>. Without authentication, any reachable host can list databases, read or write documents, and execute administrative commands.</p>MongoDB journal sync latency high: the storage signal that warns 60 seconds earlyhttps://www.netdata.cloud/guides/mongodb/mongodb-journal-sync-latency-high/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-journal-sync-latency-high/<p>Application write latency spikes. Connections pile up. Look back 60 seconds and WiredTiger journal sync latency was likely already climbing. Every write with <code>j:true</code> or <code>w:&quot;majority&quot;</code> blocks until the journal buffer is fsynced to disk. When storage struggles, journal sync is the first domino to fall.</p> <p>Journal sync latency is a storage subsystem signal, not a query or cache problem. The block device under <code>mongod</code> cannot absorb small sequential writes fast enough. The result is head-of-line delay for all durable writes, which cascades into ticket exhaustion and connection backlog.</p>MongoDB lock wait times: collection and metadata lock contention during DDLhttps://www.netdata.cloud/guides/mongodb/mongodb-lock-wait-times/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-lock-wait-times/<p>When p99 latency jumps and <code>globalLock.currentQueue</code> grows, check <code>serverStatus().locks</code>. If <code>timeAcquiringMicros</code> is climbing for <code>Collection</code> or <code>Metadata</code>, the cause is almost always DDL: <code>createIndexes</code>, <code>dropIndexes</code>, <code>collMod</code>, <code>renameCollection</code>, or similar commands that acquire exclusive collection, database, or metadata locks. WiredTiger uses document-level concurrency for ordinary reads and writes, so normal CRUD rarely blocks. A single schema change can serialize operations on a hot collection or across a database during peak traffic.</p>MongoDB long-running operations: finding and killing the query holding a tickethttps://www.netdata.cloud/guides/mongodb/mongodb-long-running-operations/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-long-running-operations/<p>Your application latency just spiked. <code>opLatencies</code> show reads and writes climbing. <code>globalLock.currentQueue</code> is no longer zero. You check <code>db.serverStatus().wiredTiger.concurrentTransactions</code>: available tickets are near zero, but throughput has not increased. An operation is holding a ticket without making progress.</p> <p>A collection scan, an unbounded aggregation, or a stalled write can hold a WiredTiger read or write ticket for minutes. The default is 128 read and 128 write tickets in MongoDB ≤6.x (7.0+ dynamically adjusts, capped at 128), so one long-running operation can cascade into system-wide queuing, connection pileup, and application timeouts. Find it and kill it, but killing the wrong operation can crash a node or leave data inconsistent.</p>MongoDB Monitoringhttps://www.netdata.cloud/monitoring-101/mongodb-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/mongodb-monitoring/<h2 id="mongodb-monitoring">MongoDB Monitoring</h2> <h3 id="what-is-mongodb">What Is MongoDB?</h3> <p>MongoDB is a leading NoSQL database platform designed for flexibility, scalability, and performance. It is used to store documents in a flexible, JSON-like format, which makes it perfect for handling large volumes of unstructured data. For more insights, check out <a href="https://www.mongodb.com/">MongoDB&rsquo;s official site</a>.</p> <h3 id="monitoring-mongodb-with-netdata">Monitoring MongoDB With Netdata</h3> <p>Netdata provides comprehensive monitoring for MongoDB, allowing users to gain real-time insights into their MongoDB servers. By utilizing the <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/mongodb/">MongoDB monitoring tool from Netdata</a>, users can track critical metrics and enhance their troubleshooting capabilities.</p>MongoDB monitoring checklist: the signals every production cluster needshttps://www.netdata.cloud/guides/mongodb/mongodb-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-monitoring-checklist/<p>Production MongoDB failures are preceded by signals that are visible but often unmonitored: climbing dirty cache ratio, shrinking oplog window, or ticket counts approaching zero. This guide organizes essential signals into four monitoring levels. Use them to audit instrumentation or triage gaps during an incident.</p> <p>Each level builds on the previous one. If you are missing a survival signal, instrument it before adding expert metrics. The thresholds below are drawn from the MongoDB <code>serverStatus()</code> and <code>rs.status()</code> contract and from operational patterns observed across WiredTiger deployments.</p>MongoDB no primary / election storm: repeated elections and write outageshttps://www.netdata.cloud/guides/mongodb/mongodb-no-primary-election-storm/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-no-primary-election-storm/<p>Applications log &ldquo;not primary&rdquo; errors. <code>rs.status()</code> shows a different <code>PRIMARY</code> than thirty seconds ago. MongoDB logs repeat <code>&quot;Starting an election&quot;</code> and <code>&quot;Stepping down&quot;</code>. Each election costs 2-12 seconds of write unavailability. More than two in ten minutes is an election storm.</p> <p>This pattern is more dangerous than a single failover because it creates rolling write outages that do not self-stabilize. Drivers reconnect, retry buffers fill, and application latency degrades even when a primary exists. Root causes usually fall into three categories: the primary is too slow to answer heartbeats, the network is dropping or delaying packets between members, or a misconfigured priority is forcing a healthy primary to step down.</p>MongoDB not master error: writes hitting a non-primary node after failoverhttps://www.netdata.cloud/guides/mongodb/mongodb-not-master-error/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-not-master-error/<p>A node restart, network partition, or planned stepdown triggers a MongoDB election. Seconds later, application logs show <code>NotWritablePrimary</code> (code 10107) or the legacy string <code>not master and slaveOk=false</code>. Writes fail against a node that used to be PRIMARY, even though the cluster has elected a new one.</p> <p>This guide covers how to find the root cause and stop it from recurring.</p> <h2 id="what-this-means">What this means</h2> <p>MongoDB replica sets elect exactly one PRIMARY at a time. When a failover occurs, the old primary steps down and a secondary is promoted. Application drivers discover the new topology through the replica set seed list and refresh their connection pools automatically. Between stepdown and election completion, there is a brief window with no writable primary. After the new primary is elected, drivers should route writes there.</p>MongoDB not primary and secondaryOk=false: reading from a secondary and how to fix ithttps://www.netdata.cloud/guides/mongodb/mongodb-not-primary-and-secondaryok-false/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-not-primary-and-secondaryok-false/<p>Your application logs show <code>NotPrimaryNoSecondaryOk</code> (code 13435) with the message <code>&quot;not primary and secondaryOk=false&quot;</code> on hello-capable clients (or <code>&quot;not master and slaveOk=false&quot;</code> on legacy clients). Metrics show read failures against a specific host. The <code>mongod</code> process is running, replica set heartbeats are clean, and replication lag looks normal. The cluster is not down. The error is a routing decision: a client sent a read to a replica set member that is not the primary, without declaring that reading from a non-primary is acceptable.</p>MongoDB OOM-killed by the kernel: RSS, cache sizing, and oom_score_adjhttps://www.netdata.cloud/guides/mongodb/mongodb-oom-killed/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-oom-killed/<p>You find <code>mongod</code> gone. The replica set has no primary. Applications time out. MongoDB logs show no graceful shutdown. Instead, <code>dmesg</code> shows <code>Out of memory: Killed process 12345 (mongod)</code>. The Linux OOM killer has reaped the process. MongoDB is a frequent target because its resident set size is usually the largest on the host.</p> <p>An OOM kill is not a MongoDB bug. It is the kernel freeing RAM by terminating the highest-scoring process. mongod&rsquo;s RSS is dominated by the WiredTiger cache, plus roughly 1 MB per connection, plus roughly 500 MB to 1 GB of internal overhead for indexes, session buffers, and stack. When that sum comes within 1 GB of total RAM, the node is in the danger zone. The kill is abrupt: no stepdown, no replica set coordination, and after restart the cache must warm again.</p>MongoDB operation exceeded time limit (MaxTimeMSExpired): maxTimeMS and killed operationshttps://www.netdata.cloud/guides/mongodb/mongodb-operation-exceeded-time-limit/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-operation-exceeded-time-limit/<p>Error code 50, <code>MaxTimeMSExpired</code>, means the server killed an operation that exceeded its processing budget. Raising the timeout without fixing the root cause turns acute failures into chronic resource exhaustion. The operation was already pathologically slow; <code>maxTimeMS</code> ended it before it consumed more resources or held locks and tickets indefinitely.</p> <p><code>maxTimeMS</code> sets a cumulative processing budget in milliseconds. MongoDB enforces it using the same interrupt mechanism as <code>killOp</code>, terminating the operation only at designated interrupt points. Idle time between cursor batches does not count toward the limit, and on direct connections network latency is excluded from the server-side clock. On sharded clusters, however, latency between <code>mongos</code> and shard <code>mongod</code> instances counts against the limit. Distinguish a true <code>MaxTimeMSExpired</code> from a client-side socket timeout, where the client gives up before the server responds.</p>MongoDB oplog window collapse: secondaries falling off and forced full resynchttps://www.netdata.cloud/guides/mongodb/mongodb-oplog-window-collapse/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-oplog-window-collapse/<p>A secondary transitions to RECOVERING and logs &ldquo;too stale to catch up.&rdquo; The oplog window compresses from 48 hours to 90 minutes while replication lag on one secondary climbs steadily. These are the signatures of oplog window collapse: a write surge turns over the oplog faster than secondaries can consume it, and the safety margin between window and lag evaporates.</p> <p>Once a secondary falls behind the oldest entry in the primary&rsquo;s oplog, its sync position no longer exists. Recovery requires a full initial sync, which can take hours to days depending on data size and network throughput. During recovery, the replica set runs with reduced redundancy. If another secondary is near the edge, the remaining members absorb increased read load that can push them toward the same fate.</p>MongoDB oplog window too small: sizing the oplog for your write volumehttps://www.netdata.cloud/guides/mongodb/mongodb-oplog-window-too-small/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-oplog-window-too-small/<p>The oplog window is the only thing standing between a routine secondary restart and a multi-hour full initial sync. It is a fixed-size capped collection that stores a variable amount of history. As your write volume grows, the window compresses. Most teams size the oplog once during initial deployment and never look at it again. Six months later, a routine maintenance window turns into an incident because the secondary fell off the oplog, entered RECOVERING, and forced a resync that saturated the remaining nodes.</p>MongoDB page faults high: working set exceeding memory after warmuphttps://www.netdata.cloud/guides/mongodb/mongodb-page-faults-high/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-page-faults-high/<p>A high page-fault rate long after startup can mean the active data set exceeds resident memory. <code>extra_info.page_faults</code> is platform-dependent; on Windows, MongoDB counts both hard and soft faults, so correlate the rate with OS-level disk-read/major-fault metrics. A brief spike after restart is normal during warmup, but sustained faults mean the working set does not fit. On EBS gp3, 50 faults per second can degrade latency. On NVMe, hundreds per second may be tolerable, but neither is free. Confirm the cause, distinguish warmup from pressure, and reduce the fault rate without guessing.</p>MongoDB rollback after failover: silent data loss and the rollback directoryhttps://www.netdata.cloud/guides/mongodb/mongodb-rollback-after-failover/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-rollback-after-failover/<p>A replica set member in <code>ROLLBACK</code> state, or an application reporting vanished documents after failover, means a former primary held writes that never reached a majority. When that node rejoins, MongoDB erases the divergent history and writes the removed data to files under <code>&lt;dbPath&gt;/rollback/</code>. The application may have received acknowledgment for those writes. With <code>w:1</code>, acknowledgment meant only that the primary applied the write. It did not guarantee replication to a majority or survival through failover. That is silent data loss.</p>MongoDB RSS growing without cache growth: leaks, threads, and tcmalloc fragmentationhttps://www.netdata.cloud/guides/mongodb/mongodb-memory-rss-growing/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-memory-rss-growing/<p><code>db.serverStatus().mem.resident</code> climbs while WiredTiger cache utilization stays flat and the host is not swapping. Virtual memory is larger than RSS by design and is not an alert target. Only RSS reflects physical memory pressure. When RSS grows without cache growth, the problem lives outside the storage engine.</p> <p>This pattern points to one of three areas: tcmalloc heap retention and fragmentation, per-connection thread stack accumulation, or unbounded internal allocations from cursors, plan caches, or aggregation pipelines. Each connection reserves roughly 1 MB of stack space, so a connection storm can add gigabytes of RSS in minutes. TCMalloc caches freed memory in per-thread or per-CPU arenas, which inflates RSS independently of the WiredTiger cache.</p>MongoDB silent index regression: when a dropped index quietly becomes a collection scanhttps://www.netdata.cloud/guides/mongodb/mongodb-silent-index-regression/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-silent-index-regression/<p>Read latency on the primary doubles while connection counts and write throughput stay flat. There are no election events or cache pressure alerts. Traffic is unchanged. Yet p99 read latency climbs until operations time out.</p> <p>The slow query log shows queries that used to finish in milliseconds now taking seconds. The plans show <code>COLLSCAN</code>. An index that existed last week is gone, or the query planner switched to a less efficient index after a cache invalidation. Because queries still return correct results, the regression is silent until it becomes an outage.</p>MongoDB slow query COLLSCAN: collection scans and the missing indexhttps://www.netdata.cloud/guides/mongodb/mongodb-slow-query-collscan/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-slow-query-collscan/<p>Queries that used to return in tens of milliseconds now breach application timeouts. Read latency climbs while write throughput stays flat. In the MongoDB slow query log, you see <code>planSummary: &quot;COLLSCAN&quot;</code> attached to operations that should be indexed. A collection scan reads documents that will never be returned, wastes disk I/O, floods the WiredTiger cache with irrelevant data, and holds read tickets until the whole instance cascades into cache pressure.</p>MongoDB ticket exhaustion: WiredTiger read/write tickets and queued operationshttps://www.netdata.cloud/guides/mongodb/mongodb-ticket-exhaustion/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-ticket-exhaustion/<p>Your application times out while the OS shows idle CPU and disk utilisation looks survivable. The MongoDB log shows no obvious errors, yet operations stall. The likely cause is WiredTiger ticket exhaustion: the storage engine has run out of read or write concurrency tokens, and new work queues behind slow operations. Confirm ticket starvation, find the root cause, and fix it without raising the ticket limit.</p> <h2 id="what-this-means">What this means</h2> <p>WiredTiger uses ticket-based admission control. Every operation that touches the storage engine must acquire a read or write ticket before it proceeds. In MongoDB 6.x and earlier, the default is 128 read and 128 write tickets per node. MongoDB 7.0 introduced a dynamic <code>throughputProbing</code> algorithm that adjusts the active ceiling downward from 128 under light load, scaling up under demand but never exceeding 128. In MongoDB 8.0+, the metrics moved from <code>wiredTiger.concurrentTransactions</code> to <code>queues.execution</code>, adding queue-length and timing fields that help distinguish true congestion from a low adaptive baseline.</p>MongoDB too stale to catch up: secondary stuck in RECOVERING and how to resynchttps://www.netdata.cloud/guides/mongodb/mongodb-too-stale-to-catch-up/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-too-stale-to-catch-up/<p>You check <code>rs.status()</code> during an incident and see a member stuck in <code>RECOVERING</code> with a stale-oplog error. Older releases reported <code>error RS102 too stale to catch up</code>; newer releases log <code>Too stale to catch up</code> and return <code>TooStaleToSyncFromSource</code> internally. The node is alive but will never transition back to <code>SECONDARY</code> on its own. Its last replicated oplog entry is older than the oldest entry still available on the primary, so the history it needs has already been overwritten. Incremental replication is impossible from this state. The only path forward is a full initial sync, which on large datasets can take hours to days, adds significant read load to the sync source, and leaves the cluster with reduced redundancy until it completes. If the stale member is a voting node, you are now one failure away from losing majority. This guide covers how to confirm the condition, identify why the secondary fell off, and recover without pushing the remaining cluster members into the same trap.</p>MongoDB WiredTiger cache dirty ratio high: the leading indicator nobody watcheshttps://www.netdata.cloud/guides/mongodb/mongodb-cache-dirty-ratio-high/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-cache-dirty-ratio-high/<p>Cache fill at 70% looks safe, but if dirty ratio is climbing past 15%, a latency spike is already forming. Dirty ratio measures modified pages not yet flushed to disk. While fill ratio tells you how much cache is in use, dirty ratio tells you how fast the storage engine is falling behind. It often leads checkpoint stalls and eviction-driven latency spikes by minutes.</p> <h2 id="what-this-means">What this means</h2> <p>WiredTiger tracks dirty bytes against the configured maximum cache size. Dirty ratio equals <code>tracked dirty bytes in the cache</code> divided by <code>maximum bytes configured</code>. Checkpoints run every 60 seconds by default to flush these pages. When write volume exceeds flush capacity, dirty data accumulates.</p>MongoDB WiredTiger cache pressure cascade: eviction stalls and latency spikeshttps://www.netdata.cloud/guides/mongodb/mongodb-cache-pressure-cascade/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mongodb/mongodb-cache-pressure-cascade/<p>Latency jumps from milliseconds to seconds for both reads and writes. The slow query log shows no single offender, but connection count climbs as clients retry and timeout. This is the cache pressure cascade. It starts in the storage engine and becomes a self-reinforcing spiral through replication, admission control, and connection handling. This guide covers the mechanism, confirmation under pressure, and how to stop it.</p> <h2 id="what-this-means">What this means</h2> <p>WiredTiger uses an in-memory cache separate from the OS page cache. The default maximum is the larger of 50% of (RAM − 1 GB), or 256 MB. Writes land in cache as dirty pages; checkpoints flush them to disk every 60 seconds by default. Background eviction threads keep cache fill near 80% and dirty pages under control.</p>Monit Monitoringhttps://www.netdata.cloud/monitoring-101/monit-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/monit-monitoring/<h2 id="monit-monitoring">Monit Monitoring</h2> <h3 id="what-is-monit">What Is Monit?</h3> <p>Monit is a small Open Source utility for managing and monitoring Unix systems. It conducts automatic maintenance and repair and can engage in stage-based escalation if there are problems.</p> <h3 id="monitoring-monit-with-netdata">Monitoring Monit With Netdata</h3> <p>Integrating the Monit monitoring tool with Netdata provides real-time, comprehensive monitoring of system services. With Netdata, you can visualize all the data that Monit collects, helping you monitor Monit and optimize your infrastructure more effectively. To see it in action, <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">check out our live demo</a>.</p>Monitoring 101https://www.netdata.cloud/monitoring-101/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/Mosquitto Monitoringhttps://www.netdata.cloud/monitoring-101/mosquitto-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/mosquitto-monitoring/<h2 id="mosquitto-monitoring">Mosquitto Monitoring</h2> <h3 id="what-is-mosquitto">What Is Mosquitto?</h3> <p>Mosquitto is a lightweight MQTT broker, designed to facilitate IoT communications efficiently. As a central hub for sending and receiving messages, Mosquitto ensures that devices can publish and subscribe to channels seamlessly, making it a critical component for IoT infrastructure and applications.</p> <h3 id="monitoring-mosquitto-with-netdata">Monitoring Mosquitto With Netdata</h3> <p>Monitoring Mosquitto can enhance your IoT message transport and system performance. By using Netdata, you can effectively monitor Mosquitto with ease. Netdata utilizes an openmetrics (Prometheus) exporter to gather and ingest data from the <a href="https://github.com/sapcc/mosquitto-exporter">Mosquitto exporter</a>. This allows users to enjoy automated dashboards and alerts, without the need for a standalone Prometheus server or Grafana setup.</p>MQTT Blackbox Monitoringhttps://www.netdata.cloud/monitoring-101/mqtt_blackbox-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/mqtt_blackbox-monitoring/<h2 id="mqtt-blackbox-monitoring">MQTT Blackbox Monitoring</h2> <h3 id="what-is-mqtt-blackbox">What Is MQTT Blackbox?</h3> <p>MQTT Blackbox is a specialized monitoring technique designed to test and track the performance of MQTT message transport using blackbox testing methods. It leverages the MQTT Blackbox Exporter to simulate client interactions and analyze the reliability and efficiency of message brokers in real-time.</p> <h3 id="monitoring-mqtt-blackbox-with-netdata">Monitoring MQTT Blackbox With Netdata</h3> <p>Netdata excels at comprehensive MQTT Blackbox monitoring by utilizing an openmetrics (prometheus) exporter. With Netdata, you can effortlessly ingest data from any Prometheus exporter, eliminating the need for a Prometheus server or Grafana. This integration provides users with automated dashboards, real-time alerts, and more, making it an incredibly efficient tool for monitoring MQTT Blackbox.</p>Mtail Monitoringhttps://www.netdata.cloud/monitoring-101/mtail-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/mtail-monitoring/<h2 id="mtail-monitoring">Mtail Monitoring</h2> <h3 id="what-is-mtail">What Is Mtail?</h3> <p>Mtail is a vital tool used for extracting and parsing log data. Developed by Google, Mtail assists in monitoring and showcasing real-time logs. This is particularly beneficial for DevOps, SREs, and IT professionals who need to ensure the smooth operation of systems through log data metrics. Mtail acts as a log data extractor tailored to plug gaps in monitoring solutions, perfect for complex environments.</p> <h3 id="monitoring-mtail-with-netdata">Monitoring Mtail With Netdata</h3> <p>Netdata offers a seamlessly integrated environment to monitor mtail using the OpenMetrics (Prometheus) exporter. Netdata&rsquo;s advanced platform can ingest data from any Prometheus exporter, providing automated dashboards, alerts, and visualizations without the need for a Prometheus server or Grafana. This attribute makes Netdata an exceptional mtail monitoring tool.</p>MySQL Aborted Connections: Causes And Fixeshttps://www.netdata.cloud/guides/mysql/mysql-aborted-connections/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-aborted-connections/<p>You notice <code>Aborted_connects</code> or <code>Aborted_clients</code> climbing on a production MySQL instance. Because these are cumulative counters, a steady upward slope means something is actively failing or dropping connections. In a busy system, a rising <code>Aborted_connects</code> rate can trigger host blocking via <code>max_connect_errors</code>, suddenly preventing legitimate clients from connecting. A rising <code>Aborted_clients</code> rate usually shows up as application-side exceptions about closed connections, forcing retries that can cascade into connection exhaustion. The two counters track completely different failure modes: <code>Aborted_connects</code> counts connection attempts that never finished authentication; <code>Aborted_clients</code> counts connections that authenticated but then died unexpectedly. Treating them as the same metric leads to wrong fixes. Restarting the network stack will not fix a credential rotation bug, and increasing <code>max_connections</code> will not fix a client killed by <code>wait_timeout</code>.</p>MySQL Binary Log Disk Full: How To Fix Ithttps://www.netdata.cloud/guides/mysql/mysql-binary-log-disk-full/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-binary-log-disk-full/<p>You get a disk-full alert on the MySQL primary. <code>df -h</code> shows the data partition at 95%, and <code>du</code> points to <code>/var/lib/mysql/binlog.*</code> consuming hundreds of gigabytes. Writes are about to fail.</p> <p>Binary logs are append-only. MySQL rotates to a new file at <code>max_binlog_size</code> (default 1 GB), but rotation does not delete old files. Deletion only happens via automatic expiry or <code>PURGE BINARY LOGS</code>. MySQL refuses to delete any binlog file that a connected replica has not yet consumed. In MySQL 5.7, the default expiry is never (<code>expire_logs_days = 0</code>). In 8.0, the default is 30 days, but automatic purge cannot remove files that a connected replica still needs. A replica lagging past the expiry window therefore causes unbounded growth.</p>MySQL connection exhaustion: detection, diagnosis, and preventionhttps://www.netdata.cloud/guides/mysql/mysql-connection-exhaustion/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-connection-exhaustion/<p>ERROR 1040 (HY000): Too many connections. Health checks fail. Users cannot sign in. If you configured an admin account correctly, a break-glass session may still get through on the reserved slot, and <code>SELECT 1</code> returns. MySQL is running, but the connection pool is a wall.</p> <p>This is a hard cliff. One moment queries flow; the next, every new TCP handshake to port 3306 is rejected. The server does not queue connections. Whether the root cause is a connection leak, a retry storm, or genuine overload from slow queries, the symptom is the same: <code>Threads_connected</code> has reached <code>max_connections</code>.</p>MySQL ERROR 1040 (HY000): Too many connections - causes and fixeshttps://www.netdata.cloud/guides/mysql/mysql-too-many-connections/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-too-many-connections/<p>Once <code>Threads_connected</code> reaches <code>max_connections</code>, MySQL returns <code>ERROR 1040 (HY000)</code> to every new connection attempt before authentication. The server is not down; it is full.</p> <p>This error is usually a symptom. Connections may be leaking from the application, a cache stampede may have flooded the pool, or slow queries may be holding slots open longer than expected. MySQL reserves one extra connection for users with <code>CONNECTION_ADMIN</code> (or the deprecated <code>SUPER</code> privilege). If that slot is free, an operator can still connect. If an app user has taken it, you may need to restart.</p>MySQL ERROR 1045 (28000): Access denied for user - diagnosishttps://www.netdata.cloud/guides/mysql/mysql-access-denied-for-user/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-access-denied-for-user/<p>When you see <code>ERROR 1045 (28000): Access denied for user 'app'@'10.0.0.5' (using password: YES)</code>, the connection never reached the query parser. MySQL rejected it during authentication, incremented <code>Aborted_connects</code>, and returned SQLSTATE <code>28000</code>. The error always includes the effective user and host as seen by the server. This is your first and most important clue.</p> <p>This error has four root causes in production: wrong credentials, user@host mismatch, authentication plugin incompatibility, and host-level blocking from accumulated connection errors. A brute-force probe and a misconfigured deploy look identical from the server side, so diagnosis hinges on correlating the error pattern with connection metrics and the host cache.</p>MySQL ERROR 1205: Lock wait timeout exceeded; try restarting transactionhttps://www.netdata.cloud/guides/mysql/mysql-lock-wait-timeout-exceeded/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-lock-wait-timeout-exceeded/<p><code>ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction</code> appears when one transaction holds an InnoDB row lock so long that another transaction exhausts <code>innodb_lock_wait_timeout</code> (default 50 seconds). Unlike a deadlock, which InnoDB resolves automatically, a timeout means a blocker is still active. The root cause is almost always a long-running transaction or hot row contention. Find it before it cascades into a wider outage.</p> <p>This error applies only to InnoDB row-level locks. Metadata lock waits from DDL operations show <code>Waiting for table metadata lock</code> in <code>SHOW PROCESSLIST</code> and are governed by <code>lock_wait_timeout</code>, not <code>innodb_lock_wait_timeout</code>. Table-level locks are also separate. If you see ERROR 1205, you are dealing with row-level contention inside InnoDB.</p>MySQL ERROR 1213: Deadlock found when trying to get lock; try restarting transactionhttps://www.netdata.cloud/guides/mysql/mysql-deadlock-found/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-deadlock-found/<p>Your application logs show <code>ERROR 1213 (40001): Deadlock found when trying to get lock; try restarting transaction</code>. One transaction was rolled back; the other completed normally. InnoDB broke a circular lock wait by selecting the cheaper transaction as the victim. Occasional deadlocks (less than one per hour) in high-concurrency OLTP are normal. A sustained storm is not: it means transactions are colliding under load.</p> <p>The error is raised instantly. There is no timeout. InnoDB detects the cycle in the wait-for graph and rolls back the victim before either transaction waits. Without retry logic, users see failures. With retry logic, a high deadlock rate burns CPU and latency on repeated attempts.</p>MySQL ERROR 2006/2013: MySQL server has gone away -- causes and fixeshttps://www.netdata.cloud/guides/mysql/mysql-server-has-gone-away/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-server-has-gone-away/<p>ERROR 2006 (CR_SERVER_GONE_ERROR) and ERROR 2013 (CR_SERVER_LOST) produce the messages &ldquo;MySQL server has gone away&rdquo; and &ldquo;Lost connection during query.&rdquo; They often appear together, but they indicate different failures. ERROR 2006 means the server closed a connection the client believed was valid. ERROR 2013 means the connection dropped while a query was executing or results were transferring.</p> <p>Treating them identically leads to incorrect fixes. Raising <code>max_connections</code> does not stop idle timeouts. Tuning timeouts does not fix an OOM kill. Before changing configuration, determine whether the MySQL process restarted. A stable process points to timeout or packet mismatches. A restarted process points to a crash or memory exhaustion.</p>MySQL FLUSH TABLES WITH READ LOCK stall: backups that freeze the serverhttps://www.netdata.cloud/guides/mysql/mysql-flush-tables-with-read-lock-stall/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-flush-tables-with-read-lock-stall/<p>Your application suddenly cannot write. <code>Threads_connected</code> climbs toward <code>max_connections</code>, but <code>Questions</code> flatlines. The last change was a backup job that started ten minutes ago. The culprit is almost always <code>FLUSH TABLES WITH READ LOCK</code> (FTWRL), and the damage is caused not by the lock itself but by what happens while the server waits to acquire it.</p> <p>FTWRL is triggered by <code>mysqldump --master-data</code>, <code>mysqldump --lock-tables</code>, and similar tools that need a consistent logical backup. It attempts to close all open tables and acquire a global read lock. While it waits for a long-running query to finish, new writes are already blocked. The result is a whole-server freeze: the query rate drops to zero, connections pile up, and the application sees cascading timeouts.</p>MySQL full table scans: Handler_read_rnd_next and the missing indexhttps://www.netdata.cloud/guides/mysql/mysql-full-table-scans/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-full-table-scans/<p>You get paged because query latency is spiking. <code>Slow_queries</code> is climbing. <code>Handler_read_rnd_next</code> has jumped five-fold over its baseline and keeps rising. Connections, CPU, and buffer pool hit ratio look fine. The culprit is usually a new full table scan after a deploy, schema change, or query pattern shift.</p> <p><code>Handler_read_rnd_next</code> increments when the storage engine reads the next row during a table scan or sorted retrieval. In a healthy OLTP system, <code>Handler_read_key</code> dominates and <code>Handler_read_rnd_next</code> stays flat relative to query volume. When the ratio inverts, you are looking at a query plan regression, a missing index, or an optimizer decision gone wrong.</p>MySQL Got error 28 from storage engine / No space left on device — recoveryhttps://www.netdata.cloud/guides/mysql/mysql-disk-full-no-space-left/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-disk-full-no-space-left/<p>When <code>Got error 28 from storage engine</code> appears, the underlying filesystem is at 100%. MySQL needs writable space for InnoDB data files, redo logs, binary logs, temporary tables, relay logs, and slow query logs. Writes fail immediately. Affected threads enter a retry loop, logging warnings until an operator frees space or kills the operation.</p> <p>The most dangerous scenario is the redo log filling up. If checkpoint age approaches capacity, InnoDB forces aggressive synchronous flushing. Under sustained pressure this can trigger an unclean shutdown and crash recovery on restart. Replicas are similarly vulnerable: a full relay log partition stops the I/O thread and lets lag grow unboundedly, risking binlog expiry on the source before catch-up.</p>MySQL GTID errant transactions: detecting replication divergencehttps://www.netdata.cloud/guides/mysql/mysql-gtid-errant-transactions/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-gtid-errant-transactions/<p>Before a planned failover, or after an orchestrator aborts with a GTID consistency error, replication can appear healthy: <code>SHOW REPLICA STATUS</code> reports both threads running, <code>Seconds_Behind_Source</code> is near zero, and the error log is quiet. Yet comparing GTID sets between source and replica reveals mismatching numbers. Errant transactions are GTIDs present in a replica&rsquo;s <code>gtid_executed</code> set that the source never generated.</p> <p>Ordinary lag resolves as the replica catches up. Errant transactions represent true divergence. Promoting a replica with extra GTIDs propagates those transactions into the new source and downstream replicas, creating split-brain that is expensive to reverse. This guide covers distinguishing benign lag from dangerous divergence, pinpointing offending GTIDs, and deciding between empty-transaction injection and a full rebuild.</p>MySQL InnoDB buffer pool hit ratio collapse: the cliff edgehttps://www.netdata.cloud/guides/mysql/mysql-buffer-pool-hit-ratio-collapse/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-buffer-pool-hit-ratio-collapse/<p>Your OLTP queries were running in single-digit milliseconds. Now every query is taking seconds, the disk subsystem is saturated, <code>Threads_running</code> is climbing toward <code>max_connections</code>, and the buffer pool hit ratio, which sat at 99.9% for months, just fell through 95% and keeps dropping.</p> <p>This is the InnoDB buffer pool cliff edge. When the working set exceeds the buffer pool, pages are evicted before they can be reused. Every miss becomes a physical disk read. The degradation is non-linear: 99.9% to 99% is a slow bleed, 99% to 95% is rapid, and below 95% disk saturation, uniform latency inflation, and connection exhaustion turn a capacity problem into an availability incident.</p>MySQL InnoDB checkpoint age: the redo log capacity signal nobody watcheshttps://www.netdata.cloud/guides/mysql/mysql-checkpoint-age-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-checkpoint-age-monitoring/<p>Checkpoint age is the distance between the current InnoDB log sequence number (LSN) and the last checkpoint LSN. It measures how much of the circular redo log is occupied by changes not yet flushed to data files. When this age approaches redo log capacity, InnoDB escalates flushing aggressiveness until it runs out of options and stalls all writes.</p> <p>Standard MySQL does not expose <code>Innodb_checkpoint_age</code> as a status variable. Depending on version, you must parse <code>SHOW ENGINE INNODB STATUS</code>, enable a disabled-by-default <code>INNODB_METRICS</code> counter, or compute the delta from MySQL 8.0.30+ redo status variables. MySQL 8.0.30 replaced <code>innodb_log_file_size</code> and <code>innodb_log_files_in_group</code> with <code>innodb_redo_log_capacity</code>. When the new variable is unset, MySQL computes capacity from the legacy settings at startup (<code>innodb_log_files_in_group</code> × <code>innodb_log_file_size</code>); if neither is set, it uses the <code>innodb_redo_log_capacity</code> default of 100 MB.</p>MySQL InnoDB history list length growing: purge lag explainedhttps://www.netdata.cloud/guides/mysql/mysql-history-list-length-growing/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-history-list-length-growing/<p>If query latency climbs across every table and no single query stands out, check the InnoDB history list length. It tracks unpurged undo records: MVCC debt. When purge falls behind, every consistent read walks longer version chains, and the slowdown is global. Unlike a slow query, this debt is invisible to conventional query analysis.</p> <p>In MySQL 8.0, the programmatic source for this metric is <code>trx_rseg_history_len</code> in <code>information_schema.INNODB_METRICS</code>. Despite being labeled <code>status_counter</code> in the metrics table, <code>trx_rseg_history_len</code> behaves as a gauge: it rises when purge lags and falls when purge catches up.</p>MySQL InnoDB redo log checkpoint stall: when all writes freezehttps://www.netdata.cloud/guides/mysql/mysql-redo-log-checkpoint-stall/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-redo-log-checkpoint-stall/<p>InnoDB redo log checkpoint stalls freeze all writes synchronously when checkpoint age reaches the end of the circular redo log. INSERTs, UPDATEs, and DELETEs that complete in milliseconds hang for seconds. <code>Threads_running</code> climbs while the <code>Questions</code> rate collapses. Read queries may still return initially, but soon every connection waits for a write lock or commit acknowledgment. Then throughput recovers just as abruptly. This is not a disk failure, deadlock, or runaway query. It is MySQL&rsquo;s write path running out of runway.</p>MySQL InnoDB row lock contention: finding who blocks whomhttps://www.netdata.cloud/guides/mysql/mysql-row-lock-contention/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-row-lock-contention/<p>Queries that normally finish in milliseconds take seconds. <code>Threads_running</code> climbs while <code>Questions</code> stalls. <code>SHOW PROCESSLIST</code> shows active threads, yet the database is frozen. That is the shape of InnoDB row lock contention: transactions are waiting to release row-level locks, and the queue is growing.</p> <p>Row lock contention differs from a metadata lock cascade. Metadata locks block DDL and DML at the table level and live in <code>performance_schema.metadata_locks</code>. Row locks are held by open InnoDB transactions and block at the row, gap, or next-key level. Rising <code>Innodb_row_lock_current_waits</code> alongside rising <code>Threads_running</code> signals a live contention crisis. The goal is to identify the blocker, the waiter, and the lock footprint so you can break the chain without guessing.</p>MySQL innodb_buffer_pool_size tuning: 60-80% of RAM and when that breakshttps://www.netdata.cloud/guides/mysql/mysql-buffer-pool-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-buffer-pool-sizing/<p>The 60-80% rule works for a bare-metal host running only MySQL. In containers, shared hardware, and high-connection-count environments, it is a hazard. Size the pool against aligned allocation, cgroup limits, per-connection memory, and OS headroom. Do not size it as a percentage of total RAM.</p> <h2 id="what-the-buffer-pool-costs">What the buffer pool costs</h2> <p>InnoDB caches data and index pages in a fixed-size pool. Every read and write touches it. When the working set fits entirely in memory, queries avoid disk. When it does not, InnoDB evicts pages and disk reads dominate latency.</p>MySQL Innodb_buffer_pool_wait_free > 0: buffer pool memory pressurehttps://www.netdata.cloud/guides/mysql/mysql-buffer-pool-wait-free/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-buffer-pool-wait-free/<p><code>Innodb_buffer_pool_wait_free</code> increments when InnoDB must synchronously flush dirty pages to make room for new reads. A sustained nonzero rate means queries are waiting on disk writes before they can proceed. Unlike the buffer pool hit ratio, which can stay above 99% while the system stalls, <code>wait_free</code> confirms the buffer pool is operating at its limit.</p> <p>This is the Buffer Pool Cliff pattern: once the working set exceeds available clean pages, performance degrades non-linearly, disk I/O saturates, and threads pile up.</p>MySQL innodb_redo_log_capacity sizing: how big should the redo log behttps://www.netdata.cloud/guides/mysql/mysql-redo-log-capacity-sizing/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-redo-log-capacity-sizing/<p>An undersized InnoDB redo log is a common cause of MySQL write stalls. When redo generation outpaces dirty-page flushing, checkpoint age advances until InnoDB enters synchronous flushing and user writes block.</p> <p>Since MySQL 8.0.30, <code>innodb_redo_log_capacity</code> replaces <code>innodb_log_file_size</code> and <code>innodb_log_files_in_group</code>. Resizing no longer requires a restart, but the sizing logic is unchanged: capacity must absorb peak write rates without pushing checkpoint age into the synchronous-flush zone.</p> <h2 id="what-it-is-and-why-it-matters">What it is and why it matters</h2> <p>InnoDB is a write-ahead log engine. Modifications append redo records before dirty pages are written to data files. The redo log is circular: once the oldest entries are flushed during a checkpoint, that space is recycled.</p>MySQL long-running transactions: detecting and killing the silent blockerhttps://www.netdata.cloud/guides/mysql/mysql-long-running-transactions/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-long-running-transactions/<p><code>Threads_running</code> climbs. A DDL operation that should take seconds is stuck for minutes. Storage grows steadily with no matching data increase. The cause is often a single idle transaction in <code>INNODB_TRX</code>, holding row locks and an MVCC read view long after its last query finished. It does not appear in the slow query log and may have no active query string. Left alone, it blocks InnoDB purge, inflates the history list, and can trigger a metadata lock cascade that fills the connection pool.</p>MySQL metadata lock cascade: how one ALTER TABLE freezes a whole tablehttps://www.netdata.cloud/guides/mysql/mysql-metadata-lock-cascade/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-metadata-lock-cascade/<p>You run an <code>ALTER TABLE</code> to add an index. Seconds later, health checks fail for queries that touch only that table. Other tables work fine. CPU and disk are idle. The connection pool fills. <code>SHOW ENGINE INNODB STATUS</code> shows no row lock waits. The culprit is a metadata lock cascade, not InnoDB contention.</p> <p>This happens when DDL requests an exclusive metadata lock (MDL) on a table already protected by a shared MDL held by a long-running or idle transaction. The DDL waits. Subsequent DML on that table queues behind it. The queue grows until the connection pool exhausts and the application times out. Because the outage is isolated to one table and leaves no trace in InnoDB lock metrics, it is easy to misdiagnose as a network blip or a runaway query.</p>MySQL Monitoringhttps://www.netdata.cloud/monitoring-101/mysql-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/mysql-monitoring/<h2 id="mysql-monitoring">MySQL Monitoring</h2> <h3 id="what-is-mysql">What Is MySQL?</h3> <p><a href="https://www.mysql.com/">MySQL</a> is a widely-used open-source relational database management system. It is a crucial component in web application architecture and is known for its reliability, scalability, and performance. MySQL supports a variety of database-driven applications by enabling efficient storage, retrieval, and management of data.</p> <h3 id="monitoring-mysql-with-netdata">Monitoring MySQL With Netdata</h3> <p>Netdata offers real-time, insightful metrics and monitoring capabilities required for effective MySQL monitoring. With Netdata, you gain access to detailed visualizations and alerts to ensure that your MySQL server operates optimally. This is achieved via <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/mysql/">Netdata&rsquo;s MySQL monitoring tool</a> which seamlessly integrates and enables deep analytics of your MySQL instances.</p>MySQL monitoring checklist: the signals every production instance needshttps://www.netdata.cloud/guides/mysql/mysql-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-monitoring-checklist/<p>Most production incidents involving MySQL stem from missing observability into specific internal subsystems. Connection saturation, buffer pool thrashing, and replication lag can degrade a healthy cluster into an outage if the right signals are not monitored.</p> <p>This checklist serves as a tiered operational reference for senior engineers and SREs. It defines the exact metrics needed to keep MySQL instances available, fast, and reliable, scaling from basic survival metrics to expert-level internals. Use it to validate existing dashboards or baseline monitoring for a new deployment.</p>MySQL online DDL still blocking: ALGORITHM, LOCK, and the copy phasehttps://www.netdata.cloud/guides/mysql/mysql-online-ddl-blocking/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-online-ddl-blocking/<p>Online DDL in MySQL is not lock-free. Even with <code>ALGORITHM=INPLACE</code> or <code>ALGORITHM=INSTANT</code>, and even with <code>LOCK=NONE</code>, every online DDL operation passes through a brief window where it upgrades its metadata lock (MDL) to exclusive. That window is short, but it is real, and it is the single most common reason an &ldquo;online&rdquo; schema change still stalls a busy production table.</p> <p>This article explains the three-phase MDL model that online DDL uses, why <code>ALGORITHM=INPLACE</code> with <code>LOCK=NONE</code> can still block, what the copy phase actually does, and how third-party tools such as <code>pt-online-schema-change</code> and <code>gh-ost</code> change the picture. It assumes you already understand the broader MySQL mental model. See the hub page for the failure-pattern catalogue that frames metadata lock stalls as one of MySQL&rsquo;s characteristic outage archetypes.</p>MySQL OOM-killed: buffer pool, per-connection buffers, and the kernel killerhttps://www.netdata.cloud/guides/mysql/mysql-out-of-memory-oom-killed/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-out-of-memory-oom-killed/<p>MySQL disappears. Application logs fill with connection timeouts. <code>Uptime</code> resets to near zero. In the kernel log: <code>oom-kill: task mysqld</code> and its anonymous RSS. Orchestrators mark the pod <code>OOMKilled</code> (exit code 137). To the application, this is a crash. To the kernel, mysqld was the largest memory consumer and the system ran out.</p> <p>OOM kills are gradual, then catastrophic. Memory pressure builds as connections open, temp tables materialize, and dirty pages accumulate. The buffer pool is the obvious consumer, but the killer often enters through the back door: a connection burst multiplies per-thread buffers, a container limit sits too close to the buffer pool size, or Transparent Huge Pages block reclamation. Map all allocators to prevent recurrence.</p>MySQL purge lag from an idle transaction: the slow bleedhttps://www.netdata.cloud/guides/mysql/mysql-purge-lag-idle-transaction/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-purge-lag-idle-transaction/<p>Your OLTP workload slows over hours. No single query dominates the slow log. CPU and disk I/O are not saturated. Yet read latency climbs, throughput drifts downward, and the undo tablespace grows. The culprit is often a single idle transaction that opened a read view and never closed it. Under InnoDB&rsquo;s default REPEATABLE READ isolation, that transaction pins the purge boundary. Every subsequent write appends to the undo log. The history list length grows without bound, and all MVCC reads traverse longer version chains.</p>MySQL query plan regression: when a query gets slow after a deploy or ANALYZEhttps://www.netdata.cloud/guides/mysql/mysql-query-plan-regression/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-query-plan-regression/<p>A query that completed in milliseconds yesterday now times out. The deploy was clean, or maybe someone ran ANALYZE TABLE during maintenance. Slow_queries climbs, Handler_read_rnd_next jumps, and the same application code suddenly kills the database. The optimizer has changed how it executes one or more queries, and the new plan is far more expensive.</p> <p>Plan regressions are sharp step-changes, not gradual growth. They correlate tightly with specific events: a schema migration, an index drop, a bulk load that triggered auto-recalc, a manual ANALYZE TABLE, or a MySQL version upgrade. The cause is usually stale or shifted statistics, an optimizer behavior change, or a missing index the optimizer can no longer use.</p>MySQL Replica_IO_Running / Replica_SQL_Running not Yes: replication stoppedhttps://www.netdata.cloud/guides/mysql/mysql-replica-io-sql-thread-stopped/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-replica-io-sql-thread-stopped/<p><code>SHOW REPLICA STATUS\G</code> (MySQL 8.0.22+) or <code>SHOW SLAVE STATUS\G</code> (MySQL 5.7) shows <code>Replica_IO_Running</code> or <code>Replica_SQL_Running</code> is not <code>Yes</code>. The IO thread may hang in <code>Connecting</code>, or the SQL thread may stop with an error. Replication no longer makes progress. Lag grows without bound, and if the source purges binary logs before recovery, you face a full rebuild.</p> <p>Unlike many MySQL problems, a stopped replication thread does not self-heal. The SQL thread halts on the first apply error and waits for operator intervention. The IO thread retries automatically, but only up to the configured retry limit. <code>Seconds_Behind_Source</code> can show <code>0</code> even when the IO thread is disconnected and the SQL thread has consumed the relay log, so lag alone is not a reliable health signal.</p>MySQL replication lag spiral: Seconds_Behind_Source growing without boundhttps://www.netdata.cloud/guides/mysql/mysql-replication-lag-spiral/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-replication-lag-spiral/<p>You check <code>SHOW REPLICA STATUS</code> and see <code>Seconds_Behind_Source</code> is not just elevated; it is climbing. Five minutes ago it was 60. Now it is 120. The replica is not catching up; it is falling further behind.</p> <p>This is a replication lag death spiral. The SQL apply thread (or threads) cannot replay events as fast as the source generates them. Relay logs accumulate. Lag compounds because longer apply queues mean larger effective transactions, longer lock holds, and greater exposure to blocking queries on the replica.</p>MySQL slow commits with idle CPU: redo and binlog fsync pressurehttps://www.netdata.cloud/guides/mysql/mysql-fsync-pressure-slow-commits/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-fsync-pressure-slow-commits/<p>Slow commits or transaction timeouts with idle CPU usually mean the bottleneck is in the durability path, not the query engine.</p> <p>With <code>innodb_flush_log_at_trx_commit=1</code> and <code>sync_binlog=1</code>, every <code>COMMIT</code> triggers an InnoDB redo log <code>fsync()</code> and a binary log <code>fsync()</code> before returning to the client. These are sequential, latency-bound operations. When storage cannot drain fsync requests as fast as the server generates them, commits queue up while the CPU waits.</p> <p>This is not a checkpoint stall. A checkpoint stall happens when the redo log fills and InnoDB must flush dirty pages synchronously to reclaim log capacity. Fsync pressure happens when the log flusher thread cannot complete <code>fsync()</code> calls fast enough to keep up with the commit rate, even though redo log capacity is abundant. Check <code>Innodb_os_log_pending_fsyncs</code> to tell the difference.</p>MySQL slow queries: from Slow_queries to the slow log to the fixhttps://www.netdata.cloud/guides/mysql/mysql-slow-queries-diagnosis/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-slow-queries-diagnosis/<p>When <code>Slow_queries</code> climbs but the slow log is empty, or <code>long_query_time</code> is still at the default 10 seconds, you have an instrumentation gap. <code>Slow_queries</code> increments regardless of whether <code>slow_query_log</code> is <code>ON</code>, so a rising counter with no log detail is a dead end.</p> <p>This guide moves from the status counter to slow log configuration, then to <code>performance_schema</code> digests, and finally to resource signals that explain why queries slowed. The goal is to help you decide in minutes whether you face a query plan regression, lock contention, buffer pool pressure, or a configuration gap.</p>MySQL Waiting for table metadata lock: diagnosing the DDL stallhttps://www.netdata.cloud/guides/mysql/mysql-waiting-for-table-metadata-lock/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/mysql/mysql-waiting-for-table-metadata-lock/<p>You run <code>SHOW PROCESSLIST</code> and see a wall of threads in <code>Waiting for table metadata lock</code>. An <code>ALTER TABLE</code> that should finish in seconds hangs for minutes. Queries against one table stop returning, the application connection pool drains, and CPU and disk look calm. This is a metadata lock (MDL) stall. It is a queueing failure, not resource exhaustion. Left alone, it cascades into connection exhaustion and a partial outage where every other table continues to work normally.</p>Nagios Monitoringhttps://www.netdata.cloud/monitoring-101/nagios-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/nagios-monitoring/<h2 id="nagios-monitoring">Nagios Monitoring</h2> <h3 id="what-is-nagios">What Is Nagios?</h3> <p>Nagios is a powerful, enterprise-grade IT infrastructure monitoring solution. It enables organizations to identify and rectify problems related to networks, systems, and applications by alerting users of the fault instances to ensure your IT systems are running efficiently. With a strong reputation in the field of <a href="https://www.nagios.org/">network monitoring</a> and <a href="https://www.nagios.com/about/">performance management</a>, Nagios has been a go-to solution for IT admins and engineers wanting to monitor critical IT infrastructure components.</p>NAT and session-table exhaustion: catching it before connections failhttps://www.netdata.cloud/guides/network/network-nat-session-table-exhaustion/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-nat-session-table-exhaustion/<p>New connections fail while existing ones keep working. Applications report &ldquo;connection refused&rdquo; or timeouts. Open SSH sessions stay alive, but new SSH attempts hang. Your monitoring shows the firewall or NAT gateway is up, interfaces are healthy, and CPU is normal. The session or NAT translation table is full.</p> <p>Session-table exhaustion is a cliff-edge failure. The table degrades gracefully until it hits its limit, then every new connection is denied. Existing flows continue because their entries are already in the table. The symptom pattern is distinctive but easy to misdiagnose as application failure, DNS issues, or upstream provider problems, because the applications are the ones reporting errors.</p>NATS Monitoringhttps://www.netdata.cloud/monitoring-101/nats-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/nats-monitoring/<h2 id="nats-monitoring">NATS Monitoring</h2> <h3 id="what-is-nats">What Is NATS?</h3> <p><a href="https://nats.io/">NATS</a> is a high-performance messaging system that enables distributed applications to generate and consume microservices in a seamless manner. It is widely used in various industries for cloud, IoT, and edge applications due to its lightweight and scalable architecture.</p> <h3 id="monitoring-nats-with-netdata">Monitoring NATS With Netdata</h3> <p>Netdata offers a cutting-edge NATS monitoring tool that provides real-time insights into the performance and health of your NATS servers. By leveraging Netdata&rsquo;s capabilities, organizations can keep their messaging infrastructure efficient and reliable. For an interactive experience, you can try out our <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">Live Demo</a>.</p>Nature Remo E lite devices Monitoringhttps://www.netdata.cloud/monitoring-101/nature_remo-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/nature_remo-monitoring/<h2 id="nature-remo-monitoring">Nature Remo Monitoring</h2> <h3 id="what-is-nature-remo">What Is Nature Remo?</h3> <p>Nature Remo E lite devices are innovative smart home solutions designed to enhance home automation and energy management. These devices enable you to control your home environment, focusing on convenience and efficiency, by integrating seamlessly into your smart home ecosystem.</p> <h3 id="monitoring-nature-remo-with-netdata">Monitoring Nature Remo With Netdata</h3> <p>To monitor Nature Remo, Netdata employs an openmetrics (Prometheus) exporter, allowing the ingestion of data from any Prometheus exporter. This setup ensures you get automated dashboards, real-time alerts, and a comprehensive monitoring experience without needing a Prometheus server or Grafana. <a href="https://github.com/kenfdev/remo-exporter">Get the community exporter here</a> to easily set up Nature Remo monitoring.</p>NetApp ONTAP API Monitoringhttps://www.netdata.cloud/monitoring-101/netapp_ontap-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/netapp_ontap-monitoring/<h2 id="netapp-ontap-api-monitoring">NetApp ONTAP API Monitoring</h2> <h3 id="what-is-netapp-ontap-api">What Is NetApp ONTAP API?</h3> <p>NetApp ONTAP API, renowned for its robust data management capabilities, is a storage operating system designed to efficiently manage and protect petabytes of data. Its performance directly impacts storage efficiency, making it essential for technical professionals, such as DevOps, IT admins, and SREs, to keep an attentive eye on its metrics. Monitoring the performance and health of the NetApp ONTAP API is critical in ensuring data integrity and optimizing storage functionalities.</p>NetApp Solidfire Monitoringhttps://www.netdata.cloud/monitoring-101/netapp_solidfire-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/netapp_solidfire-monitoring/<h2 id="netapp-solidfire-monitoring">NetApp Solidfire Monitoring</h2> <h3 id="what-is-netapp-solidfire">What Is NetApp Solidfire?</h3> <p>NetApp Solidfire is a high-performing storage solution designed to manage data efficiently across your storage infrastructure. It provides seamless data handling capabilities that ensure optimal resource allocation and management. Solidfire is instrumental in handling workloads with demanding storage and performance requirements.</p> <h3 id="monitoring-netapp-solidfire-with-netdata">Monitoring NetApp Solidfire With Netdata</h3> <p>When it comes to monitoring NetApp Solidfire, Netdata takes advantage of an openmetrics (Prometheus) exporter. The <a href="https://github.com/mjavier2k/solidfire-exporter">NetApp Solidfire Exporter</a> is utilized to gather pertinent metrics, which are essential for monitoring and enhancing overall system performance.</p>Netatmo Sensors Monitoringhttps://www.netdata.cloud/monitoring-101/netatmo-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/netatmo-monitoring/<h2 id="netatmo-sensors-monitoring">Netatmo Sensors Monitoring</h2> <h3 id="what-are-netatmo-sensors">What Are Netatmo Sensors?</h3> <p>Netatmo sensors are a range of smart home devices designed to monitor environmental conditions such as temperature, humidity, and air quality. These IoT devices play a crucial role in home automation and energy management, enabling users to adapt their environments for comfort and efficiency.</p> <h3 id="monitoring-netatmo-sensors-with-netdata">Monitoring Netatmo Sensors With Netdata</h3> <p>Effective tools for monitoring Netatmo Sensors are essential for ensuring optimal performance and timely insights. Netdata provides a comprehensive solution for monitoring Netatmo Sensors without the complexity of setting up separate Prometheus servers or Grafana dashboards. By using an openmetrics (Prometheus) exporter, Netdata can ingest data from the <a href="https://github.com/xperimental/netatmo-exporter">Netatmo exporter</a>, offering automated dashboards and alerts to keep track of your smart home devices&rsquo; performance in real time.</p>Netdata at AWS Cloud Days 2023https://www.netdata.cloud/events/aws-cloud-days-2023/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/aws-cloud-days-2023/<p>Ralph Meijer, VP of Technology at Netdata, joined a panel at AWS Cloud Days Athens 2023 on October 10. The session, &ldquo;Running Managed Containers in AI-Powered Startups,&rdquo; ran from 16:45 to 17:15 and focused on the operational side of containerized workloads in fast-moving companies.</p> <p>The discussion covered what it actually takes to run containers in production when your team is small and your infrastructure is changing weekly. Observability came up repeatedly &ndash; specifically the gap between what managed container services give you out of the box and what you actually need to debug a problem at 2 AM. Ralph brought Netdata&rsquo;s perspective: auto-detection of containers, per-second metrics without manual configuration, and the ability to monitor ephemeral workloads that spin up and disappear before traditional tools finish their first collection cycle.</p>Netdata at Civo Navigate 2023https://www.netdata.cloud/events/civo-navigate-2023/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/civo-navigate-2023/<p>Netdata sent two speakers to Civo Navigate Europe 2023 in London on September 5&ndash;6. Ralph Meijer, VP of Technology, opened with &ldquo;Opinionated Observability&rdquo; at noon on day one &ndash; a talk about the design trade-offs behind monitoring defaults and why those choices matter more than most vendors admit. The argument: when your tool ships with good opinions about what to collect, how to visualize it, and when to alert, you remove an entire class of configuration toil.</p>Netdata at Conf42 Cloud Native 2024https://www.netdata.cloud/events/conf42-cloud-native-2024/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/conf42-cloud-native-2024/<p>Costa Tsaousis spoke at Conf42 Cloud Native 2024 (virtual, March 2024) with &ldquo;Practical AI with Machine Learning for Observability in Netdata.&rdquo; The talk was a technical walkthrough of how Netdata applies unsupervised machine learning to metrics &ndash; not as a feature checkbox, but as a way to surface problems that static thresholds miss.</p> <p>The key insight Costa presented: individual anomalies on individual metrics are often noise. A CPU spike on one node, a latency bump on one service &ndash; these happen constantly and mean nothing on their own. But when anomalies converge across multiple metrics and services simultaneously, that convergence is a strong signal that something unusual is actually happening. As he put it: &ldquo;The power of ML becomes evident when seemingly noisy anomalies converge across various services, serving as indicators of something exceedingly unusual.&rdquo;</p>Netdata at Conf42 DevOps 2024https://www.netdata.cloud/events/conf42-devops-2024/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/conf42-devops-2024/<p>Costa Tsaousis spoke at Conf42 DevOps 2024 on January 25 with a talk titled &ldquo;Observability Standardization: the elephant is still in the room!&rdquo; The event was virtual, so the audience was global.</p> <p>The premise of the talk was blunt: the industry talks endlessly about open standards and protocol compatibility for observability, but the real question is whether we actually need custom monitoring solutions for every infrastructure scenario. OpenTelemetry, Prometheus exposition format, StatsD, SNMP &ndash; there is no shortage of standards. The problem is not the number of protocols. It is that the underlying data models, collection patterns, and retention strategies are so different across tools that &ldquo;standardization&rdquo; often just means another translation layer rather than true interoperability.</p>Netdata at Conf42 DevOps 2025https://www.netdata.cloud/events/conf42-devops-2025/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/conf42-devops-2025/<p>Shyam Sreevalsan spoke at Conf42 DevOps 2025 on January 23 (virtual) about the future of observability. The talk covered three threads: AI-driven anomaly detection, real-time processing at the edge, and predictive analytics as a replacement for reactive alerting.</p> <p>The central argument was that monitoring is shifting from &ldquo;tell me when something breaks&rdquo; to &ldquo;tell me before something breaks.&rdquo; Proactive monitoring requires two things that most traditional tools lack: per-second data collection (because you cannot predict what you cannot see) and ML models that run continuously rather than on a query schedule. Shyam walked through how Netdata handles both &ndash; distributed agents collecting every second, unsupervised ML training on each metric individually, and anomaly correlation that surfaces coordinated deviations before they become incidents.</p>Netdata at Data Centre World London 2025https://www.netdata.cloud/events/data-centre-world-london-2025/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/data-centre-world-london-2025/<p>Netdata exhibited at Data Centre World London 2025, March 12&ndash;13 at ExCeL London, at Booth DC476 in the co-located Tech Show London event. We ran live infrastructure monitoring demos throughout both days and held a LEGO draw that produced two winners.</p> <p>The audience here was different from a developer conference. Data centre operators and infrastructure managers care about things like power monitoring, cooling efficiency, network throughput, and server fleet health &ndash; all at scale, all in real time. The conversations at the booth centered on three recurring pain points: the cost of existing observability tools (especially per-GB ingestion pricing), the complexity of maintaining multiple monitoring systems for different parts of the stack, and the time wasted on manual troubleshooting when dashboards show 60-second averages that hide the actual problem.</p>Netdata at DevOops Athens Meetup 2024https://www.netdata.cloud/events/devops-athens-meetup-2024/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/devops-athens-meetup-2024/<p>Costa Tsaousis spoke at the DevOops Athens Meetup in December 2024, telling the origin story of Netdata. The project was born out of a production incident &ndash; a real problem that existing monitoring tools failed to diagnose quickly enough. That experience shaped everything that followed: the insistence on per-second granularity, the zero-configuration philosophy, the decision to run monitoring at the edge rather than depending on a remote backend.</p> <p>For a local meetup in Athens, the tone was more personal than a typical conference talk. Costa could talk about the early days of the project, the decisions that felt risky at the time, and how those choices played out over the years. The audience was Athens-based DevOps practitioners &ndash; people who work in the Greek tech ecosystem and, in many cases, had been following the project since its early days.</p>Netdata at DevOps Meetup Finland 2024https://www.netdata.cloud/events/devops-meetup-finland-2024/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/devops-meetup-finland-2024/<p>Shyam Sreevalsan presented &ldquo;Opinionated Observability&rdquo; at the DevOps Finland Meetup in May 2024. The talk picked up a thread from Ralph Meijer&rsquo;s earlier presentation at Civo Navigate and adapted it for a meetup audience &ndash; shorter, more conversational, and grounded in specific examples.</p> <p>The core question: what happens when you move from collecting metrics to actually visualizing and alerting on them? That transition is where most monitoring setups break down. You install an agent, metrics flow into a database, and then you spend weeks building dashboards, tuning thresholds, and configuring notification rules. Shyam walked through the trade-offs involved in making those decisions for the user &ndash; good defaults for visualization, sensible alert thresholds out of the box, and the risks of being too opinionated versus not opinionated enough.</p>Netdata at DevOps Summer Retreat Latvia 2024https://www.netdata.cloud/events/devops-summer-retreat-2024/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/devops-summer-retreat-2024/<p>Shyam Sreevalsan spoke at the DevOps &amp; Agile Summer Retreat in Latvia in July 2024. His talk, &ldquo;The Future of DevOps: The Next 10 Years,&rdquo; was an attempt to lay out a technical roadmap for where the discipline is heading &ndash; not vague predictions, but specific shifts already underway.</p> <p>Three themes anchored the talk. First, AI-driven automation: not replacing engineers, but handling the repetitive diagnostic and remediation tasks that consume on-call time. Second, DevSecOps becoming the default rather than the exception &ndash; security as a continuous, embedded practice rather than a gate at the end of a pipeline. Third, decentralized autonomous teams with decentralized tools and workflows, where each team owns its full stack including observability, rather than relying on a central platform team to configure monitoring for them.</p>Netdata at DevOpsDays Geneva 2024https://www.netdata.cloud/events/devops-days-geneva-2024/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/devops-days-geneva-2024/<p>Costa Tsaousis spoke at DevOpsDays Geneva 2024 with a talk that had one of the more specific titles we have brought to a conference: &ldquo;A powerful logs management solution we all have and use, but we underestimate: systemd-journal.&rdquo; We also had a booth.</p> <p>The argument was simple. Every Linux system running systemd already has a structured, indexed, binary log store built in. Most teams ignore it and ship logs to an external system immediately, paying for ingestion, storage, and query infrastructure that duplicates something the OS already provides. Costa walked through how systemd-journal works, what it stores, how Netdata integrates with it for log exploration and correlation with metrics, and where it falls short (multi-node aggregation being the obvious gap).</p>Netdata at DEVworld Amsterdam 2025https://www.netdata.cloud/events/devworld-amsterdam-2025/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/devworld-amsterdam-2025/<p>Netdata exhibited at DEVworld Conference in Amsterdam in February 2025, at Booth 18E. No talk at this one &ndash; just the team at the booth, running live demos and talking to developers.</p> <p>DEVworld attracts a broad developer audience, not just infrastructure or DevOps specialists. That meant explaining Netdata to people who might not have thought much about monitoring beyond &ldquo;is my app up or down.&rdquo; The live demos worked well for this: showing real-time, per-second dashboards to someone who has only ever seen delayed, aggregated metrics makes the difference immediately obvious.</p>Netdata at FOCS 2026 — The Future of Cybersecurity Summithttps://www.netdata.cloud/events/focs-malaysia-2026/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/focs-malaysia-2026/<p>Netdata is at the 7th Future of Cybersecurity Summit (FOCS) 2026, organized by the PIKOM Cybersecurity Chapter in Petaling Jaya, Malaysia, alongside our regional partner <a href="https://www.cloudengined.com/">Cloud Engine Digital (CED)</a>. CED is an exhibition partner at FOCS and brings expertise in cloud infrastructure, security, and data engineering across Southeast Asia. This year&rsquo;s theme is &ldquo;Cybersecurity 2030: Building Resilience in an AI-Driven, Borderless World,&rdquo; and the agenda covers AI-driven security operations, predictive risk management, and the regulatory landscape across the region.</p>Netdata at FOSDEM 2024https://www.netdata.cloud/events/fosdem-2024/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/fosdem-2024/<p>Costa Tsaousis presented in the Observability Devroom at FOSDEM 2024 in Brussels, starting at 16:30. The talk covered the journey of Netdata &ndash; how it started, the architectural decisions that shaped it, and the challenges of building a distributed monitoring system in the open.</p> <p>FOSDEM is not a vendor event. The audience is developers and maintainers who care about how things work, not how they are marketed. Costa&rsquo;s talk leaned into that: the early design goal of per-second granularity, the choice to run everything at the edge rather than relying on a centralized backend, and the ongoing tension between keeping the project simple for individual users while scaling it for organizations with thousands of nodes.</p>Netdata at FOSSCOMM 2024https://www.netdata.cloud/events/fosscomm-2024/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/fosscomm-2024/<p>Costa Tsaousis spoke at FOSSCOMM 2024, held November 9&ndash;10 at the University of Macedonia in Thessaloniki. FOSSCOMM is Greece&rsquo;s largest open-source conference, and for Netdata &ndash; a project with Greek roots &ndash; it was a homecoming of sorts.</p> <p>The talk, &ldquo;Netdata: Open Source, Distributed Observability Pipeline &ndash; Journey and Challenges,&rdquo; covered the full arc: how the project started, the architectural decisions that defined it, the community that grew around it, and the ongoing challenges of maintaining a large open-source codebase that millions of nodes depend on. Costa did not shy away from the hard parts &ndash; the difficulty of balancing open-source community expectations with commercial product development, and the engineering cost of supporting an agent that runs on everything from a Raspberry Pi to a 256-core production server.</p>Netdata at Gartner IOCS Las Vegas 2025https://www.netdata.cloud/events/gartner-iocs-2025/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/gartner-iocs-2025/<p>Netdata exhibited at the Gartner IT Infrastructure, Operations &amp; Cloud Strategies Conference (IOCS) 2025, December 9&ndash;11 at The Venetian in Las Vegas. We were at Booth #636 in the Solution Village: Operations section, running live demos every 30 minutes and meeting with IT leaders from enterprises and mid-market organizations.</p> <p>The highlight was Costa Tsaousis&rsquo;s talk on December 11 at 12:30 PM PST in Theater 3: &ldquo;Why 80% of Organizations Will Overspend for Observability in 2026.&rdquo; The thesis was direct. Legacy observability tools have a broken economic model &ndash; they charge by data volume, which means the more you monitor, the more you pay. That creates a perverse incentive to sample, average, and reduce data, which in turn creates blind spots. Organizations end up paying more for less visibility. Costa walked through how sampling at 15&ndash;60 second intervals masks the very spikes and anomalies that cause incidents, and how that hidden cost &ndash; longer MTTR, more outages, more manual investigation &ndash; often exceeds the monitoring bill itself.</p>Netdata at GITEX AI ASIA 2026https://www.netdata.cloud/events/gitex-asia-2026/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/gitex-asia-2026/<p>Netdata is at GITEX AI ASIA 2026, April 9–10 at Marina Bay Sands in Singapore, together with our regional partner <a href="https://www.cloudengined.com/">Cloud Engine Digital (CED)</a>. GITEX AI ASIA is the region&rsquo;s largest tech and AI event, drawing enterprise leaders, startups, and investors from over 110 countries.</p> <p>We&rsquo;re showing live demos of Netdata&rsquo;s real-time monitoring—per-second granularity across infrastructure, from Kubernetes clusters to bare metal servers. For teams running AI and ML workloads, this means capturing GPU utilization spikes, training pipeline anomalies, and inference latency fluctuations that 15–60 second sampling intervals simply cannot see.</p>Netdata at Howard Conference and Expo 2026https://www.netdata.cloud/events/howard-expo-2026/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/howard-expo-2026/<p>Netdata exhibited at the Howard Conference and Expo &ldquo;Game On&rdquo; event, February 24&ndash;26 at the Grand Hotel Marriott Resort in Fairhope, Alabama. Constantine Nikitiadis and Stuart McMurran were on the ground, running demos and talking with IT leaders attending the conference.</p> <p>The demos focused on two things: per-second granularity versus the 15&ndash;60 second sampling that most monitoring tools default to, and AI-assisted troubleshooting that turns hours of dashboard investigation into minutes of directed analysis. For an audience of IT practitioners managing diverse infrastructure &ndash; bare metal, VMs, cloud, some Kubernetes &ndash; the &ldquo;works everywhere&rdquo; message landed well. One agent, one install, coverage across the full stack.</p>Netdata at India DevOps Show 2025https://www.netdata.cloud/events/india-devops-show-2025/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/india-devops-show-2025/<p>Netdata was a Co-Presenting Partner at the 7th Edition India DevOps Show on May 23, 2025 at the Holiday Inn in Mumbai. Satyadeep Ashwathnarayana, Constantine Nikitiadis, and Shyam Sreevalsan represented the team.</p> <p>The talk &ndash; &ldquo;Stop Building Dashboards. Start Solving Problems.&rdquo; &ndash; challenged the default approach to observability that most DevOps teams fall into: install a monitoring tool, spend weeks building dashboards, and then stare at those dashboards during incidents trying to find the problem. The argument is that dashboards are a means, not an end. If your monitoring tool can surface the problem directly &ndash; through anomaly detection, automated correlation, and AI-driven investigation &ndash; then the dashboard becomes a verification step, not a diagnostic one.</p>Netdata at India DevOps Show 2026https://www.netdata.cloud/events/india-devops-show-2026/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/india-devops-show-2026/<p>Netdata participated as a Silver Partner at the 10th Edition India DevOps Show on February 13, 2026 at the Aloft ORR Hotel in Bengaluru. Shyam Sreevalsan and Constantine Nikitiadis represented the team, meeting with DevOps practitioners and tech leaders from across India.</p> <p>The focus was on showing how per-second metrics change the way teams respond to deployments and incidents. When you can see the impact of a deployment within seconds rather than waiting for the next polling interval, rollback decisions get faster and more confident. We demonstrated Netdata&rsquo;s AI-assisted troubleshooting &ndash; how it analyzes anomalies across the stack and produces actionable investigation reports in minutes rather than the hours of manual dashboard-digging that most teams are used to.</p>Netdata at ObservabilityCon 2023https://www.netdata.cloud/events/observabilitycon-2023/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/observabilitycon-2023/<p>Netdata had a booth at ObservabilityCon 2023 in London, hosted by Grafana Labs. No talk this time &ndash; just the team at a booth, ready for deep-dive conversations about how different observability tools fit together.</p> <p>The event drew people who are already invested in open-source observability, many of them running Grafana alongside other tools. That made for pointed, technical conversations. A common thread: people were interested in how Netdata handles high-resolution metrics collection at the edge without requiring a heavy backend. The idea of collecting per-second data, running ML-based anomaly detection locally, and then feeding results into Grafana dashboards resonated with teams already comfortable in that ecosystem.</p>Netdata at Open Source Monitoring Conference 2024https://www.netdata.cloud/events/open-source-monitoring-conference-2024/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/open-source-monitoring-conference-2024/<p>Costa Tsaousis opened the final day of the Open Source Monitoring Conference (OSMC) 2024 in Nuremberg on November 21, speaking from 9:30 to 10:00 at the Jacobi venue. His talk, &ldquo;Netdata: Open Source, Distributed Observability Pipeline &ndash; Journey and Challenge,&rdquo; covered the project&rsquo;s evolution and the architectural decisions that set it apart from other open-source monitoring tools.</p> <p>OSMC runs November 19&ndash;21 and is one of the more established events in the European IT monitoring space. The attendees are people who run Icinga, Checkmk, Prometheus, Zabbix, and similar tools in production. They know monitoring. What they wanted to hear was how Netdata&rsquo;s distributed approach &ndash; agents collecting and processing data at the edge, with no mandatory centralized storage &ndash; compares to the centralized architectures they are used to.</p>Netdata at Open Source Observability Day 2024https://www.netdata.cloud/events/open-source-observability-day-2024/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/open-source-observability-day-2024/<p>Costa Tsaousis spoke at Open Source Observability Day 2024 on October 24. The talk focused on the evolution of Netdata and the broader challenges facing open-source observability tooling.</p> <p>The tension Costa addressed is one that every open-source monitoring project faces: how do you keep things simple for a developer who just wants to monitor a few servers, while also scaling to organizations with thousands of nodes and complex compliance requirements? Netdata&rsquo;s answer has been a distributed architecture &ndash; agents at the edge doing the heavy lifting, with optional cloud coordination &ndash; but that comes with its own set of challenges around consistency, aggregation, and user experience.</p>Netdata at OpenConf 2025https://www.netdata.cloud/events/openconf-2025/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/openconf-2025/<p>Costa Tsaousis spoke at OpenConf 2025, held November 21&ndash;22 at Dais Events in Athens. The talk, &ldquo;Practical AI and Machine Learning for Observability in Netdata,&rdquo; presented a specific framing of anomaly detection that Costa has been developing across multiple conferences: ML as an advisor, not just an alert trigger.</p> <p>The distinction matters. Most ML-in-monitoring implementations boil down to &ldquo;replace static thresholds with dynamic ones.&rdquo; Netdata&rsquo;s approach is different. Multiple independent ML models run on each node, each trained on a single metric&rsquo;s behavior. When one model flags an anomaly, that is information but not necessarily action. When dozens of models across multiple services flag anomalies simultaneously, that convergence is a strong signal. The system acts as an advisor &ndash; surfacing unusual patterns, predicting potential failures, and detecting early signs of security breaches &ndash; rather than firing off yet another alert.</p>Netdata at QBITS 2025https://www.netdata.cloud/events/qbits-2025/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/qbits-2025/<p>Netdata sponsored QBITS 2025 in Montreal, April 8&ndash;10. Shyam Sreevalsan (VP - Product &amp; Strategy) and Stuart McMurran (Enterprise Sales) represented the team at this Quadbridge event, which brings together IT leaders from across Canada and the US.</p> <p>The audience was heavily tilted toward infrastructure decision-makers &ndash; CTOs, VPs of IT, directors of operations. These are people who sign off on monitoring tool purchases and live with the consequences. Three pain points came up in nearly every conversation at the booth: cost (observability bills that scale unpredictably with data volume), complexity (too many tools, too many dashboards, too much configuration), and manual troubleshooting (spending hours correlating data across systems during an incident).</p>Netdata at SREcon 2023https://www.netdata.cloud/events/srecon-2023/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/srecon-2023/<p>Costa Tsaousis, Netdata&rsquo;s founder and CEO, joined a panel at SREcon23 Americas on October 11, 2023 in San Francisco. The session, &ldquo;Open-source Development as a Full-time Pursuit,&rdquo; ran from 16:50 to 17:30 and brought together maintainers who build open-source infrastructure tooling as their day job &ndash; not as a side project.</p> <p>The panel dug into the realities of sustaining an open-source project when it is also the foundation of a company. Topics included funding models, the tension between community contributions and product roadmap, and the practical challenge of keeping a project healthy when you have both volunteer contributors and a paid engineering team pulling in potentially different directions.</p>Netdata at SREday London 2024https://www.netdata.cloud/events/sreday-london-2024/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/sreday-london-2024/<p>Costa Tsaousis spoke at SREday London 2024 on September 19&ndash;20 with &ldquo;Practical AI with Machine Learning for Observability in Netdata.&rdquo; The event ran a promo code &ndash; COSTA10 &ndash; for 10% off tickets, which brought some extra traffic our way.</p> <p>The talk was tailored for an SRE audience. These are people who live in dashboards, write alert rules, and get paged at night. They are skeptical of ML claims because they have seen too many tools that promise &ldquo;intelligent alerting&rdquo; and deliver more noise. Costa focused on the mechanics: how Netdata trains unsupervised models per metric at the edge, why anomaly convergence across metrics matters more than any single anomaly score, and how this translates to fewer false positives in practice.</p>Netdata at stackconf 2024https://www.netdata.cloud/events/stackconf-2024/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/stackconf-2024/<p>Costa Tsaousis spoke at stackconf 2024 in Berlin on June 19, in a 14:30&ndash;15:00 slot. The talk traced the history of Netdata from its inception: the original goals, the architectural bets, and what held up over time.</p> <p>The starting point was straightforward. When Costa began building Netdata, the goal was high-resolution metrics &ndash; per-second granularity, not the 10- or 60-second averages that were standard at the time. That required a fundamentally different collection architecture: lightweight agents that process data locally, real-time visualization that does not depend on a query round-trip to a central database, and auto-detection of services so that adding a new node does not require writing configuration files.</p>Netdata at Tech Show London 2026https://www.netdata.cloud/events/techshow-london-2026/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/techshow-london-2026/<p>Netdata is exhibiting at Tech Show London 2026, March 4&ndash;5 at ExCeL London. We are at Booth F223 in the Cloud &amp; AI Infrastructure zone. Constantine Nikitiadis and Shyam Sreevalsan are running the booth, with 1:1 meetings available for anyone who wants dedicated time.</p> <p>The booth features live monitoring demos comparing per-second granularity against the 10&ndash;60 second averages that most tools deliver. For teams running AI and cloud infrastructure, that difference is not academic &ndash; GPU utilization spikes, model training anomalies, and container scheduling events happen on sub-second timescales that traditional monitoring simply misses. We are also showing Netdata&rsquo;s AI-powered infrastructure observability: how unsupervised ML at the edge catches anomalies across your stack without requiring manual threshold configuration.</p>Netdata at WeAreDevelopers World Congress 2024https://www.netdata.cloud/events/wearedevelopers-2024/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/wearedevelopers-2024/<p>Netdata was at WeAreDevelopers World Congress 2024 in Berlin, July 17&ndash;19. We had a booth in Hall A at stand A_S10, and Costa Tsaousis gave a talk on &ldquo;Practical AI with Machine Learning in Observability.&rdquo;</p> <p>The booth was packed for most of the event. We ran live demos of Netdata&rsquo;s real-time dashboards, had a spin-the-wheel game, and did a prize draw. The wheel brought people in; the demos kept them. Developers who stopped by expecting a quick spin ended up watching per-second metrics streaming across a live infrastructure and asking how the anomaly detection works under the hood.</p>Netdata at WeAreDevelopers World Congress 2025https://www.netdata.cloud/events/wearedevelopers-2025/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/events/wearedevelopers-2025/<p>Netdata returned to WeAreDevelopers World Congress in Berlin as a partner for the 2025 edition, July 9&ndash;11. Costa Tsaousis gave &ldquo;Practical AI with Machine Learning in Observability&rdquo; &ndash; a talk he has been refining throughout 2024 and into 2025, each time sharpening the examples and responding to questions from previous audiences.</p> <p>The booth was busy all three days. WeAreDevelopers draws tens of thousands of developers, and the crowd skews younger and more curious than a typical infrastructure conference. Many visitors had not thought deeply about monitoring before &ndash; they knew they needed it, but had not compared tools or architectures. Live demos of Netdata running on real infrastructure, showing per-second metrics with zero configuration, gave them a baseline to compare against whatever they try next.</p>Netdata Enterprise Agenthttps://www.netdata.cloud/secure-foss-agent/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/secure-foss-agent/Netdata Partner Networkhttps://www.netdata.cloud/partnerships/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/partnerships/Netdata Pricing: Free Up to 5 Nodes | From $4.50/nodehttps://www.netdata.cloud/pricing/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/pricing/Netdata vs Chronosphere | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/chronosphere/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/comparisons/chronosphere/Netdata provides edge-native observability with per-second granularity, automatic ML anomaly detection, and transparent pricing—eliminating PromQL learning curves and SaaS-only limitations that challenge Chronosphere users.Netdata vs KloudFuse | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/kloudfuse/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/comparisons/kloudfuse/Discover why Netdata delivers instant infrastructure visibility with per-second granularity and transparent pricing, while KloudFuse requires days of setup and quote-based costs.Netdata vs Microsoft SCOM | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/msscom/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/comparisons/msscom/Netdata vs Site24x7 | Monitoring Tools Comparisonhttps://www.netdata.cloud/comparisons/site24x7/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/comparisons/site24x7/NetFlow v9/IPFIX template desync: flows decoded wrong or dropped after a reboothttps://www.netdata.cloud/guides/network/network-netflow-template-desync/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-netflow-template-desync/<p>You rebooted a router or upgraded its firmware. Minutes later, your flow collector shows a gap or anomaly. The exporter is still sending data: UDP packet counters are nonzero and climbing. But decoded flow records are zero, suspiciously low, or the field values are shifted and garbled.</p> <p>This is NetFlow v9 or IPFIX template desync. The collector holds cached template definitions that no longer match what the exporter is sending. Until it receives and caches the correct templates, it either drops records silently or misinterprets the byte layout, producing garbage fields.</p>Network monitoring checklist: the signals every production network needshttps://www.netdata.cloud/guides/network/network-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-monitoring-checklist/<p>This checklist covers the signals production networks need, organized by detection priority and mapped to maturity levels from survival to expert.</p> <p>An NPM stack is a federation of collectors, parsers, enrichment services, storage tiers, and an analytics core. Most production incidents are not &ldquo;the network broke&rdquo; but &ldquo;a collector&rsquo;s UDP buffer dropped packets,&rdquo; &ldquo;the NetFlow v9 template cache went stale after a device reboot,&rdquo; or &ldquo;the polling worker pool fell behind and now a healthy device looks down.&rdquo; The checklist is organized to surface those failure modes, not just the top-level symptoms.</p>Nextcloud Monitoringhttps://www.netdata.cloud/monitoring-101/nextcloud-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/nextcloud-monitoring/<h2 id="nextcloud-monitoring">Nextcloud Monitoring</h2> <h3 id="what-is-nextcloud">What Is Nextcloud?</h3> <p>Nextcloud is a widely-used, self-hosted productivity platform that offers a suite of client-server software for creating and using file hosting services. It is designed to allow users to share and collaborate on documents, manage files, and streamline communication all within the cloud. As a cornerstone of cloud services and computing, ensuring the optimal performance of your Nextcloud servers is critical for scalability and efficient operations.</p>NextDNS Monitoringhttps://www.netdata.cloud/monitoring-101/nextdns-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/nextdns-monitoring/<h2 id="nextdns-monitoring">NextDNS Monitoring</h2> <h3 id="what-is-nextdns">What Is NextDNS?</h3> <p>NextDNS is a powerful DNS resolver and security platform, tailored to provide efficient DNS management and enhance security. It&rsquo;s an essential tool for IT teams looking to optimize their network infrastructure by offering better privacy, security, and performance.</p> <h3 id="monitoring-nextdns-with-netdata">Monitoring NextDNS With Netdata</h3> <p>Monitor NextDNS effortlessly with Netdata, which employs an OpenMetrics (Prometheus) exporter for seamless integration. This enables you to gather crucial DNS resolver and security metrics, helping you manage your domain&rsquo;s name system more efficiently. One of the standout features of Netdata is its ability to ingest data from any Prometheus exporter, providing automated dashboards and alerts without requiring a dedicated Prometheus server or Grafana setup.</p>NGINX $request_time vs $upstream_response_time: isolating where latency liveshttps://www.netdata.cloud/guides/nginx/nginx-request-time-vs-upstream-response-time/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-request-time-vs-upstream-response-time/<p>P95 $request_time doubles. The default assumption is upstream degradation, so you scale the backend, tune the database, and add instances. The latency barely moves. The bottleneck was a slow mobile client, proxy temp-file disk I/O, or a large request body on a lossy network. This is the most common nginx misdiagnosis.</p> <p>$request_time measures the full cycle from the first byte read from the client to the last byte sent to the client. It includes reading the request, waiting for the upstream, and writing the response. $upstream_response_time measures only the backend portion, from establishing the upstream connection to receiving the last byte of the response body. The gap between them is where client-side, network, and nginx-internal delays live. To avoid chasing phantom backend problems, log both variables and compare them.</p>nginx 413 Request Entity Too Large: client_max_body_size explainedhttps://www.netdata.cloud/guides/nginx/nginx-413-request-entity-too-large/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-413-request-entity-too-large/<p>A <code>413 Request Entity Too Large</code> after adding <code>client_max_body_size 50m</code> to <code>nginx.conf</code> usually means a more specific context still overrides it, or the upstream application rejects the body after nginx accepts it. The directive applies to <code>http</code>, <code>server</code>, and <code>location</code> blocks. Raising it at the edge only moves the failure deeper if the rest of the stack is not adjusted. This guide covers how the directive inherits, when nginx fires the 413, how <code>proxy_request_buffering</code> changes the failure mode, and why you must verify every hop including the upstream application.</p>nginx 499 status code: why clients close connections before the responsehttps://www.netdata.cloud/guides/nginx/nginx-499-client-closed-connection/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-499-client-closed-connection/<p>Status 499 in nginx access logs means the client closed the TCP connection before nginx finished responding. It is an nginx-specific code that never reaches the client, so it is easy to dismiss. In practice, a 499 surge is an early warning: users or intermediaries abandon requests before upstreams officially time out and before 5xx errors spike. Ignore 499s and you usually see 502s or 504s minutes later.</p> <p>This guide shows how to read 499s, separate real user pain from load-balancer noise, and fix the root cause.</p>nginx 500 Internal Server Error: how to diagnose ithttps://www.netdata.cloud/guides/nginx/nginx-500-internal-server-error/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-500-internal-server-error/<p>A 500 from nginx tells you something failed in the request path, but not whether the failure originated in your application, FastCGI/uWSGI backend, or nginx itself. When 500s spike during an incident, first determine which side of the nginx boundary is breaking.</p> <p>Unlike 502 Bad Gateway or 504 Gateway Time-out, which point upstream, a 500 can be an application bug passed through by nginx, a configuration error, a permission failure, or resource exhaustion inside an nginx worker.</p>NGINX 502 Bad Gateway: Causes And How To Fix Ithttps://www.netdata.cloud/guides/nginx/nginx-502-bad-gateway/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-502-bad-gateway/<p>A 502 Bad Gateway means the upstream server returned an invalid response, refused the connection, or terminated before completing the response. Unlike 504, which signals upstream slowness, 502 means the upstream never produced a valid response or nginx could not reach it.</p> <p>Start with the error log. A single line like <code>connect() failed (111: Connection refused)</code> tells you the upstream is not listening. A line like <code>upstream prematurely closed connection</code> tells you the backend died mid-request. Match the exact message to the root cause.</p>Nginx 503 Service Temporarily Unavailable: Causes & Fixeshttps://www.netdata.cloud/guides/nginx/nginx-503-service-unavailable/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-503-service-unavailable/<p>A <code>503 Service Temporarily Unavailable</code> from nginx does not always mean the upstream application is broken. A healthy nginx process returns 503 by design when rate limits or connection limits reject traffic; when every backend in an upstream block is unavailable, it returns 502 instead (or 504 when a backend times out). The status code covers two failure paths here: intentional throttling and shared memory zone exhaustion; upstream exhaustion surfaces as 502 or 504. The fix depends on which path the request took.</p>NGINX 504 Gateway Time-Out: Causes & Fixeshttps://www.netdata.cloud/guides/nginx/nginx-504-gateway-timeout/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-504-gateway-timeout/<p>A 504 Gateway Time-out means nginx reached the upstream but the upstream did not finish its response before <code>proxy_read_timeout</code> expired. The default is 60 seconds. Unlike a 502 Bad Gateway, which means nginx never established a valid upstream connection, a 504 means the connection succeeded but the response did not complete in time.</p> <p>This guide covers isolating slow upstreams via access log variables, tuning timeouts and retries, and distinguishing 504 from 502.</p>NGINX active connections climbing: reading, writing, waiting explainedhttps://www.netdata.cloud/guides/nginx/nginx-active-connections-high/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-active-connections-high/<p>When operators see Active connections climbing in <code>stub_status</code>, the first instinct is often to add capacity. That instinct is usually wrong. The <code>stub_status</code> module exposes exactly seven metrics, and the most useful of them is the breakdown of active connections into Reading, Writing, and Waiting. The absolute number of active connections is almost meaningless without the ratio between these three states. A server with 10,000 active connections where 9,000 are Waiting is healthy. A server with 500 active connections where 400 are Reading may be under a slowloris-style attack.</p>NGINX Backend Cascade Failure: When Slow Upstreams Take Down Everythinghttps://www.netdata.cloud/guides/nginx/nginx-backend-cascade-failure/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-backend-cascade-failure/<p>Users report timeouts. 502 Bad Gateway and 504 Gateway Time-out responses are climbing, and nginx error logs show upstream timeouts. On the nginx host, CPU and memory are normal, and the master process is alive. The proxy is healthy but out of connections.</p> <p>This is a backend cascade failure. One slow upstream causes nginx workers to hold connections open while waiting for responses, consuming finite <code>worker_connections</code> slots. As slots fill, new requests cannot be forwarded. Traffic concentrates on the remaining healthy backends, which overload and slow down. Eventually every backend times out or fails health checks, and nginx returns 502/504 to all clients while the proxy process remains up.</p>nginx connect() failed (111: Connection refused) while connecting to upstreamhttps://www.netdata.cloud/guides/nginx/nginx-connect-failed-connection-refused-upstream/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-connect-failed-connection-refused-upstream/<p>HTTP 502 Bad Gateway and the error <code>connect() failed (111: Connection refused) while connecting to upstream</code> mean nginx reached the upstream IP, but the target port actively refused the TCP connection. The backend is either not running, not listening on the interface nginx expects, or a firewall is blocking the port.</p> <p>This is distinct from <code>upstream timed out (110: Connection timed out)</code>. A timeout means the TCP SYN never received a response, usually because a firewall silently dropped the packet or the host is unreachable. Errno 111 means the network path is open but no process is accepting connections. The error log includes the upstream address, such as <code>upstream: &quot;fastcgi://127.0.0.1:9000&quot;</code>. Read that line first to isolate the exact backend.</p>NGINX Connection Exhaustion: Detection, Diagnosis & Preventionhttps://www.netdata.cloud/guides/nginx/nginx-connection-exhaustion/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-connection-exhaustion/<p>Users see connection timeouts while load balancer health checks and the NGINX <code>stub_status</code> endpoint still return HTTP 200. New connections are silently dropped. Connection exhaustion is a cliff-edge failure: once the limit is hit, there is no graceful degradation. Connections are refused at the kernel level, or accepted into the TCP backlog but discarded by NGINX because no worker has a free connection slot.</p> <p>The capacity boundary is <code>worker_connections</code> multiplied by <code>worker_processes</code>. In proxy mode, every request consumes at least two slots: one for the client and one for the upstream. With the default <code>worker_connections</code> of 512, four worker processes can handle at most 2,048 connections, or roughly 1,000 concurrent proxied requests. The gap between <code>accepts</code> and <code>handled</code> in <code>stub_status</code> is the leading indicator; it grows before the active connection count flatlines.</p>NGINX Dropped Connections: The Accepts vs Handled Gaphttps://www.netdata.cloud/guides/nginx/nginx-dropped-connections/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-dropped-connections/<p>Users report intermittent connection timeouts. Your HTTP 5xx rate is flat. The error log is quiet. Something is dropping traffic before it ever becomes a request.</p> <p>On every NGINX instance, the <code>stub_status</code> page exposes two cumulative counters: <code>accepts</code> and <code>handled</code>. When <code>accepts</code> grows faster than <code>handled</code>, NGINX is taking connections from the kernel and then discarding them. This gap is a leading indicator of connection-slot or file-descriptor exhaustion. It often starts increasing minutes before the system hits the hard wall.</p>nginx limiting requests, excess -- understanding limit_req rejectionshttps://www.netdata.cloud/guides/nginx/nginx-limiting-requests-excess/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-limiting-requests-excess/<p>When <code>[error] ... limiting requests, excess</code> appears in nginx error logs alongside 503 responses in access logs, determine whether you are under attack, misconfigured, or out of shared memory. The <code>ngx_http_limit_req_module</code> implements a leaky bucket rate limiter. Its interaction with <code>burst</code>, <code>nodelay</code>, and shared memory sizing determines whether you reject malicious traffic, delay legitimate users, or silently stop enforcing limits.</p> <h2 id="what-it-is-and-why-it-matters">What it is and why it matters</h2> <p><code>limit_req</code> is nginx&rsquo;s request-level rate limiter. It uses a shared memory zone, configured via <code>limit_req_zone</code>, to track request rates per key, typically <code>$binary_remote_addr</code>. The zone is mapped into every worker process. When a request arrives, nginx checks the key&rsquo;s current rate against the configured limit. Depending on <code>burst</code> and <code>nodelay</code>, it delays the request, rejects it, or processes it immediately.</p>NGINX Listen Queue Overflow: Somaxconn, Backlog & Silent Connection Dropshttps://www.netdata.cloud/guides/nginx/nginx-listen-queue-overflow/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-listen-queue-overflow/<p>Clients report intermittent connection timeouts. Your load balancer health checks pass. NGINX error logs are clean and access logs show no 5xx spikes. The issue is not in NGINX workers or upstream applications. It is in the kernel accept queue.</p> <p>When the accept queue fills, the kernel drops new connections silently. NGINX never sees them, so it logs nothing. Evidence is client-side timeouts and the kernel counter <code>TcpExtListenOverflows</code>.</p> <p>On Linux, the effective listen backlog is <code>min(NGINX backlog, net.core.somaxconn)</code>. NGINX defaults to 511 on Linux; modern kernels default <code>somaxconn</code> to 4096, but older systems may use 128. If <code>somaxconn</code> is 128, the effective backlog is 128 regardless of what NGINX requests. Fix both.</p>NGINX Monitoringhttps://www.netdata.cloud/monitoring-101/nginx-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/nginx-monitoring/<h2 id="nginx-monitoring">NGINX Monitoring</h2> <h3 id="what-is-nginx">What Is NGINX?</h3> <p><a href="https://www.nginx.com/">NGINX</a> is a high-performance web server, reverse proxy server, and load balancer designed to handle a large number of concurrent connections efficiently. Its modular architecture allows it to be extended with additional features, making it a versatile component in modern application infrastructures.</p> <h3 id="monitoring-nginx-with-netdata">Monitoring NGINX With Netdata</h3> <p>When it comes to monitoring NGINX, Netdata offers an intuitive and real-time monitoring solution. With <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/nginx/">Netdata&rsquo;s NGINX monitoring tool</a>, you can observe your server&rsquo;s metrics in real time, use interactive charts, and detect any anomalies swiftly.</p>NGINX Monitoring Checklist: The Signals Every Production Server Needshttps://www.netdata.cloud/guides/nginx/nginx-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-monitoring-checklist/<p>NGINX is an event-driven, single-threaded-per-worker process. Most production failures follow predictable patterns: <a href="https://www.netdata.cloud/guides/nginx/nginx-connection-exhaustion/">connection exhaustion</a>, backend cascades, file descriptor limits, or silent kernel-level drops. This article maps the signals that expose those failures into four cumulative maturity levels: Survival, Operational, Mature, and Expert. Use it to audit your current coverage or to justify instrumentation work before the next incident.</p> <p>Each level adds depth. Survival answers &ldquo;Is it up?&rdquo; Operational answers &ldquo;Is it healthy?&rdquo; Mature adds leading indicators. Expert adds the signals you instrument after your third postmortem. The tables below list each signal, why it matters, and the threshold that should trigger a response.</p>nginx no live upstreams while connecting to upstream: what it meanshttps://www.netdata.cloud/guides/nginx/nginx-no-live-upstreams/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-no-live-upstreams/<p>When nginx logs <code>no live upstreams while connecting to upstream</code>, every server in the affected upstream block is marked unavailable. The proxied request has no eligible backend, so nginx returns 502 Bad Gateway. This is not an nginx defect; it signals that all backends have failed open-source nginx&rsquo;s passive health checks, or a network partition has made them unreachable from the nginx host.</p> <p>Open-source nginx supports only passive health checks. The defaults are aggressive: <code>max_fails=1</code> and <code>fail_timeout=10s</code>. One timeout or connection failure inside a ten-second window removes a server from rotation for ten seconds. When every server crosses that threshold, the pool has zero live members.</p>NGINX Plus Monitoringhttps://www.netdata.cloud/monitoring-101/nginxplus-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/nginxplus-monitoring/<h2 id="nginx-plus-monitoring">NGINX Plus Monitoring</h2> <h3 id="what-is-nginx-plus">What Is NGINX Plus?</h3> <p><a href="https://www.nginx.com/products/nginx/">NGINX Plus</a> is a premium version of NGINX, offering additional features such as advanced load balancing, reliability, security, and flexibility to deploy applications. It is widely used for web serving, reverse proxying, caching, load balancing, media streaming, and more.</p> <h3 id="monitoring-nginx-plus-with-netdata">Monitoring NGINX Plus With Netdata</h3> <p>Netdata provides a robust NGINX Plus monitoring tool that gives real-time insight into the performance and health of your NGINX Plus servers. With the ability to visualize key metrics and diagnose performance issues swiftly, Netdata becomes an invaluable tool for any DevOps, SRE, or IT professional managing NGINX Plus instances. To learn more, see the <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/nginxplus/?utm_source=website&amp;utm_content=monitoring101">NGINX Plus collector documentation</a>.</p>NGINX proxy buffer spill to disk: proxy_buffers and temp file latencyhttps://www.netdata.cloud/guides/nginx/nginx-proxy-buffer-spill-to-disk/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-proxy-buffer-spill-to-disk/<p>You notice some proxied requests are crawling. Upstream logs show sub-50 ms response times. The network path is clean. The nginx error log is quiet. In the access log, however, <code>$request_time</code> is ten times larger than <code>$upstream_response_time</code>. For large responses, this gap is the signature of proxy buffer spill.</p> <p>When an upstream response exceeds the memory buffers allocated by <code>proxy_buffers</code>, nginx writes the overflow to a temporary file under <code>proxy_temp_path</code> and reads it back later. Because the log message for this event is emitted at debug level only, the delay is silent. Standard upstream monitoring gives no hint; the delay hides entirely inside nginx.</p>NGINX proxy_cache not caching: why responses bypass the cachehttps://www.netdata.cloud/guides/nginx/nginx-proxy-cache-not-caching/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-proxy-cache-not-caching/<p>After enabling <code>proxy_cache</code> and defining the cache path, upstreams still take every hit. Access logs show <code>$upstream_cache_status</code> as <code>BYPASS</code> or <code>MISS</code>, hit rate stays near zero, and nothing appears in the error log. NGINX applies a strict request-phase and response-phase decision tree before anything enters the cache. If any condition fails, the response is never stored. The symptom looks like upstream overload, but the root cause is usually a directive, a header, or a missing validity window.</p>NGINX reload not applying config: why old workers keep servinghttps://www.netdata.cloud/guides/nginx/nginx-reload-not-applying-config/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-reload-not-applying-config/<p>You pushed a config change, ran <code>nginx -s reload</code>, and moved on. Hours later, the new certificate is not being served, the updated upstream is not receiving traffic, or the tightened rate limit never took effect. NGINX did not stop running, but the reload never applied. This is the silent rollback: when a reload fails validation, the master keeps the previous configuration active and old workers continue serving. Even when validation passes, old workers can remain alive for hours if long-lived connections prevent them from draining and <code>worker_shutdown_timeout</code> is not set. This guide shows how to confirm the failure, find the root cause, and prevent config drift from going undetected.</p>NGINX slow requests: from access log to root causehttps://www.netdata.cloud/guides/nginx/nginx-slow-requests/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-slow-requests/<p>Elevated <code>$request_time</code> in access logs does not mean the upstream is slow. The variable measures the full lifecycle: from reading the first client byte through sending the last response byte. That includes client upload, upstream wait, nginx processing, and client download. Blaming the backend by reflex is the most common nginx latency mistake.</p> <p>To split the time accurately, confirm your <code>log_format</code> includes <code>$request_time</code>, <code>$upstream_response_time</code>, <code>$upstream_connect_time</code>, and <code>$upstream_header_time</code>.</p> <h2 id="what-this-means">What this means</h2> <p><code>$request_time</code> is the wall-clock time nginx spends on a single request. For a proxied request:</p>NGINX SSL certificate expired: detection and emergency renewalhttps://www.netdata.cloud/guides/nginx/nginx-ssl-certificate-expired/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-ssl-certificate-expired/<p>An expired SSL certificate on NGINX is an immediate outage, not gradual degradation. Browsers and API clients reject the connection at the TLS handshake, often before NGINX logs anything useful. The fix is rarely as simple as running a renewal script again. Verify what is on disk, confirm the running configuration is using it, and force a reload so workers load the new certificate.</p> <p>NGINX loads certificates at configuration parse time. Workers present whatever the master loaded at startup or during the last reload. Replacing the PEM file on disk does not change what active workers present. Only a reload or restart pulls the new material into memory. If a reload fails, NGINX continues serving with the previous configuration, which still holds the expired certificate. Old workers continue until their connections drain, so even after a successful reload, long-lived connections may briefly present the old certificate.</p>NGINX SSL/TLS handshake CPU saturation: detection and tuninghttps://www.netdata.cloud/guides/nginx/nginx-ssl-handshake-cpu-saturation/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-ssl-handshake-cpu-saturation/<p>NGINX latency climbs while requests per second flatline. Worker processes are pinned near 100% CPU, yet active connections are nowhere near the <code>worker_connections</code> limit. Access logs show fast upstream response times, but <code>$request_time</code> is an order of magnitude larger. The bottleneck is not the network, disk, or backends: it is the TLS handshake.</p> <p>When workers burn CPU on cryptography, the single-threaded event loop has no time left for request processing. Every new TCP connection that requires a full SSL handshake adds asymmetric crypto workload. If clients do not resume sessions and the connection rate is high, throughput collapses even though the machine has plenty of idle connection slots. This guide shows how to detect, diagnose, and tune for SSL handshake CPU saturation.</p>NGINX Unit Monitoringhttps://www.netdata.cloud/monitoring-101/nginxunit-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/nginxunit-monitoring/<h2 id="nginx-unit-monitoring">NGINX Unit Monitoring</h2> <p>NGINX Unit monitoring is crucial for ensuring the optimal performance and reliability of web applications. With the capabilities offered by the <a href="https://unit.nginx.org/">NGINX Unit</a>, a dynamic application server, it&rsquo;s possible to handle various configurations for multiple languages seamlessly. Using robust monitoring tools like the Netdata platform can provide real-time insights into your NGINX Unit, allowing IT engineers, DevOps, and SRE teams to swiftly detect issues and optimize their infrastructure.</p>nginx upstream prematurely closed connection while reading response headerhttps://www.netdata.cloud/guides/nginx/nginx-upstream-prematurely-closed-connection/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-upstream-prematurely-closed-connection/<p><code>upstream prematurely closed connection while reading response header from upstream</code> means the upstream server closed the TCP socket while nginx was still reading response headers. This produces a 502 Bad Gateway. Unlike a timeout, the upstream actively terminated the connection.</p> <p>The root cause is typically on the backend: a crash, worker recycle, request size limit, or stale keepalive connection the backend closed while nginx tried to reuse it. nginx retries the request on another backend only if <code>proxy_next_upstream</code> includes <code>error</code> (the default for idempotent methods). Retries improve availability but do not fix the underlying issue.</p>nginx upstream sent too big header while reading response header from upstreamhttps://www.netdata.cloud/guides/nginx/nginx-upstream-sent-too-big-header/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-upstream-sent-too-big-header/<p>The error log contains <code>upstream sent too big header while reading response header from upstream</code>. Clients receive 502 Bad Gateway. This is not an upstream crash or network timeout. It is a hard size limit: an upstream server is sending response headers larger than the fixed buffer nginx allocates for reading them, so nginx aborts the request and returns 502.</p> <p>This failure typically hits specific endpoints rather than the whole site. Login callbacks, OAuth2 redirects, and session initialization paths are common because they inject large <code>Set-Cookie</code> headers, JWTs, or verbose debug information into the response. The error is deterministic: every request that produces an oversized header triggers it. This makes it easy to reproduce, but it also blocks all traffic to the affected endpoint until the buffer is enlarged or the header is shrunk.</p>nginx upstream timed out (110: Connection timed out) while connecting/readinghttps://www.netdata.cloud/guides/nginx/nginx-upstream-timed-out/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-upstream-timed-out/<p><code>upstream timed out (110: Connection timed out)</code> in the nginx error log usually surfaces to clients as a 504 Gateway Timeout. The suffix after the error string tells you which phase failed: connecting, sending, or reading. That phase determines whether you are looking at a dead backend, a network partition, or a retry storm hiding the real problem.</p> <p>The defaults are unforgiving. <code>proxy_connect_timeout</code>, <code>proxy_send_timeout</code>, and <code>proxy_read_timeout</code> all default to 60 seconds, and <code>proxy_next_upstream</code> implicitly retries on <code>error</code> and <code>timeout</code>. Retries can mask the root cause while exhausting upstream capacity.</p>NGINX VTS Monitoringhttps://www.netdata.cloud/monitoring-101/nginxvts-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/nginxvts-monitoring/<h2 id="nginx-vts-monitoring">NGINX VTS Monitoring</h2> <h3 id="what-is-nginx-vts">What Is NGINX VTS?</h3> <p>NGINX VTS (Virtual Traffic Status) is a third-party module for NGINX, a high-performance web server and reverse proxy. The VTS module provides detailed traffic status and metrics crucial for web server monitoring and management. It enables users to keep track of the overall health and performance of their NGINX server instances.</p> <h3 id="monitoring-nginx-vts-with-netdata">Monitoring NGINX VTS With Netdata</h3> <p>Using Netdata as an NGINX VTS monitoring tool allows you to collect and visualize vital metrics in real time, offering unprecedented visibility into your web server&rsquo;s performance. With <a href="https://www.netdata.cloud/">Netdata</a>, you can monitor NGINX VTS effortlessly by leveraging its extensive integration capabilities and live data streaming features.</p>NGINX worker_connections & worker_processes: Sizing For Real Traffichttps://www.netdata.cloud/guides/nginx/nginx-worker-connections-tuning/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-worker-connections-tuning/<p>NGINX defaults leave most CPU cores idle and exhaust quickly under load. The real limit is often the OS file descriptor ceiling, which silently overrides the directive.</p> <p>Sizing these parameters means understanding the capacity chain: kernel queue, connection slot, file descriptor limit, event loop. This guide provides concrete rules for static and proxy workloads and the signals that reveal when headroom has disappeared.</p> <h2 id="how-the-worker-model-consumes-capacity">How The Worker Model Consumes Capacity</h2> <p>NGINX uses an event-driven, non-blocking, single-threaded-per-worker architecture. The master process binds to ports and spawns workers. Each worker runs an independent event loop that accepts connections and moves them through a state machine. The directive <code>worker_connections</code> sets the maximum number of simultaneous connections each worker can track. The theoretical system-wide ceiling is <code>worker_processes</code> multiplied by <code>worker_connections</code>.</p>nginx: a client request body is buffered to a temporary file — what it meanshttps://www.netdata.cloud/guides/nginx/nginx-buffered-to-temporary-file/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-buffered-to-temporary-file/<p>You are tailing the nginx error log during a latency investigation and see the line: a client request body is buffered to a temporary file. It is logged at [warn], not [error], so it is easy to ignore. But the message means a request body has exceeded the in-memory buffer and nginx is now writing that data to disk. On a busy reverse proxy or file-upload endpoint, this behavior can add hundreds of milliseconds or seconds of latency before your upstream application receives the payload. It also consumes file descriptors and disk I/O capacity without ever surfacing as a 5xx status code.</p>nginx: bind() to 0.0.0.0:80 failed (98: Address already in use)https://www.netdata.cloud/guides/nginx/nginx-address-already-in-use/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-address-already-in-use/<p>The error log shows <code>[emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)</code> and the master process exits. During a reload, old workers keep running with the previous configuration, so users may not notice immediately. During system boot or a manual start, the service is down.</p> <p>Error 98 is <code>EADDRINUSE</code>. The nginx master binds listening sockets before forking workers. If the kernel reports port 80 is occupied, nginx cannot start or apply the new configuration. The holder might be a different service, a stale nginx master after a crash, or another nginx instance. Inside the same configuration, conflicting socket options for the same address:port can also trigger the error.</p>nginx: configuration file test failed - finding the syntax errorhttps://www.netdata.cloud/guides/nginx/nginx-configuration-file-test-failed/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-configuration-file-test-failed/<p>An <code>nginx -t</code> or <code>nginx -s reload</code> ending with <code>nginx: configuration file /path/to/nginx.conf test failed</code> means the configuration tree is syntactically invalid or references a missing file. The master process rejects the change, so the running server continues with the previous working configuration. That prevents an outage, but your intended change is silently inactive. Read the exact error message, map it to the real source, fix it, and validate with <code>nginx -t</code> before reloading.</p>nginx: no resolver defined to resolve - dynamic upstream DNShttps://www.netdata.cloud/guides/nginx/nginx-no-resolver-defined/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-no-resolver-defined/<p>502 Bad Gateway responses paired with <code>no resolver defined to resolve example.com</code> in the error log mean <code>proxy_pass</code> uses a variable - for example, <code>proxy_pass http://$backend;</code> - and the enclosing context has no <code>resolver</code> directive.</p> <p>With a literal <code>proxy_pass</code>, nginx resolves the upstream hostname once at startup or reload and caches the result indefinitely. It never queries DNS again until restart or reload. With a variable-based <code>proxy_pass</code>, nginx resolves the hostname at request time through its internal async resolver. Without a <code>resolver</code> directive, the lookup fails immediately and returns 502.</p>Nginx: Too Many Open Files - Diagnosing File Descriptor Exhaustionhttps://www.netdata.cloud/guides/nginx/nginx-too-many-open-files/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-too-many-open-files/<p>After a traffic spike, the error log shows <code>accept4() failed (24: Too many open files)</code>, then goes silent. Existing connections still serve, but new ones cannot land.</p> <p>File descriptor exhaustion is a hard failure. Once the limit is hit, nginx cannot accept new connections, open upstream sockets, or write to the error log. Default OS limits of 1024 are too low for production reverse proxies. Each proxied request consumes at least two FDs, and idle keepalive connections hold them indefinitely. The effective limit is the lower of <code>worker_rlimit_nofile</code> and the OS hard limit enforced by systemd or the container runtime.</p>Nginx: worker_connections Are Not Enough - Causes & Fixeshttps://www.netdata.cloud/guides/nginx/nginx-worker-connections-are-not-enough/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/nginx/nginx-worker-connections-are-not-enough/<p>Your error log shows <code>worker_connections are not enough while connecting to upstream</code>. New clients time out while existing connections may still work. This is a hard capacity cliff: once a worker exhausts its connection slots, it cannot accept new connections until a slot frees. The default limit is 512 per worker, not 1024, and in reverse-proxy mode each request consumes at least two slots. Raising the number is often the first reaction, but if a slow backend is holding connections open, the slots will fill again no matter how high you set the limit.</p>NIC RSS misconfiguration: one CPU core silently dropping your telemetryhttps://www.netdata.cloud/guides/network/network-collector-nic-rss/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-collector-nic-rss/<p>Your flow collector has 16 CPU cores, but one is pinned at 100% while the other 15 sit idle. NIC receive drop counters are climbing. UDP socket buffer errors (<code>Udp_RcvbufErrors</code>) are incrementing. Your bandwidth charts show traffic declining during what is actually a traffic spike. The box looks underpowered, so you start sizing a bigger one. The real problem: Receive Side Scaling (RSS) is funneling every inbound packet to a single receive queue serviced by a single CPU core. No amount of additional cores or RAM fixes this until RSS distributes interrupts across them.</p>NRPE daemon Monitoringhttps://www.netdata.cloud/monitoring-101/nrpe-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/nrpe-monitoring/<h2 id="nrpe-daemon-monitoring">NRPE daemon Monitoring</h2> <h3 id="what-is-nrpe-daemon">What Is NRPE daemon?</h3> <p>The Nagios Remote Plugin Executor (NRPE) daemon is an integral part of system and network monitoring, widely utilized to execute remote commands and scripts. This daemon facilitates the collection of key performance metrics from remote systems, providing insights into system health and performance. It is especially crucial for environments relying on Nagios for extensive monitoring capabilities, allowing for seamless integration of remote checks into the central monitoring framework.</p>NSD Monitoringhttps://www.netdata.cloud/monitoring-101/nsd-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/nsd-monitoring/<h2 id="nsd-monitoring">NSD Monitoring</h2> <h3 id="what-is-nsd">What Is NSD?</h3> <p>NSD is an authoritative DNS name server developed by NLnet Labs. It is renowned for its high performance, robust security measures, and support for various DNS standards. NSD is a cornerstone for businesses looking for a reliable DNS solution to ensure smooth and secure network communication. You can find more in-depth information on the <a href="https://nsd.docs.nlnetlabs.nl/en/latest">NSD official documentation</a>.</p> <h3 id="monitoring-nsd-with-netdata">Monitoring NSD With Netdata</h3> <p>Monitoring NSD effectively is crucial to maintaining optimal server performance and securing uptime. Netdata offers a comprehensive NSD monitoring tool that easily integrates with your system to provide in-depth insights into your DNS server&rsquo;s performance. By leveraging Netdata, you can continuously monitor NSD metrics in real time, enabling swift diagnosis and resolution of potential issues.</p>NTP drift on network devices: the silent killer of event correlationhttps://www.netdata.cloud/guides/network/network-ntp-drift/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-ntp-drift/<p>Clock drift on network devices produces no visible symptom. The device stays up, interfaces carry traffic, BGP sessions remain Established, SNMP keeps responding. The damage surfaces hours or days later, in a postmortem where two devices&rsquo; timestamps disagree by hundreds of milliseconds and the analyst cannot reconstruct the event sequence. Every cross-device correlation in the monitoring stack depends on accurate, monotonic time across every collector and every polled device.</p> <p>The telemetry itself looks fine. Syslog messages arrive with timestamps. Flow records carry timestamps. BGP NOTIFICATION traps are time-stamped. The problem is that those timestamps are wrong relative to each other, and nothing flags the discrepancy. A device 200 milliseconds off its peers produces records that technically arrive but correlate poorly with records from correctly synchronized devices.</p>NTPd Monitoringhttps://www.netdata.cloud/monitoring-101/ntpd-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/ntpd-monitoring/<h2 id="ntpd-monitoring">NTPd Monitoring</h2> <h3 id="what-is-ntpd">What Is NTPd?</h3> <p>NTPd stands for Network Time Protocol daemon, an essential component for time synchronization across computer networks. By utilizing the NTP protocol, NTPd ensures that timekeeping is accurate and consistent across systems, which is crucial for numerous applications and services.</p> <h3 id="monitoring-ntpd-with-netdata">Monitoring NTPd With Netdata</h3> <p>When you monitor NTPd with Netdata, you gain real-time insights into your time synchronization processes. The <a href="https://www.netdata.cloud/integrations/data-collection/networking/ntpd/">NTPd monitoring tool</a> by Netdata offers comprehensive visibility into NTPd&rsquo;s operational metrics, helping you to ensure your network&rsquo;s timing accuracy.</p>Nvidia GPU Monitoringhttps://www.netdata.cloud/monitoring-101/nvidia-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/nvidia-monitoring/<h2 id="what-is-nvidia-gpu">What is Nvidia GPU?</h2> <p>Nvidia GPU (Graphic Processing Unit) is a specialized electronic circuit designed to rapidly process and manipulate graphics data. Nvidia GPUs are typically found in high-end gaming computers, workstations, and servers. They are used to power complex video games and other graphics-intensive tasks.</p> <h2 id="monitoring-nvidia-gpu-with-netdata">Monitoring Nvidia GPU with Netdata</h2> <p>The prerequisites for monitoring Nvidia GPU with Netdata are to have a system with an Nvidia GPU and <a href="https://learn.netdata.cloud/docs/cloud/get-started/">Netdata installed</a> on your system.</p>Nvidia GPU Monitoringhttps://www.netdata.cloud/monitoring-101/nvidia_smi-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/nvidia_smi-monitoring/<h2 id="nvidia-gpu-monitoring">Nvidia GPU Monitoring</h2> <h3 id="what-is-nvidia-gpu">What Is Nvidia GPU?</h3> <p>Nvidia GPUs are specialized processing units designed by <a href="https://www.nvidia.com/en-us/">Nvidia</a> primarily for graphics rendering, though they are widely used in computational tasks such as deep learning, scientific simulations, and cryptocurrency mining. Nvidia&rsquo;s advanced GPU technology empowers applications to perform complex tasks efficiently.</p> <h3 id="monitoring-nvidia-gpu-with-netdata">Monitoring Nvidia GPU With Netdata</h3> <p>Netdata provides real-time monitoring for Nvidia GPUs by leveraging the <code>nvidia-smi</code> CLI tool. This setup allows you to keep an eye on various performance metrics, ensuring optimal operation and helping diagnose potential issues as they occur.</p>NVMe Monitoringhttps://www.netdata.cloud/monitoring-101/nvme-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/nvme-monitoring/<h2 id="nvme-monitoring">NVMe Monitoring</h2> <h3 id="what-is-nvme">What Is NVMe?</h3> <p>NVMe, or Non-Volatile Memory Express, is a storage protocol designed to capitalize on the low latency and internal parallelism of solid-state drives (SSDs). It is widely embraced for boosting storage performance and is crucial for applications demanding high data throughput and speed. NVMe allows for direct CPU communication, drastically reducing data transfer overhead compared to legacy protocols like SATA.</p> <h3 id="monitoring-nvme-with-netdata">Monitoring NVMe With Netdata</h3> <p>Monitoring NVMe is essential for maintaining optimal performance, ensuring data integrity, and identifying potential hardware issues. Netdata provides a robust set of monitoring tools tailored for NVMe devices that allow you to track their health and performance metrics in real time.</p>OBS Studio Monitoringhttps://www.netdata.cloud/monitoring-101/obs_studio-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/obs_studio-monitoring/<h2 id="obs-studio-monitoring">OBS Studio Monitoring</h2> <h3 id="what-is-obs-studio">What Is OBS Studio?</h3> <p>OBS Studio is a powerful open-source software often used for live streaming and recording. Its capabilities cater to content creators who produce video content for platforms like YouTube, Twitch, and Facebook Live. With its extensive suite of features, OBS Studio enables seamless video mixing, filtering, and transitions, making it a staple in media streaming and recording environments.</p> <h3 id="monitoring-obs-studio-with-netdata">Monitoring OBS Studio With Netdata</h3> <p>To effectively monitor OBS Studio, utilizing the <a href="https://github.com/lukegb/obs_studio_exporter">OBS Studio Exporter</a> is crucial. Netdata, a cutting-edge monitoring solution, leverages openmetrics (prometheus) to integrate with the OBS Studio Exporter. This integration empowers technical users to ingest data from any Prometheus exporter without the need for a standalone Prometheus server or Grafana dashboards. Instead, Netdata provides automated dashboards, real-time alerts, and other interactive functionalities to ensure comprehensive monitoring of your OBS Studio setup.</p>Open vSwitch Monitoringhttps://www.netdata.cloud/monitoring-101/openvswitch-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/openvswitch-monitoring/<h2 id="open-vswitch-monitoring">Open vSwitch Monitoring</h2> <h3 id="what-is-open-vswitch">What Is Open vSwitch?</h3> <p>Open vSwitch (OVS) is a multilayer software switch used in virtualized environments to manage network traffic. It is designed to enable network automation through programmatic extensions, while supporting standard management interfaces. OVS plays a significant role in creating highly scalable distributed networking environments.</p> <h3 id="monitoring-open-vswitch-with-netdata">Monitoring Open vSwitch With Netdata</h3> <p>Monitoring Open vSwitch with Netdata is a straightforward process which can greatly enhance your understanding of network performance and reliability. Netdata utilizes an <a href="https://github.com/digitalocean/openvswitch_exporter">OpenMetrics (Prometheus) exporter</a> specifically designed for Open vSwitch, allowing users to collect and visualize key network metrics in real-time. Notably, Netdata does not require a separate Prometheus server or Grafana, simplifying the deployment process. Once data is collected, users receive automated dashboards and alerts, enabling proactive troubleshooting and network optimization.</p>OpenRC Monitoringhttps://www.netdata.cloud/monitoring-101/openrc-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/openrc-monitoring/<h2 id="openrc-monitoring">OpenRC Monitoring</h2> <h3 id="what-is-openrc">What Is OpenRC?</h3> <p>OpenRC is a dependency-based init system that provides services management for Unix-like operating systems. Known for its versatility and compatibility with various environments, OpenRC is an appealing choice for managing system startup processes.</p> <h3 id="monitoring-openrc-with-netdata">Monitoring OpenRC With Netdata</h3> <p>To effectively monitor OpenRC, using a comprehensive and robust tool like Netdata is crucial. Netdata employs an openmetrics (Prometheus) exporter to collect data from OpenRC systems. This allows for seamless ingestion of metrics and the creation of automated dashboards and alerts without the need for an extensive setup involving a Prometheus server or Grafana. With Netdata, you can gather insights about system performance, detect anomalies, and ensure the health of your OpenRC-managed environments with ease.</p>OpenROADM devices Monitoringhttps://www.netdata.cloud/monitoring-101/openroadm-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/openroadm-monitoring/<h2 id="openroadm-devices-monitoring">OpenROADM devices Monitoring</h2> <h3 id="what-is-openroadm-devices">What Is OpenROADM devices?</h3> <p>OpenROADM (Reconfigurable Optical Add-Drop Multiplexer) devices are integral components of optical transport networks, enabling data to traverse long distances with high fidelity. These devices ensure efficient utilization of optical bandwidth and support the dynamic reconfiguration of network paths, making them critical for modern, adaptable network infrastructure.</p> <h3 id="monitoring-openroadm-devices-with-netdata">Monitoring OpenROADM devices With Netdata</h3> <p>To monitor OpenROADM devices, Netdata employs an openmetrics (Prometheus) exporter, providing a seamless integration process. Netdata supports data ingestion from any Prometheus exporter, which provides automated dashboards, alerts, and more - all without needing a dedicated Prometheus server or Grafana instance. This makes Netdata an excellent $name monitoring tool as it streamlines the network performance monitoring process, giving you insights in real-time.</p>OpenVPN Monitoringhttps://www.netdata.cloud/monitoring-101/openvpn-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/openvpn-monitoring/<h2 id="openvpn-monitoring">OpenVPN Monitoring</h2> <h3 id="what-is-openvpn">What Is OpenVPN?</h3> <p>OpenVPN is a renowned open-source VPN protocol that offers secure point-to-point and site-to-site connections. Often utilized to bypass restrictions, enhance online privacy, or securely connect remote workers to enterprise networks, OpenVPN provides a robust and flexible solution for various VPN needs. It is a key tool in the arsenal of IT admins and DevOps engineers who aim to ensure secure network access across distributed environments.</p>OpenVPN Status Log Monitoringhttps://www.netdata.cloud/monitoring-101/openvpn-status-log-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/openvpn-status-log-monitoring/<h2 id="what-is-openvpn-status-log">What is OpenVPN Status Log?</h2> <p>Netdata parses server log files and provides summary (client, traffic) metrics. Unlike the OpenVPN collector which requires management interface to be enabled.</p> <h2 id="monitoring-openvpn-status-log-with-netdata">Monitoring OpenVPN Status Log with Netdata</h2> <p>Netdata auto discovers hundreds of services, and for those it doesn&rsquo;t turning on manual discovery is a one line configuration. For more information on configuring Netdata for OpenVPN Status Log monitoring please read the collector <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/openvpn_status_log/">documentation</a>.</p> <p>Netdata has a public <a href="https://app.netdata.cloud/spaces/netdata-demo/">demo space</a> (no login required) where you can explore different monitoring use-cases and get a feel for Netdata.</p>OpenVPN Status Log Monitoringhttps://www.netdata.cloud/monitoring-101/openvpn_status_log-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/openvpn_status_log-monitoring/<h2 id="openvpn-monitoring">OpenVPN Monitoring</h2> <h3 id="what-is-openvpn">What Is OpenVPN?</h3> <p>OpenVPN is a widely-used open-source VPN protocol designed to secure point-to-point or site-to-site connections in routed or bridged configurations. With a versatile range of applications, it provides secure communication by encrypting data and passing it through secure virtual tunnels. Learn more about OpenVPN on their <a href="https://openvpn.net/">official website</a>.</p> <h3 id="monitoring-openvpn-with-netdata">Monitoring OpenVPN With Netdata</h3> <p>Monitoring an OpenVPN setup ensures that your VPN service maintains high performance and reliability. With Netdata, you can monitor OpenVPN by collecting and visualizing metrics in real-time. This allows you to assess your VPN&rsquo;s health proactively and troubleshoot efficiently, safeguarding your network&rsquo;s privacy and integrity.</p>OpenWeatherMap Monitoringhttps://www.netdata.cloud/monitoring-101/openweathermap-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/openweathermap-monitoring/<h2 id="openweathermap-monitoring">OpenWeatherMap Monitoring</h2> <h3 id="what-is-openweathermap">What Is OpenWeatherMap?</h3> <p>OpenWeatherMap is a widely-used platform that delivers a comprehensive range of weather data and air pollution metrics. It serves as an invaluable tool for developers, IT admins, and engineers looking to incorporate real-time weather data into their applications. With OpenWeatherMap, you can access detailed weather information that is crucial for environmental monitoring and analysis, enabling smarter business decisions.</p> <h3 id="monitoring-openweathermap-with-netdata">Monitoring OpenWeatherMap With Netdata</h3> <p>Monitoring OpenWeatherMap with Netdata involves using an openmetrics (Prometheus) exporter. <a href="https://www.netdata.cloud/?utm_source=website&amp;utm_content=monitoring101">Netdata</a> is capable of ingesting data from any Prometheus-compatible exporter, including the <a href="https://github.com/Tenzer/openweathermap-exporter">OpenWeatherMap Exporter</a>. This integration eliminates the need for a separate Prometheus server or Grafana dashboards, as Netdata provides automatically generated dashboards, real-time alerts, and more. By leveraging Netdata&rsquo;s powerful monitoring capabilities, you gain seamless access to critical weather and environmental metrics, ensuring efficient monitoring and analysis.</p>Optical Modules Monitoringhttps://www.netdata.cloud/monitoring-101/ethtool-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/ethtool-monitoring/<h2 id="optical-modules-monitoring">Optical Modules Monitoring</h2> <h3 id="what-is-optical-modules">What Is Optical Modules?</h3> <p>Optical modules are integral components in network environments, tasked with converting electrical signals to optical signals and vice versa for data transmission over fiber optic networks. They are pivotal in ensuring seamless connectivity across high-speed networks. These modules, such as SFP and DDM, support a range of diagnostic features that can be leveraged for efficient monitoring and maintenance.</p> <h3 id="monitoring-optical-modules-with-netdata">Monitoring Optical Modules With Netdata</h3> <p>Using Netdata, you can effectively monitor optical modules with the <a href="https://man7.org/linux/man-pages/man8/ethtool.8.html">ethtool</a> collector. Built into Netdata&rsquo;s go.d.plugin, this tool provides real-time insights into essential diagnostic parameters like temperature, voltage, laser bias current, and power levels. Access the <a href="https://www.netdata.cloud/integrations/data-collection/networking/optical-modules/">Optical Modules collector documentation</a> to get started quickly.</p>Patroni Monitoringhttps://www.netdata.cloud/monitoring-101/patroni-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/patroni-monitoring/<h2 id="patroni-monitoring">Patroni Monitoring</h2> <h3 id="what-is-patroni">What Is Patroni?</h3> <p>Patroni is an open-source high-availability solution for PostgreSQL databases, providing automatic failover and reliable replication solutions. It is designed to be easy to configure and highly reliable, making it a popular choice for database administrators who require robust failover management.</p> <h3 id="monitoring-patroni-with-netdata">Monitoring Patroni With Netdata</h3> <p>Monitoring Patroni with Netdata gives users real-time insights into their Patroni clusters. By utilizing an openmetrics (Prometheus) exporter like <a href="https://github.com/gopaytech/patroni_exporter">Patroni Exporter</a>, Netdata can seamlessly ingest metrics from any Prometheus exporter, allowing for automated dashboards, alerts, and more—all without the need for a Prometheus server or Grafana setup. This approach ensures that you have everything you need to monitor Patroni efficiently with minimal setup.</p>Personal Weather Station Monitoringhttps://www.netdata.cloud/monitoring-101/pws-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/pws-monitoring/<h2 id="personal-weather-station-monitoring">Personal Weather Station Monitoring</h2> <h3 id="what-is-personal-weather-station">What Is Personal Weather Station?</h3> <p>A Personal Weather Station (PWS) allows individuals and enthusiasts to set up their own weather monitoring system, offering localized weather metrics that aren&rsquo;t typically available from larger public weather services. These stations can provide real-time data on temperature, humidity, wind speed, rainfall, and other atmospheric conditions.</p> <h3 id="monitoring-personal-weather-station-with-netdata">Monitoring Personal Weather Station With Netdata</h3> <p>To monitor a Personal Weather Station effectively, Netdata employs an openmetrics (Prometheus) exporter. This seamless integration allows Netdata to ingest data from any Prometheus exporter, providing automated dashboards, alerts, and more—without the need for setting up a Prometheus server or Grafana. The <a href="https://github.com/JohnOrthoefer/pws-exporter">Personal Weather Station Exporter</a> is an essential tool in this process, enabling efficient real-time monitoring and tracking of weather data.</p>pgBackRest Monitoringhttps://www.netdata.cloud/monitoring-101/pgbackrest-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/pgbackrest-monitoring/<h2 id="pgbackrest-monitoring">pgBackRest Monitoring</h2> <h3 id="what-is-pgbackrest">What Is pgBackRest?</h3> <p>pgBackRest is a reliable, efficient, and secure backup solution for PostgreSQL databases. It offers advanced functionality for backup and restore, including full, differential, and incremental backups, along with support for parallelism, compression, and encryption. This ensures that your databases are efficiently managed and protected against data loss.</p> <h3 id="monitoring-pgbackrest-with-netdata">Monitoring pgBackRest With Netdata</h3> <p>Monitoring pgBackRest can be seamlessly integrated into your infrastructure using Netdata. Netdata uses an openmetrics (Prometheus) exporter for pgBackRest, allowing you to efficiently track metrics. Netdata&rsquo;s pgBackRest monitoring tool can ingest data from any Prometheus exporter, automatically generating insightful dashboards and setting up alerts — all without needing a separate Prometheus server or Grafana setup. This integration simplifies the monitoring process and provides real-time visualization of pgBackRest&rsquo;s performance metrics.</p>PgBouncer Monitoringhttps://www.netdata.cloud/monitoring-101/pgbouncer-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/pgbouncer-monitoring/<h2 id="pgbouncer-monitoring">PgBouncer Monitoring</h2> <h3 id="what-is-pgbouncer">What Is PgBouncer?</h3> <p><a href="https://www.pgbouncer.org/">PgBouncer</a> is a lightweight connection pooler for PostgreSQL that aims to reduce the overhead of establishing connections to a PostgreSQL database server. It excels in handling large numbers of connection requests to ensure efficient resource usage and smoother database operations.</p> <h3 id="monitoring-pgbouncer-with-netdata">Monitoring PgBouncer With Netdata</h3> <p>Netdata, a comprehensive real-time monitoring solution, provides an invaluable toolset to monitor PgBouncer. With Netdata, you can visualize and understand your PgBouncer instances deeply, using real-time visualizations of key metrics that help to diagnose issues and improve performance.</p>Pgpool-II Monitoringhttps://www.netdata.cloud/monitoring-101/pgpool2-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/pgpool2-monitoring/<h2 id="pgpool-ii-monitoring">Pgpool-II Monitoring</h2> <h3 id="what-is-pgpool-ii">What Is Pgpool-II?</h3> <p>Pgpool-II is an essential middleware tool for PostgreSQL databases, allowing for significant improvements in connection pooling, load balancing, and data replication. Designed to handle database connections more efficiently, Pgpool-II helps to maximize your database&rsquo;s performance and scalability. This makes it an ideal choice for developers, DevOps, and SRE professionals who focus on optimizing database operations.</p> <h3 id="monitoring-pgpool-ii-with-netdata">Monitoring Pgpool-II With Netdata</h3> <p>Monitoring Pgpool-II is crucial for ensuring the performance and reliability of your database systems. Netdata offers a powerful solution for Pgpool-II monitoring by utilizing an openmetrics (Prometheus) exporter. This means that Netdata can seamlessly integrate data from any Prometheus exporter, providing automated dashboards, intelligent alerts, and more, all without the need for a separate Prometheus server or Grafana setup. With Netdata, monitoring Pgpool-II becomes effortless, allowing you to focus on what truly matters—analyzing performance data and making informed decisions.</p>Philips Hue Monitoringhttps://www.netdata.cloud/monitoring-101/philips_hue-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/philips_hue-monitoring/<h2 id="philips-hue-monitoring">Philips Hue Monitoring</h2> <h3 id="what-is-philips-hue">What Is Philips Hue?</h3> <p>Philips Hue is a smart lighting system that allows users to control light fixtures remotely and automate lighting setups to improve home automation and energy efficiency. With a range of bulbs and accessories, Philips Hue integrates seamlessly into a connected home environment.</p> <h3 id="monitoring-philips-hue-with-netdata">Monitoring Philips Hue With Netdata</h3> <p>To monitor Philips Hue, Netdata employs an openmetrics (Prometheus) exporter. The integration allows Netdata to collect metrics from Philips Hue using the <a href="https://github.com/aexel90/hue_exporter">Philips Hue Exporter</a>. This setup enables users to have access to automated dashboards, alerts, and more, all without requiring a separate Prometheus server or Grafana installation. With Netdata&rsquo;s real-time monitoring capabilities, you can ensure that your Philips Hue system is running efficiently and effectively.</p>PHP-FPM Monitoringhttps://www.netdata.cloud/monitoring-101/phpfpm-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/phpfpm-monitoring/<h2 id="php-fpm-monitoring">PHP-FPM Monitoring</h2> <h3 id="what-is-php-fpm">What Is PHP-FPM?</h3> <p>PHP-FPM (FastCGI Process Manager) is a PHP FastCGI implementation, primarily focused on managing heavy-loaded web applications that demand high performance and fast execution. It is an alternative PHP FastCGI implementation with some additional features useful for sites of any size, especially busier sites. <a href="https://php-fpm.org/">Learn more about PHP-FPM</a>.</p> <h3 id="monitoring-php-fpm-with-netdata">Monitoring PHP-FPM With Netdata</h3> <p>To effectively monitor PHP-FPM, you need real-time insights into its performance and workload. Netdata provides a comprehensive PHP-FPM monitoring tool capable of capturing in-depth metrics with minimal configuration. Netdata’s intuitive UI and detailed charts allow you to visualize PHP-FPM’s operation and pinpoint performance bottlenecks swiftly.</p>phpDaemon Monitoringhttps://www.netdata.cloud/monitoring-101/phpdaemon-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/phpdaemon-monitoring/<h2 id="phpdaemon-monitoring">phpDaemon Monitoring</h2> <h3 id="what-is-phpdaemon">What Is phpDaemon?</h3> <p>phpDaemon is an advanced asynchronous server-side daemon for PHP that can efficiently handle diverse application workloads by relying on an event-driven architecture. It is particularly suited for applications requiring persistent connections and rapid response times.</p> <h3 id="monitoring-phpdaemon-with-netdata">Monitoring phpDaemon With Netdata</h3> <p>Netdata offers a comprehensive monitoring solution for phpDaemon, showcasing a range of metrics in real time. By integrating the Netdata Agent with your phpDaemon instance, you can enjoy insightful visual data right at your fingertips, utilize historical insights, and diagnose issues seamlessly. <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/phpdaemon/">Read the phpDaemon collector documentation</a> to get started.</p>Pi-hole Monitoringhttps://www.netdata.cloud/monitoring-101/pihole-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/pihole-monitoring/<h2 id="pi-hole-monitoring">Pi-hole Monitoring</h2> <h3 id="what-is-pi-hole">What Is Pi-hole?</h3> <p>Pi-hole is a popular network-wide ad blocker that functions as a DNS sinkhole. It blocks unwanted content by intercepting DNS queries and preventing ads and trackers, enabling a cleaner and faster web browsing experience. Its efficiency and open-source nature make it a favorite among privacy-conscious users.</p> <h3 id="monitoring-pi-hole-with-netdata">Monitoring Pi-hole With Netdata</h3> <p>To ensure Pi-hole runs optimally, monitoring is essential. With <a href="https://www.netdata.cloud">Netdata</a>, you gain real-time insights into your Pi-hole metrics, identifying trends and spot anomalies quickly. Netdata supports Pi-hole monitoring via its <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/pihole/">pi-hole collector module</a>, collecting various DNS statistics from the Pi-hole API 6.0, including total queries, blocked domains, and client information.</p>Pika Monitoringhttps://www.netdata.cloud/monitoring-101/pika-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/pika-monitoring/<h2 id="pika-monitoring">Pika Monitoring</h2> <h3 id="what-is-pika">What Is Pika?</h3> <p>Pika is a NoSQL database server, designed for high concurrency and scalability, compatible with Redis protocol. Pika adds persistence to the Redis dataset and is engineered to support large datasets while maintaining excellent performance.</p> <h3 id="monitoring-pika-with-netdata">Monitoring Pika With Netdata</h3> <p>Using <a href="https://app.netdata.cloud/?utm_source=website&amp;utm_content=monitoring101">Netdata</a> as your Pika monitoring tool provides real-time insights and comprehensive metrics from your Pika servers. By leveraging Netdata&rsquo;s monitoring capabilities, you&rsquo;ll gain visibility into system operations, enabling you to diagnose issues and optimize performance efficiently.</p>Pimoroni Enviro+ Monitoringhttps://www.netdata.cloud/monitoring-101/pimoroni_enviro_plus-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/pimoroni_enviro_plus-monitoring/<h2 id="pimoroni-enviro-monitoring">Pimoroni Enviro+ Monitoring</h2> <h3 id="what-is-pimoroni-enviro">What Is Pimoroni Enviro+?</h3> <p>The Pimoroni Enviro+ is a sophisticated environmental monitoring device equipped to track air quality and other environmental data. Outfitted with various sensors, it allows developers and environmental enthusiasts to collect crucial data for analysis and decision-making. Its capabilities are particularly essential for IoT projects that require precise environmental readings.</p> <h3 id="monitoring-pimoroni-enviro-with-netdata">Monitoring Pimoroni Enviro+ With Netdata</h3> <p>When it comes to effectively monitor Pimoroni Enviro+, Netdata stands out as a robust monitoring tool. Netdata utilizes an openmetrics (Prometheus) exporter to seamlessly ingest data from the Pimoroni Enviro+. By using this method, you can avoid the hassle of setting up and maintaining a separate Prometheus server or Grafana dashboards. Netdata provides automated dashboards and alerting mechanisms, making the monitoring process straightforward and efficient.</p>Ping Monitoringhttps://www.netdata.cloud/monitoring-101/ping-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/ping-monitoring/<h2 id="ping-monitoring">Ping Monitoring</h2> <h3 id="what-is-ping">What Is Ping?</h3> <p>Ping is a network administration tool used to test the reachability of a host on an Internet Protocol (IP) network. It works by sending Internet Control Message Protocol (ICMP) Echo Request packets to the target host and waiting for a response. This basic utility is fundamental in diagnosing network connections and performance issues, making it a critical tool for IT professionals.</p> <h3 id="monitoring-ping-with-netdata">Monitoring Ping With Netdata</h3> <p>When it comes to monitoring ping, Netdata provides a comprehensive solution through its go.d.plugin with the ping module. This $name monitoring tool assesses network performance by measuring round-trip time (RTT) and packet loss, offering valuable insights into the health and reliability of your network connections. With Netdata, you can monitor ping in real-time, visualize trends, identify bottlenecks, and troubleshoot issues efficiently.</p>Podman Monitoringhttps://www.netdata.cloud/monitoring-101/podman-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/podman-monitoring/<h2 id="podman-monitoring">Podman Monitoring</h2> <h3 id="what-is-podman">What Is Podman?</h3> <p>Podman is a platform and service designed to manage and run containers from the CLI. It allows developers and IT administrators to create, deploy, and maintain containerized applications. Unlike Docker, Podman operates without a central daemon and can run in a rootless mode, offering more flexibility and security.</p> <h3 id="monitoring-podman-with-netdata">Monitoring Podman With Netdata</h3> <p>Monitoring Podman can be a game-changer for maintaining optimal performance of your containerized applications. Netdata provides a robust Podman monitoring tool powered by an openmetrics (Prometheus) exporter—<a href="https://github.com/containers/prometheus-podman-exporter">Prometheus Podman Exporter</a>. Netdata can ingest data from any Prometheus exporter, enabling you to monitor Podman extensively without requiring a Prometheus server or Grafana. This functionality comes with ready-to-use dashboards and alerts for a seamless monitoring experience.</p>Postfix Monitoringhttps://www.netdata.cloud/monitoring-101/postfix-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/postfix-monitoring/<h2 id="postfix-monitoring">Postfix Monitoring</h2> <h3 id="what-is-postfix">What Is Postfix?</h3> <p>Postfix is a well-known open-source mail transfer agent (MTA) used by systems administrators to manage and route email communications across networks. It is reputed for its robustness and efficiency, making it a popular choice among users looking to handle mail server tasks effectively. <a href="https://www.postfix.org/">Learn more about Postfix</a>.</p> <h3 id="monitoring-postfix-with-netdata">Monitoring Postfix With Netdata</h3> <p>To effectively monitor Postfix, leveraging a real-time monitoring tool like Netdata is invaluable. By utilizing <a href="https://www.netdata.cloud/integrations/data-collection/applications/postfix/">Netdata&rsquo;s collector for Postfix</a>, you can access critical insights about your mail server&rsquo;s activities. The integration is seamless, allowing you to diagnose issues promptly and maintain the health of your email infrastructure. To see it in action, <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">check out the Live Demo</a>.</p>PostgreSQL ALTER TABLE blocked: zero-downtime DDL patternshttps://www.netdata.cloud/guides/postgres/postgres-alter-table-blocked/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-alter-table-blocked/<p>An <code>ALTER TABLE</code> to add a column or change a type hangs. Application queries time out. Connection pools saturate. What looked like a simple schema change becomes a production incident.</p> <p>By default, <code>ALTER TABLE</code> acquires an <code>ACCESS EXCLUSIVE</code> lock. It conflicts with every other lock mode, including <code>ACCESS SHARE</code> held by a plain <code>SELECT</code>. Once the DDL statement queues behind a blocker, every subsequent read and write on that table queues behind the waiting DDL. The table goes offline before the <code>ALTER TABLE</code> executes any work.</p>PostgreSQL autovacuum blocked by long-running transaction: detection and fixhttps://www.netdata.cloud/guides/postgres/postgres-autovacuum-blocked-by-long-transaction/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-autovacuum-blocked-by-long-transaction/<p>Autovacuum workers are active, but <code>n_dead_tup</code> climbs and queries slow down as they scan dead tuples. Table bloat grows because <code>VACUUM</code> cannot reclaim dead row versions: a long-running transaction, abandoned replication slot, or hot-standby feedback is pinning the <strong>xmin horizon</strong> cluster-wide. The worker is not broken; it is blocked by an older transaction ID that must remain visible.</p> <h2 id="what-this-means">What this means</h2> <p>PostgreSQL&rsquo;s MVCC keeps old tuple versions in the table until <code>VACUUM</code> removes them. <code>VACUUM</code> cannot remove any tuple that might still be visible to an active transaction. The boundary is the <strong>xmin horizon</strong>: the oldest transaction ID still active anywhere in the cluster.</p>PostgreSQL autovacuum not running: detection, causes, and fixeshttps://www.netdata.cloud/guides/postgres/postgres-autovacuum-not-running/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-autovacuum-not-running/<p>Table sizes grow faster than insert rates. Query latency creeps up on UPDATE-heavy workloads. <code>pg_stat_user_tables.n_dead_tup</code> climbs while <code>last_autovacuum</code> stays frozen. Autovacuum should clean this up, but it is not. Dead tuple accumulation degrades performance and can eventually trigger transaction-ID-wraparound shutdown. Detect why autovacuum is stalled, find the blocker, and fix it without making things worse.</p> <h2 id="what-this-means">What this means</h2> <p>Autovacuum is a background subsystem that spawns workers to run <code>VACUUM</code> and <code>ANALYZE</code> based on table-level thresholds. When it works, it reclaims dead tuple space, updates the free space map, maintains the visibility map, and freezes old transaction IDs to prevent wraparound. When it stops, effects cascade: table and index bloat grow, sequential scans read more dead pages, the planner chooses worse plans as statistics stale, and database age advances toward the 2-billion-transaction hard limit.</p>PostgreSQL autovacuum tuning: per-table thresholds for high-churn workloadshttps://www.netdata.cloud/guides/postgres/postgres-autovacuum-tuning/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-autovacuum-tuning/<p>Default autovacuum settings target modest OLTP workloads. On a 500-million-row table, the global <code>autovacuum_vacuum_scale_factor</code> of 0.2 means autovacuum ignores the table until dead tuples exceed twenty percent of the row count. For high-churn tables, that delay lets bloat accumulate, degrades indexes, slows scans, and pushes transaction ID age toward wraparound. PostgreSQL overrides these thresholds per table via storage parameters (reloptions), so a 50 GB hot table can run aggressive settings without saturating workers across a 500 MB reference table. This guide covers calculating overrides, sizing worker memory, and verifying vacuum keeps up without drowning the cluster in background I/O.</p>PostgreSQL backup strategy: pg_dump, pg_basebackup, and pgBackRest comparedhttps://www.netdata.cloud/guides/postgres/postgres-backup-strategy/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-backup-strategy/<p>Your backup tool determines your RPO, RTO, and whether you can restore to a point in time or only to the backup moment. This guide compares logical dumps via <code>pg_dump</code>, built-in physical copies via <code>pg_basebackup</code>, and the third-party tool pgBackRest. PostgreSQL 17 introduced native incremental physical backups. Operators must decide whether built-in capabilities are sufficient or whether to adopt alternatives such as Barman or WAL-G.</p> <h2 id="pg_dump-and-pg_dumpall-logical-portability">pg_dump and pg_dumpall: logical portability</h2> <p><code>pg_dump</code> and <code>pg_dumpall</code> use an MVCC snapshot to produce a logically consistent SQL archive without blocking reads. Use <code>--table</code> or <code>--schema</code> for selective extraction. Parallel dumps use <code>--jobs</code> with directory format (<code>-Fd</code>) or custom format (<code>-Fc</code>):</p>PostgreSQL Blocking Queries: Finding The Root Blocker In A Lock Cascadehttps://www.netdata.cloud/guides/postgres/postgres-blocking-queries/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-blocking-queries/<p>A query that normally finishes in milliseconds is now running for minutes. <code>pg_stat_activity</code> shows a queue of sessions with <code>wait_event_type = 'Lock'</code>. You identify one session holding the contested lock, but terminating it does not clear the queue. That session was itself blocked by another, which was blocked by another. Until you find the session at the head of the chain, the cascade continues.</p> <p>Use this guide to traverse the lock graph, distinguish direct blockers from the root blocker, and decide whether to terminate or wait. It applies to self-managed PostgreSQL, RDS, Aurora, and containerized deployments where you have access to <code>pg_stat_activity</code> and <code>pg_locks</code>.</p>PostgreSQL checkpoint storms: detection, causes, and tuninghttps://www.netdata.cloud/guides/postgres/postgres-checkpoint-storms/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-checkpoint-storms/<p>If query latency spikes and TPS drops coincide with your <code>checkpoint_timeout</code> schedule or follow a large bulk load, you are likely hitting a checkpoint storm. PostgreSQL checkpoints guarantee that dirty buffers are on disk. In a healthy system, timed checkpoints occur at <code>checkpoint_timeout</code> intervals and the background writer spreads that I/O. A storm happens when WAL generation hits <code>max_wal_size</code> before the timeout, forcing a requested checkpoint that flushes most dirty buffers at once, saturating disk bandwidth and stalling queries.</p>PostgreSQL Connection Exhaustion: Detection, Diagnosis & Preventionhttps://www.netdata.cloud/guides/postgres/postgres-connection-exhaustion/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-connection-exhaustion/<p>Application logs show <code>FATAL: sorry, too many clients already</code>. Health checks are failing. A rolling deploy just finished, and now the database is rejecting connections. Because PostgreSQL uses one process per connection, every slot consumes memory and scheduler overhead. Once <code>max_connections</code> is reached, the server refuses new backends entirely. Raising <code>max_connections</code> without fixing the root cause increases memory pressure and context-switch thrashing. This guide covers how to distinguish a true capacity shortage from a leak or pool misconfiguration, how to recover safely, and how to prevent recurrence.</p>PostgreSQL connection refused: pg_hba, listen_addresses, and TCP diagnosishttps://www.netdata.cloud/guides/postgres/postgres-connection-refused/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-connection-refused/<p>An application cannot reach PostgreSQL. The client reports either &ldquo;Connection refused,&rdquo; a hang until timeout, or &ldquo;no pg_hba.conf entry.&rdquo; These three symptoms point to different layers. Mixing them up leads to wasted restarts, overly broad firewall rules, or <code>pg_hba.conf</code> edits that never take effect. Work through the transport layer first, then the network path, then the authorization layer.</p> <p>PostgreSQL defaults to binding only to the loopback interface. A fresh installation or container image rejects remote TCP attempts before <code>pg_hba.conf</code> is consulted. Changing <code>listen_addresses</code> requires a restart; changing <code>pg_hba.conf</code> only requires a reload. The diagnostic sequence is: confirm the listener, confirm the path, then confirm the rule.</p>PostgreSQL dead tuples piling up: why autovacuum can't keep uphttps://www.netdata.cloud/guides/postgres/postgres-dead-tuples-piling-up/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-dead-tuples-piling-up/<p>Table sizes grow faster than insert rates, and queries that scanned thousands of rows last week now scan millions. <code>pg_stat_user_tables</code> shows <code>n_dead_tup</code> climbing into the millions while <code>last_autovacuum</code> is stale or absent. Autovacuum is running somewhere in the cluster, but it is losing the race.</p> <p>PostgreSQL creates dead tuples on every <code>UPDATE</code> and <code>DELETE</code>. Autovacuum reclaims them only when the dead tuple count crosses a threshold. On large or high-churn tables, the default threshold is far too conservative, and even when vacuum does fire, long-running transactions, worker starvation, or streaming replica feedback can prevent tuple removal. The result is bloat: wasted space, slower scans, and eventually transaction ID wraparound risk.</p>PostgreSQL deadlock detected: how to diagnose and prevent deadlockshttps://www.netdata.cloud/guides/postgres/postgres-deadlock-detected/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-deadlock-detected/<p><code>ERROR: deadlock detected</code> means PostgreSQL aborted one transaction to break a circular wait-for graph. The victim returns SQLSTATE <code>40P01</code>; the application must retry it. Deadlocks are a safety mechanism, not a bug: they fire when concurrent transactions acquire locks in incompatible orders. Even a few per minute degrade user experience, burn retry budget, and mask deeper contention. This guide shows how to read the deadlock output, find the root cause, and stop the cycle.</p>PostgreSQL disk full: emergency recovery and root cause analysishttps://www.netdata.cloud/guides/postgres/postgres-disk-full/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-disk-full/<p>When <code>df -h</code> shows 100% utilization on the PostgreSQL data volume, queries fail with &ldquo;could not write to file&rdquo;. If <code>pg_wal</code> fills, the server enters PANIC and refuses to restart until space is freed. The fastest way to make the incident worse is to delete WAL files from <code>pg_wal</code> manually. PostgreSQL needs those files for crash recovery; removing them causes data inconsistency that forces a restore from backup. Identify which subsystem is consuming space, reclaim it safely, and fix the root cause before the cycle repeats.</p>PostgreSQL ERROR: Could Not Obtain Lock — Diagnosis & Recoveryhttps://www.netdata.cloud/guides/postgres/postgres-lock-not-available/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-lock-not-available/<p><code>ERROR: could not obtain lock on row in relation</code> and <code>ERROR: canceling statement due to lock timeout</code> mean a query requested a lock but PostgreSQL refused to wait. The database is not down; a session is holding a resource another transaction needs.</p> <p>Three variants produce these errors:</p> <ul> <li><code>SELECT ... FOR UPDATE NOWAIT</code> fails immediately if the row is locked.</li> <li>A statement that exceeds <code>lock_timeout</code> fails after waiting.</li> <li>DDL such as <code>ALTER TABLE</code> or <code>TRUNCATE</code> requires <code>AccessExclusiveLock</code> and will wait or fail depending on session configuration.</li> </ul> <p>These often cascade: one long-running query blocks a schema change, the schema change queues behind it, and subsequent queries queue behind the DDL until the <a >connection pool exhausts</a>.</p>PostgreSQL FATAL: Too Many Connections - Causes & Fixeshttps://www.netdata.cloud/guides/postgres/postgres-too-many-connections/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-too-many-connections/<p>Applications throw <code>FATAL: sorry, too many clients already</code>. Health checks fail. Retries amplify the problem. The database is not down, but it rejects new traffic.</p> <p><a href="https://www.netdata.cloud/guides/postgres/">PostgreSQL</a> uses a process-per-connection model. Every backend holds memory and scheduler time even when idle. Raising <code>max_connections</code> usually deepens the problem because the root cause is why slots are occupied and what those backends are doing.</p> <p>This guide shows how to diagnose <a href="https://www.netdata.cloud/guides/postgres/postgres-connection-exhaustion/">connection exhaustion</a>, distinguish PostgreSQL saturation from pooler exhaustion, and fix common root causes safely.</p>PostgreSQL frozen XID monitoring: catching wraparound 6 months earlyhttps://www.netdata.cloud/guides/postgres/postgres-frozen-xid-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-frozen-xid-monitoring/<p>Transaction ID wraparound is a slow burn, not a sudden crisis. The 32-bit XID counter advances with every transaction. If VACUUM freeze does not keep pace, PostgreSQL will eventually refuse new transactions to prevent data corruption. By the time built-in log warnings fire, you may have only hours of runway left. Monitor <code>age(datfrozenxid)</code> and <code>age(relfrozenxid)</code> with tiered thresholds so you act with months of lead time.</p> <p>To use those metrics effectively, you need to know what blocks freeze progress and which response matches each threshold tier. This guide covers the freeze mechanism, exact queries, common blocker patterns, and operational thresholds.</p>PostgreSQL Idle In Transaction: Detecting & Killing Zombie Sessionshttps://www.netdata.cloud/guides/postgres/postgres-idle-in-transaction/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-idle-in-transaction/<p>When <code>pg_stat_activity</code> fills with <code>idle in transaction</code> sessions, autovacuum stalls, dead tuples accumulate, and applications throw &ldquo;too many clients&rdquo; errors while backends sit idle. These zombie sessions hold a transaction snapshot. Under MVCC, this prevents VACUUM from reclaiming dead tuples created after the transaction started, causing table bloat, blocked DDL, and transaction-ID wraparound pressure.</p> <p>This guide shows how to detect these sessions, determine whether they are blocking work, terminate them safely, and prevent recurrence.</p>PostgreSQL index bloat: detection and REINDEX CONCURRENTLY recoveryhttps://www.netdata.cloud/guides/postgres/postgres-index-bloat/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-index-bloat/<p>Queries that used to return in milliseconds are now spiking to hundreds. Disk usage grows faster than insert volume. <code>EXPLAIN</code> shows a bitmap index scan pulling thousands of heap pages for a selective filter. The cause is usually index bloat: dead pages and fragmentation in B-tree indexes. Unlike table bloat, index bloat is not visible in <code>pg_stat_user_tables</code>, and it often degrades query latency or fills a volume before you notice it. Detect bloat with <code>pgstattuple</code> and recover online with <code>REINDEX CONCURRENTLY</code>.</p>PostgreSQL logical replication failures: conflicts, schema drift, and recoveryhttps://www.netdata.cloud/guides/postgres/postgres-logical-replication-failures/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-logical-replication-failures/<p>Your subscriber is behind. <code>pg_stat_subscription</code> shows a stalled LSN, the apply worker is throwing errors, or worse: replication appears healthy while the subscriber silently diverges from the publisher. Logical replication does not replicate DDL, does not resolve row conflicts automatically, and will halt on the first integrity error it encounters. When it breaks, the failure is often on the subscriber, but the root cause may be schema drift on either side, a forgotten replication slot on the publisher, or a local write that violated the assumption that the subscriber is read-only.</p>PostgreSQL major version upgrade: pg_upgrade, logical replication, and rollback planshttps://www.netdata.cloud/guides/postgres/postgres-major-version-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-major-version-upgrade/<p>A major version upgrade is one of the highest-risk maintenance operations on a PostgreSQL cluster. Storage format, system catalogs, and the query planner all change between major versions, so you cannot simply restart the server with new binaries. Every major upgrade is a migration, even when it happens on the same host.</p> <p>Most teams choose between two paths. <code>pg_upgrade</code> rewrites system catalogs while reusing or copying data files. It is fast but requires a downtime window. Logical replication streams row changes to a new cluster running the target version, enabling near-zero-downtime cutover but adding operational complexity. The wrong choice is usually the one made without understanding rollback boundaries.</p>PostgreSQL missing indexes: detection from pg_stat_statements and logshttps://www.netdata.cloud/guides/postgres/postgres-missing-indexes/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-missing-indexes/<p>When the planner cannot find a suitable index path, it falls back to a sequential scan. On large tables, this turns millisecond queries into multi second outages.</p> <p>PostgreSQL exposes evidence through built-in instrumentation: <code>pg_stat_user_tables</code> tracks sequential versus index scan ratios, <code>pg_stat_statements</code> surfaces the most time-consuming query fingerprints, and <code>auto_explain</code> logs execution plans that reveal <code>Seq Scan</code> nodes directly.</p> <p>This guide gives an operator workflow to detect missing indexes using read-only checks and hypothetical index simulation. It assumes <code>pg_stat_statements</code> is enabled; if not, adding it to <code>shared_preload_libraries</code> requires a server restart.</p>PostgreSQL Monitoringhttps://www.netdata.cloud/monitoring-101/postgres-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/postgres-monitoring/<h2 id="postgresql-monitoring">PostgreSQL Monitoring</h2> <h3 id="what-is-postgresql">What Is PostgreSQL?</h3> <p>PostgreSQL is a powerful, open-source object-relational database management system known for its robustness, extensibility, and standards compliance. <a href="https://www.postgresql.org/">Learn more about PostgreSQL</a>.</p> <h3 id="monitoring-postgresql-with-netdata">Monitoring PostgreSQL With Netdata</h3> <p>Netdata provides a comprehensive PostgreSQL monitoring tool that allows you to keep an eye on crucial metrics in real-time and diagnose potential performance issues effectively. Using the <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/postgres/">Netdata Agent&rsquo;s PostgreSQL module</a>, you can monitor various aspects of your database to ensure optimal performance.</p>PostgreSQL Monitoringhttps://www.netdata.cloud/monitoring-101/postgresql-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/postgresql-monitoring/<h2 id="whats-postgresql-and-why-monitor-it">What&rsquo;s PostgreSQL and why monitor it?</h2> <p>PostgreSQL is a popular open source object-relational database system designed to work for a wide range of workloads from single machines to data warehouses to web services with many concurrent users. PostgreSQL runs on all major operating systems and is used by teams and organizations across the world, including Netdata.</p> <p>If you are using PostgreSQL in production, it is crucial that you monitor it for potential issues. And the more comprehensive the monitoring the better!</p>PostgreSQL Monitoring Checklist: The Signals Every Production Database Needshttps://www.netdata.cloud/guides/postgres/postgres-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-monitoring-checklist/<p><a href="https://www.netdata.cloud/guides/postgres/">PostgreSQL</a> exposes hundreds of counters across the <code>pg_stat_*</code> views, yet most production outages trace back to a small set of undetected conditions. Bloat accumulates silently until vacuum cannot catch up. Replication lag grows until failover becomes a data-loss event. Transaction ID age crosses a threshold and the database stops accepting writes. The problem is rarely a lack of metrics. It is knowing which signals to instrument at each stage of operational maturity.</p>PostgreSQL Out Of Memory: OOM Killer, shared_buffers & work_memhttps://www.netdata.cloud/guides/postgres/postgres-out-of-memory/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-out-of-memory/<p>Your PostgreSQL primary restarts without warning, or individual backends vanish from the process list. The kernel log shows <code>Out of Memory: Killed process 12345 (postgres)</code>. Existing connections may survive, but new connections fail until the postmaster recovers. This is a memory accounting mismatch between Linux overcommit, PostgreSQL shared and private memory allocation, and how you size <code>shared_buffers</code> and <code>work_mem</code>.</p> <p>Inside Kubernetes or containers, the symptom is identical but the mechanism differs: cgroup v2 <code>memory.max</code> triggers an immediate SIGKILL with no ENOMEM grace period. In both cases, stop guessing at memory limits and start budgeting.</p>PostgreSQL pg_wal directory full: causes and emergency recoveryhttps://www.netdata.cloud/guides/postgres/postgres-wal-disk-full/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-wal-disk-full/<p>Your paging system fires because the PostgreSQL primary has stopped accepting writes. The error log reports a disk-full condition, and the WAL volume is at 100%. You cannot simply delete files from pg_wal to free space: doing so corrupts the database and breaks replication.</p> <p>PostgreSQL recycles WAL segments only after a checkpoint, and only when they are no longer needed for crash recovery, archiving, or replication slots. Archiving failures, stalled replication slots, or bulk loads that exceed max_wal_size cause unbounded accumulation. This guide covers identification, safe recovery, and prevention.</p>PostgreSQL replication lag: detection, diagnosis, and fixeshttps://www.netdata.cloud/guides/postgres/postgres-replication-lag/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-replication-lag/<p>Replication lag is the distance between the last WAL record generated on the primary and the last record applied on a replica. In asynchronous streaming replication, a few seconds of lag is normal. When lag grows without bound, your recovery point objective becomes fiction.</p> <p>Lag often grows silently. Replication processes stay connected, WAL streams flow, and uptime checks stay green while the byte gap creeps from megabytes to gigabytes. Promoting a replica that is hours behind destroys the consistency your application assumes.</p>PostgreSQL replication slot bloat: when a stale slot fills the diskhttps://www.netdata.cloud/guides/postgres/postgres-replication-slot-bloat/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-replication-slot-bloat/<p>Disk is filling on the primary. Table sizes are stable and active replicas show healthy replication lag, but WAL in pg_wal keeps growing and is not being recycled. The most likely cause is a stale replication slot. When a logical subscriber, CDC connector, or physical replica disconnects without cleaning up its slot, PostgreSQL retains every WAL segment from the slot&rsquo;s restart_lsn onward. This retention ignores max_wal_size unless max_slot_wal_keep_size is set to a finite value. The default is -1 (unlimited). The primary will retain WAL until the disk fills and writes halt. This guide covers confirmation, recovery, and prevention.</p>PostgreSQL Slow Queries: Diagnosis From Log To Plan To Fixhttps://www.netdata.cloud/guides/postgres/postgres-slow-queries-diagnosis/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-slow-queries-diagnosis/<p>A query that returned in 10 ms yesterday is now taking 8 seconds. No deploys, no schema changes. Before adding an index or restarting the database, determine whether the slowness is in the plan, the data, or the environment. This guide covers a three-layer workflow: log-based discovery with <code>log_min_duration_statement</code>, aggregate profiling with <code>pg_stat_statements</code>, and per-query execution plan capture with <code>auto_explain</code> and manual <code>EXPLAIN (ANALYZE, BUFFERS)</code>.</p> <pre class="mermaid" data-source="markdown-fence">flowchart TD A[Slow query reported] --> B[Check pg_stat_statements for mean_exec_time and stddev_exec_time] B --> C{High stddev relative to mean?} C -->|Yes| D[Plan flapping or parameter skew] C -->|No| E[Stable plan or system bottleneck] D --> F[Capture plan with auto_explain or EXPLAIN] E --> F F --> G{Estimated rows far from actual?} G -->|Yes| H[Stale statistics or skewed data] G -->|No| I[Bloat, locks, or cache pressure]</pre> <h2 id="what-this-means">What This Means</h2> <p>A slow query is a symptom. <a href="https://www.netdata.cloud/guides/postgres/">PostgreSQL&rsquo;s planner</a> chooses a path based on statistics from <code>ANALYZE</code>, bound parameter values, and configuration such as <code>work_mem</code>. When these inputs change, the same query text can switch from a hash join to a nested loop and slow down by orders of magnitude.</p>PostgreSQL table bloat: detection, measurement, and remediationhttps://www.netdata.cloud/guides/postgres/postgres-table-bloat/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-table-bloat/<p>Table bloat appears as tables growing while row counts stay flat, sequential scans slowing despite indexes, and disk alarms that do not track business growth. PostgreSQL&rsquo;s MVCC writes new tuple versions instead of overwriting old ones; every UPDATE leaves a dead row and every DELETE leaves invisible garbage. VACUUM reclaims that space for reuse within the file, but plain VACUUM does not shrink the relation on disk. When dead tuples outpace cleanup, a table can become several times larger than its logical content.</p>PostgreSQL transaction ID wraparound: detection and emergency recoveryhttps://www.netdata.cloud/guides/postgres/postgres-transaction-id-wraparound/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-transaction-id-wraparound/<p>PostgreSQL can suddenly stop accepting writes and emit warnings that the database must be vacuumed within a shrinking number of transactions. This is transaction ID wraparound. It is not gradual performance degradation; it is a hard stop that can take a database offline for hours if old tuples are not frozen in time.</p> <p>Every write transaction consumes a 32-bit XID. After roughly two billion transactions, the counter nears the point where older tuples could appear to belong to the future, corrupting visibility. PostgreSQL refuses to hand out new XIDs once fewer than roughly three million remain. Warnings appear at roughly forty million remaining. The defense is VACUUM freeze, which marks old rows with FrozenTransactionId so they no longer depend on the live counter.</p>PostgreSQL: checkpoints are occurring too frequently -- what to tunehttps://www.netdata.cloud/guides/postgres/postgres-checkpoints-occurring-too-frequently/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-checkpoints-occurring-too-frequently/<p>Your PostgreSQL logs show <code>LOG: checkpoints are occurring too frequently (9 seconds apart)</code> with the hint <code>Consider increasing the configuration parameter 'max_wal_size'</code>. Sustained I/O latency spikes correlate with WAL segment rotation. On write-heavy primaries, this almost always means <code>max_wal_size</code> is too small for the workload.</p> <p>A checkpoint flushes all dirty shared buffers to disk. By default, a checkpoint fires every 5 minutes (<code>checkpoint_timeout</code>) or every 1 GB of WAL (<code>max_wal_size</code>), whichever comes first. On a busy OLTP primary, 1 GB of WAL can accumulate in minutes. When <code>max_wal_size</code> triggers the checkpoint, you get a forced (requested) checkpoint. These are unpredictable, collide with existing write load, and cause visible latency spikes.</p>PostgreSQL: database is not accepting commands to avoid wraparound data losshttps://www.netdata.cloud/guides/postgres/postgres-database-not-accepting-commands/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-database-not-accepting-commands/<p>Writes fail abruptly. SELECT still works, but INSERT, UPDATE, DELETE, and DDL return an error like:</p> <pre tabindex="0"><code>ERROR: database is not accepting commands that assign new transaction IDs to avoid wraparound data loss in database &#34;...&#34; </code></pre><p>This is PostgreSQL&rsquo;s emergency brake, not a crash. The engine has stopped issuing new transaction IDs to prevent tuple visibility corruption. Modern PostgreSQL lets you recover without restarting or entering single-user mode. Remove whatever is blocking VACUUM progress, then freeze old rows.</p>PowerDNS Monitoringhttps://www.netdata.cloud/monitoring-101/powerdns-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/powerdns-monitoring/<h2 id="powerdns-monitoring">PowerDNS Monitoring</h2> <h3 id="what-is-powerdns">What Is PowerDNS?</h3> <p>PowerDNS Authoritative Server is a versatile and highly efficient DNS server software that forms a pivotal part of many IT infrastructures. Renowned for its performance capabilities and extensive management features, PowerDNS provides authoritative DNS services that cater to a wide range of deployment scenarios.</p> <h3 id="monitoring-powerdns-with-netdata">Monitoring PowerDNS With Netdata</h3> <p>Netdata offers a comprehensive PowerDNS monitoring solution that allows you to track, visualize, and analyze real-time data from your PowerDNS instances. By leveraging the Netdata platform, which is acclaimed for its simplicity and effectiveness, you can gain insights into server performance, diagnose potential issues, and ensure optimal service delivery.</p>PowerDNS Recursor Monitoringhttps://www.netdata.cloud/monitoring-101/powerdns-recursor-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/powerdns-recursor-monitoring/<h2 id="what-is-powerdns-recursor">What is PowerDNS Recursor?</h2> <p><a href="https://doc.powerdns.com/recursor/"><code>PowerDNS Recursor</code></a> is a high-performance DNS recursor with built-in scripting capabilities.</p> <h2 id="monitoring-powerdns-recursor-with-netdata">Monitoring PowerDNS Recursor with Netdata</h2> <p>The prerequisites for monitoring PowerDNS Recursor with Netdata are to have PowerDNS Recursor and <a href="https://learn.netdata.cloud/docs/cloud/get-started/">Netdata installed</a> on your system.</p> <p>Netdata auto discovers hundreds of services, and for those it doesn&rsquo;t turning on manual discovery is a one line configuration. For more information on configuring Netdata for PowerDNS Recursor monitoring please read the collector <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/powerdns_recursor/">documentation</a>.</p>PowerDNS Recursor Monitoringhttps://www.netdata.cloud/monitoring-101/powerdns_recursor-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/powerdns_recursor-monitoring/<h2 id="powerdns-recursor-monitoring">PowerDNS Recursor Monitoring</h2> <h3 id="what-is-powerdns-recursor">What Is PowerDNS Recursor?</h3> <p>PowerDNS Recursor is a high-performance DNS server used by service providers to resolve web traffic efficiently. Designed with a focus on scalability and security, the PowerDNS Recursor acts as the backbone of DNS infrastructure in complex network setups, maintaining trust and performance at scale.</p> <h3 id="monitoring-powerdns-recursor-with-netdata">Monitoring PowerDNS Recursor With Netdata</h3> <p>When it comes to monitoring PowerDNS Recursor, Netdata offers a comprehensive <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/powerdns_recursor/">PowerDNS Recursor monitoring tool</a>. Using Netdata, you can monitor key metrics such as incoming and outgoing questions, answer times, timeouts, and cache usage with real-time precision.</p>Powerpal Devices Monitoringhttps://www.netdata.cloud/monitoring-101/powerpal-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/powerpal-monitoring/<h2 id="powerpal-devices-monitoring">Powerpal Devices Monitoring</h2> <h3 id="what-is-powerpal-devices">What Is Powerpal Devices?</h3> <p>Powerpal devices are innovative IoT-driven smart meters that allow users to efficiently track their energy consumption in real-time. Designed to promote energy efficiency, they provide detailed insights into electricity usage, enabling homeowners and businesses to make informed decisions about their energy consumption strategies.</p> <h3 id="monitoring-powerpal-devices-with-netdata">Monitoring Powerpal Devices With Netdata</h3> <p>When it comes to monitoring Powerpal devices, Netdata offers a robust solution that leverages the openmetrics (Prometheus) exporter approach. Using a community exporter, such as the <a href="https://github.com/aashley/powerpal_exporter">Powerpal Exporter</a>, Netdata can effortlessly ingest and visualize metrics without the need for setting up a Prometheus server or a Grafana dashboard. With Netdata&rsquo;s user-friendly platform, users can benefit from automated dashboards and real-time alerts, ensuring they stay informed about their energy consumption patterns.</p>Pre-register to join the waiting list!https://www.netdata.cloud/waiting-list/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/waiting-list/Privacy Policyhttps://www.netdata.cloud/privacy/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/privacy/ProFTPD Monitoringhttps://www.netdata.cloud/monitoring-101/proftpd-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/proftpd-monitoring/<h2 id="proftpd-monitoring">ProFTPD Monitoring</h2> <h3 id="what-is-proftpd">What Is ProFTPD?</h3> <p>ProFTPD is a popular FTP server used for hosting, transferring, and sharing files over networks. Known for its security features, configurability, and flexibility, ProFTPD is a go-to solution for many organizations that require robust file transfer capabilities. It supports numerous authentication methods and access control options, making it versatile for varied environments.</p> <h3 id="monitoring-proftpd-with-netdata">Monitoring ProFTPD With Netdata</h3> <p>When it comes to monitoring ProFTPD, Netdata offers a seamless way to collect and visualize vital metrics using the <a href="https://github.com/transnano/proftpd_exporter">ProFTPD Exporter</a>. Netdata taps into openmetrics with a Prometheus-compatible exporter, meaning you can capture detailed insights into your ProFTPD server’s performance. Unlike traditional setups that require a Prometheus server or a Grafana dashboard, Netdata simplifies the process. With its integration capabilities, users gain access to real-time automated dashboards and alerts without additional complex setups.</p>Prometheus Endpoint Monitoringhttps://www.netdata.cloud/monitoring-101/generic-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/generic-monitoring/<h2 id="prometheus-endpoint-monitoring">Prometheus Endpoint Monitoring</h2> <h3 id="what-is-prometheus">What Is Prometheus?</h3> <p>Prometheus is an open-source systems monitoring and alerting toolkit, originally built at SoundCloud. Now, it’s a part of the Cloud Native Computing Foundation, providing powerful capabilities for collecting and querying metrics.</p> <h3 id="monitoring-prometheus-endpoints-with-netdata">Monitoring Prometheus Endpoints With Netdata</h3> <p>To monitor Prometheus endpoints efficiently, Netdata employs an OpenMetrics (Prometheus) exporter. This allows Netdata to ingest data from any Prometheus exporter with ease. Users can leverage Netdata to gain automated dashboards and alerts without the need for deploying a Prometheus server or setting up Grafana. This enables seamless and efficient monitoring of your systems with minimal overhead.</p>Prometheus Endpoint Monitoringhttps://www.netdata.cloud/monitoring-101/prometheus-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/prometheus-monitoring/<p>Prometheus endpoints are HTTP interfaces exposed by various applications and services that provide metrics in a format consumable by Prometheus. These endpoints follow the OpenMetrics exposition format, which ensures compatibility with Prometheus monitoring. By collecting and analyzing metrics from these endpoints, Prometheus enables users to gain deep insights into their infrastructure&rsquo;s performance and health, helping them detect and resolve issues proactively. The ability to monitor Prometheus endpoints is crucial for maintaining the performance and reliability of modern applications and systems.</p>Proxmox VE Monitoringhttps://www.netdata.cloud/monitoring-101/proxmox-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/proxmox-monitoring/<h2 id="proxmox-ve-monitoring">Proxmox VE Monitoring</h2> <h3 id="what-is-proxmox-ve">What Is Proxmox VE?</h3> <p>Proxmox VE (Virtual Environment) is a comprehensive open-source platform for enterprise virtualization, combining powerful KVM hypervisor technology with robust container-based solutions. It allows IT teams to manage virtual machines, containers, highly available clusters, and software-defined storage, all in a single convenient solution.</p> <h3 id="monitoring-proxmox-ve-with-netdata">Monitoring Proxmox VE With Netdata</h3> <p>To efficiently monitor Proxmox VE, Netdata leverages an openmetrics (prometheus) exporter. Netdata seamlessly ingests data from any Prometheus exporter. This enables IT professionals to benefit from automated dashboards, alerts, and detailed statistics, without the need for a dedicated Prometheus server or Grafana setup. With <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">Netdata</a>, you can visualize metrics in real-time, easily detect anomalies, and ensure your virtual environment operates optimally.</p>ProxySQL Monitoringhttps://www.netdata.cloud/monitoring-101/proxysql-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/proxysql-monitoring/<h2 id="proxysql-monitoring">ProxySQL Monitoring</h2> <h3 id="what-is-proxysql">What Is ProxySQL?</h3> <p><a href="https://www.proxysql.com/">ProxySQL</a> is a high-performance SQL proxy designed to manage multiple back-end MySQL servers behind a single proxy interface. It enhances MySQL database scalability and reliability, supporting advanced query routing and connection pooling, which leads to improved performance for your database workloads.</p> <h3 id="monitoring-proxysql-with-netdata">Monitoring ProxySQL With Netdata</h3> <p>Monitoring ProxySQL is vital for maintaining the health and performance of your database layer. Netdata provides a comprehensive ProxySQL monitoring tool that offers real-time insights into various metrics, enabling you to diagnose and troubleshoot any issues promptly. With <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/proxysql/?utm_source=website&amp;utm_content=monitoring101">Netdata&rsquo;s ProxySQL integration</a>, you can easily observe key performance metrics and customize your monitoring according to your needs.</p>Puppet Monitoringhttps://www.netdata.cloud/monitoring-101/puppet-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/puppet-monitoring/<h2 id="puppet-monitoring">Puppet Monitoring</h2> <h3 id="what-is-puppet">What Is Puppet?</h3> <p>Puppet is a powerful tool for managing and automating the configuration of servers and applications in IT environments. It allows for defining infrastructure as code, enabling consistent and repeatable system setups. Visit the <a href="https://www.puppet.com/">official Puppet site</a> to learn more.</p> <h3 id="monitoring-puppet-with-netdata">Monitoring Puppet With Netdata</h3> <p>Using a $name monitoring tool like Netdata provides real-time, per-second visibility into the performance and health of your Puppet infrastructure. Netdata’s lightweight and intuitive dashboards can help diagnose performance issues and ensure the smooth operation of your systems.</p>RabbitMQ ACCESS_REFUSED - Login was refused: authentication failures and credential rotationhttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-access-refused-login/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-access-refused-login/<p>Your application logs are filling with <code>ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN</code>, and the broker log shows matching <code>PLAIN login refused</code> lines. No messages flow from the affected clients, and depending on the client library&rsquo;s retry behavior, the broker may also be spending CPU on a tight connect-authenticate-reject loop.</p> <p>This error means the broker rejected the username/password pair (or the backend that validates them) during AMQP connection establishment. It happens before any vhost, exchange, or queue is touched. The connection is closed immediately, which is why a single misconfigured deployment can turn into connection churn that looks like a capacity problem.</p>RabbitMQ connection blocked / blocking: publishers frozen by a resource alarmhttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-connection-blocked-blocking/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-connection-blocked-blocking/<p>Your publishers are hanging. No errors, no exceptions, no disconnections. Publish calls simply never return, and queue depth stops growing. When you check the management UI or <code>rabbitmqctl list_connections</code>, you see connections in state <code>blocking</code> or <code>blocked</code> instead of <code>running</code>.</p> <p>This is not a network problem and not a client bug. RabbitMQ has raised a resource alarm (memory or disk) and has deliberately stopped reading from publisher connections across the entire cluster. It is a circuit breaker doing its job. The danger is that many client libraries hide this completely: from the application&rsquo;s perspective, the publish call just hangs with no error, which sends operators chasing ghosts in the wrong place.</p>RabbitMQ connection in flow state: credit-based backpressure explainedhttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-connection-state-flow/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-connection-state-flow/<p>You opened the management UI or ran <code>rabbitmqctl list_connections state</code> and saw one or more connections sitting in <code>state: flow</code>. No alarm fired. Nothing is blocked cluster-wide. Is it a problem? Usually no, and treating it like one is a common source of alert noise.</p> <p>Connection state <code>flow</code> is RabbitMQ&rsquo;s internal, per-connection, credit-based backpressure doing what it was designed to do. A specific publishing connection is outrunning something downstream: a queue process, the message store, disk I/O, or an inter-node link. The broker throttles just that connection, transiently, toggling between blocked and unblocked many times per second. It is surgical. It is not a resource alarm.</p>RabbitMQ connection storm: reconnect loops, FD pressure, and CPU spent on handshakeshttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-connection-storm/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-connection-storm/<p>A connection storm happens when many clients open connections to RabbitMQ at the same time, or when a smaller set of clients reconnect in a tight loop. The broker tolerates thousands of idle connections far better than it tolerates creating them. Connection setup is expensive: TCP handling, TLS handshake, AMQP negotiation, authentication, a new Erlang process per connection, plus one process per channel the client opens.</p> <p>The symptom pattern is distinct. <code>churn_rates.connection_created</code> spikes far above baseline. File descriptor and socket usage climb fast. The Erlang run queue rises because scheduler time goes to handshakes instead of message routing and heartbeats. In the worst case, healthy connections start timing out because the VM cannot service them, those clients reconnect, and the storm feeds itself.</p>RabbitMQ consumer timeout: delivery acknowledgement timed out and the channel is closedhttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-consumer-timeout/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-consumer-timeout/<p>You found this in the broker log or your client logs:</p> <pre tabindex="0"><code>delivery acknowledgement on channel 1 timed out </code></pre><p>In 3.13+ the fuller broker-side message names the consumer, queue, vhost, delivery tag, and the timeout value used, and the channel is closed with a <code>PRECONDITION_FAILED</code> (406) channel exception. The client library then typically reopens the channel and resubscribes, until it happens again.</p> <p>This is RabbitMQ&rsquo;s <code>consumer_timeout</code> mechanism firing. When a consumer holds a delivery without acknowledging it for longer than the configured timeout, the broker concludes the consumer is stuck, force-closes the channel, and requeues the unacknowledged messages. It is a protective feature, not a bug: an unacknowledged message is pinned in broker memory for potential redelivery, and a consumer that never acks is a slow-motion memory leak.</p>RabbitMQ consumers connected but not acknowledging: the consumer black holehttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-consumers-not-acking/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-consumers-not-acking/<p>The queue has consumers. The management UI shows <code>consumers: 3</code>. Yet <code>messages_ready</code> keeps climbing, the ack rate is flat at zero, and nothing is draining. Everything looks connected and nothing is working. This is the consumer black hole: dangerous because every surface-level health check passes.</p> <p>The trap is confusing connection health with consumer health. An open TCP connection and a registered consumer tag do not mean messages are being processed. A consumer can be connected, have channels open, and be completely stuck: deadlocked, blocked on a failed downstream dependency, or a zombie where the application process died but the OS never closed the socket. The broker will hold unacknowledged messages for it, pin them in RAM, and wait. Left alone, this escalates into the <a href="https://www.netdata.cloud/guides/rabbitmq/rabbitmq-memory-resource-limit-alarm/">memory wall</a>: unacked messages are not paged out, memory grows, the watermark is crossed, and every publisher in the cluster is blocked.</p>RabbitMQ disk free limit alarm: free disk space insufficient and publishing haltedhttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-disk-free-limit-alarm/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-disk-free-limit-alarm/<p>Your RabbitMQ cluster just stopped accepting messages. Publishers are connected but frozen. Consumers are still draining queues normally. The broker log shows a disk alarm, and the management UI shows <code>disk_free_alarm: true</code> on at least one node.</p> <p>This is the RabbitMQ disk free limit alarm. It fires when free space on the node&rsquo;s data partition drops below <code>disk_free_limit</code>, and it blocks every publisher on every node in the cluster, not just the affected node. It is a hard circuit breaker, not a gradual degradation: one threshold crossing and ingestion stops instantly.</p>RabbitMQ disk_free_limit at the default 50MB: the production footgunhttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-disk-free-limit-default-50mb/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-disk-free-limit-default-50mb/<p>RabbitMQ ships with <code>disk_free_limit</code> set to 50MB. When free disk space on the node&rsquo;s data partition drops below that limit, the broker raises a disk alarm and blocks every publisher on every node in the cluster. Consumers keep draining, but message ingestion stops until free space climbs back above the threshold.</p> <p>The 50MB default exists so development installs on tiny machines do not silently eat a laptop&rsquo;s disk. On a production server with terabytes of storage, it is not a safety margin; it is a tripwire one inch off the floor. A single log rotation, an Erlang crash dump, or a burst of persistent messages can consume 50MB in seconds, and the resulting incident looks exactly like a broker outage: publishers frozen, applications timing out, queue depth flat at zero growth while upstream systems back up.</p>RabbitMQ file descriptor exhaustion: fd_used near fd_total and refused connectionshttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-file-descriptor-exhaustion/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-file-descriptor-exhaustion/<p>Clients that were connected keep working, but every new connection attempt fails. Publishers in a reconnect loop after a deployment start timing out. The broker log shows <code>too many open files</code>, and the management API shows <code>fd_used</code> sitting at or near <code>fd_total</code>. This is RabbitMQ file descriptor exhaustion, and it is a cliff-edge failure: no graceful degradation, just a hard refusal.</p> <p>This is also one of the most preventable RabbitMQ incidents. The default OS limit (often 1024) is absurdly low for any real deployment, and <code>fd_used / fd_total</code> is a ratio you can watch climbing for hours or days before anything breaks. Mid-incident, the fix is cutting connection pressure now and raising limits properly afterward. Proactively, the monitoring section is the part that matters.</p>RabbitMQ flow control vs resource alarms: the two throttling mechanisms operators confusehttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-flow-control-vs-resource-alarms/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-flow-control-vs-resource-alarms/<p>Your RabbitMQ dashboard shows connections that are not in <code>running</code> state, your alert fired, and you need to know: is the broker in trouble, or working as designed? The answer depends entirely on whether those connections show <code>flow</code> or <code>blocked</code>. The difference is not a matter of degree. They are two independent mechanisms with different scope, different causes, and different required responses.</p> <p>Teams that alert on <code>flow</code> the same way they alert on <code>blocked</code> generate constant false positives: any sustained load produces <code>flow</code> connections, so the alert fires constantly and gets muted. Then, when a real resource alarm blocks every publisher in the cluster, the alert that should have paged someone is buried in a channel nobody reads.</p>RabbitMQ memory resource limit alarm: publishers blocked across the whole clusterhttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-memory-resource-limit-alarm/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-memory-resource-limit-alarm/<p>Your RabbitMQ cluster just stopped accepting messages. Publishers are connected but nothing flows. The broker log shows:</p> <pre tabindex="0"><code>memory resource limit alarm set on node rabbit@node1. *** Publishers will be blocked until this alarm clears *** </code></pre><p>One node crossed its memory high watermark, and RabbitMQ responded by blocking every publisher on every node in the cluster. There is no gradual degradation: the transition from &ldquo;fine&rdquo; to &ldquo;all ingestion halted&rdquo; is a single threshold crossing.</p>RabbitMQ memory usage climbing toward the watermark: mem_used vs mem_limithttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-memory-usage-climbing/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-memory-usage-climbing/<p>The memory alarm has not fired yet. Publishers are still running. But <code>mem_used</code> has been creeping up for hours and <code>mem_used / mem_limit</code> just crossed 0.7. This is the last quiet window you get: RabbitMQ&rsquo;s memory failure mode is a cliff edge. When <code>mem_used</code> reaches <code>mem_limit</code>, the alarm fires and every publisher on every node in the cluster is blocked at once.</p> <p>Two mistakes are common here. The first is treating <code>mem_limit</code> as raw RAM you should multiply by the watermark again. It is not; the watermark is already baked in. The second is dismissing a rising ratio because the alarm has not fired. By the time it fires, you have zero recovery headroom.</p>RabbitMQ messages lost on restart: durable queues, persistent messages, and transient trapshttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-messages-lost-on-restart/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-messages-lost-on-restart/<p>You restarted a RabbitMQ node, it came back healthy, and now downstream systems are reporting missing data. The queues are there. The exchanges and bindings are there. But messages that were sitting in queues before the restart are gone, or a queue itself vanished entirely.</p> <p>This is almost never a RabbitMQ bug. It is a mismatch between what the operator thinks durability means and what RabbitMQ actually guarantees. The broker did exactly what it was configured to do; the configuration just guarantees less than you assumed.</p>RabbitMQ Monitoringhttps://www.netdata.cloud/monitoring-101/rabbitmq-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/rabbitmq-monitoring/<h2 id="rabbitmq-monitoring">RabbitMQ Monitoring</h2> <h3 id="what-is-rabbitmq">What Is RabbitMQ?</h3> <p>RabbitMQ is an open-source message broker that facilitates communication between distributed systems by sending messages back and forth. It&rsquo;s widely used in enterprise and cloud environments to build robust messaging environments that excel in scalability and flexibility. Learn more about <a href="https://www.rabbitmq.com/">RabbitMQ</a>.</p> <h3 id="monitoring-rabbitmq-with-netdata">Monitoring RabbitMQ With Netdata</h3> <p>Netdata provides a comprehensive RabbitMQ monitoring tool that allows you to keep a real-time watch over your RabbitMQ instances. Using Netdata’s rich UI and advanced visualizations, users can easily understand their RabbitMQ environment, troubleshoot issues, and optimize performance. With automated alerts, you stay informed about critical events without manual effort.</p>RabbitMQ monitoring checklist: the signals every production broker needshttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-monitoring-checklist/<p>Most RabbitMQ incidents are not exotic. They are memory alarms nobody saw coming, disk alarms triggered by a 50MB default limit, unacked messages pinning RAM while the queue depth graph looked fine, and silent routing loss that only surfaced when a downstream team reported missing data. The broker exposed the signals the whole time. The gap is in what the team chose to collect and alert on.</p> <p>This checklist organizes RabbitMQ monitoring into four maturity levels: survival, operational, mature, and expert. Each level assumes the previous one is in place. Scope: RabbitMQ 3.13+ with quorum queues as the recommended queue type. Classic mirrored queues were deprecated in 3.9 and removed in 4.0, so they are not covered.</p>RabbitMQ network partition detected: split-brain in cluster_statushttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-network-partition-detected/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-network-partition-detected/<p>You ran <code>rabbitmqctl cluster_status</code> (or your monitoring scraped <code>/api/nodes</code>) and saw the &ldquo;Network Partitions&rdquo; section listing node names, or a non-empty <code>partitions</code> array on one or more nodes. The cluster has split: some nodes can no longer see each other over the Erlang distribution link, and each side now has its own view of the world.</p> <p>This is a paging condition. What happens next depends on <code>cluster_partition_handling</code>: the two sides may be accepting writes independently and diverging (the <code>ignore</code> default), the minority side may have frozen and stopped serving clients (<code>pause_minority</code>), or nodes may be about to restart themselves (<code>autoheal</code>). Each outcome has a different blast radius, and the wrong response makes it worse.</p>RabbitMQ node down: telling a dead broker apart from a partitioned onehttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-node-down/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-node-down/<p>A node has disappeared from your cluster view. The first question is not &ldquo;how do I bring it back&rdquo; but &ldquo;what actually happened to it.&rdquo; A dead broker (VM crashed, process killed, host gone) and a partitioned broker (Erlang node still running but cut off from its peers) look almost identical from one vantage point and completely different from another. The recovery steps are opposite: you restart a dead node, but restarting a partitioned node mid-partition can make split-brain worse.</p>RabbitMQ node is quorum critical: checking before a rolling restarthttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-node-quorum-critical/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-node-quorum-critical/<p>You are about to restart a RabbitMQ node: a rolling upgrade, an OS patch, an instance resize. Before you stop it, one question decides whether this is routine maintenance or a queue outage: if this node goes down right now, does any quorum queue or stream lose its online majority?</p> <p>RabbitMQ ships a purpose-built check for exactly this. <code>rabbitmq-diagnostics check_if_node_is_quorum_critical</code> returns unhealthy when stopping the target node would drop a quorum queue below the number of online members it needs to accept writes. The same logic is exposed over HTTP at <code>GET /api/health/checks/node-is-quorum-critical</code>, which makes it usable from automation, load balancer health gates, and CI-driven upgrade pipelines.</p>RabbitMQ NOT_FOUND - no queue or exchange: publishing to something that does not existhttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-not-found-no-queue-exchange/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-not-found-no-queue-exchange/<p>Your publisher or consumer logs show <code>NOT_FOUND - no exchange 'orders.events' in vhost '/'</code>, or the queue variant, <code>NOT_FOUND - no queue 'billing.jobs' in vhost '/'</code>. The RabbitMQ server log has the matching line: <code>operation basic.publish caused a channel exception not_found: no exchange 'orders.events' in vhost '/'</code>. The channel that raised it is now closed, and depending on the client library, your application may be spinning in a declare-fail-reconnect loop.</p>RabbitMQ PRECONDITION_FAILED - inequivalent arg: redeclaring a queue with different propertieshttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-precondition-failed-inequivalent-arg/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-precondition-failed-inequivalent-arg/<p>Your application logs are filling with channel exceptions and consumers or publishers keep reconnecting:</p> <pre tabindex="0"><code>PRECONDITION_FAILED - inequivalent arg &#39;x-queue-type&#39; for queue &#39;email.queue&#39; in vhost &#39;Email&#39;: received none but current is the value &#39;quorum&#39; of type &#39;longstr&#39; </code></pre><p>This is AMQP error 406, a channel-level exception. A client declared a queue (or exchange) that already exists, but one or more of the declared properties do not match how the entity was originally created. RabbitMQ refuses the declaration and closes the channel. The connection usually survives, but most client libraries treat a channel exception as fatal and tear down the whole connection, so a single mismatched declaration often looks like a reconnect storm.</p>RabbitMQ RESOURCE_LOCKED - cannot obtain exclusive access to queuehttps://www.netdata.cloud/guides/rabbitmq/rabbitmq-resource-locked-exclusive-queue/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/rabbitmq/rabbitmq-resource-locked-exclusive-queue/<p>Your application logs show a channel-level exception, the channel closes, and the consumer never comes back:</p> <pre tabindex="0"><code>reply-code=405, reply-text=RESOURCE_LOCKED - cannot obtain exclusive access to locked queue &#39;reply.xyz&#39; in vhost &#39;/&#39; </code></pre><p>This is AMQP error 405, a channel exception raised when a connection tries to declare, consume from, purge, or delete an exclusive queue that is still owned by a different connection. Exclusive queues are bound to the lifecycle of the connection that declared them: only that connection may use them, and they are deleted when that connection closes or is lost. The error is not a capacity problem, not an alarm, and not a permissions failure. It is an ownership conflict.</p>Radio Thermostat Monitoringhttps://www.netdata.cloud/monitoring-101/radio_thermostat-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/radio_thermostat-monitoring/<h2 id="radio-thermostat-monitoring">Radio Thermostat Monitoring</h2> <h3 id="what-is-radio-thermostat">What Is Radio Thermostat?</h3> <p>Radio Thermostat is a line of smart thermostats that offer precision control over home temperature settings, contributing to efficient home automation and energy management. These devices can be integrated with home networks, allowing users to manage their heating, ventilation, and air conditioning systems remotely through smart devices.</p> <h3 id="monitoring-radio-thermostat-with-netdata">Monitoring Radio Thermostat With Netdata</h3> <p>To monitor Radio Thermostat, Netdata leverages an openmetrics (prometheus) exporter, specifically the <a href="https://github.com/andrewlow/radio-thermostat-exporter">Radio Thermostat Exporter</a>. This empowers users with detailed insights into heating and cooling trends, enabling proactive adjustments and energy savings.</p>RADIUS Monitoringhttps://www.netdata.cloud/monitoring-101/radius-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/radius-monitoring/<h2 id="radius-monitoring">RADIUS Monitoring</h2> <h3 id="what-is-radius">What Is RADIUS?</h3> <p>RADIUS, or Remote Authentication Dial-In User Service, is a networking protocol that provides centralized Authentication, Authorization, and Accounting (AAA) management for users who connect and use a network service. It is a vital component for many network security and management setups, allowing for streamlined and secure user access management. RADIUS is often used by ISPs and large organizations to manage user credentials.</p> <h3 id="monitoring-radius-with-netdata">Monitoring RADIUS With Netdata</h3> <p>Monitoring RADIUS with Netdata is a seamless experience thanks to the openmetrics (Prometheus) exporter support. Netdata&rsquo;s $name monitoring tool leverages the RADIUS exporter to collect essential protocol metrics without the need for a dedicated Prometheus server or Grafana dashboards. This capability allows DevOps, SREs, developers, and IT admins to monitor RADIUS performance in real-time with automated dashboards and alerts, ensuring efficient authentication and access management.</p>Raritan PDU Monitoringhttps://www.netdata.cloud/monitoring-101/raritan_pdu-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/raritan_pdu-monitoring/<h2 id="raritan-pdu-monitoring">Raritan PDU Monitoring</h2> <h3 id="what-is-raritan-pdu">What Is Raritan PDU?</h3> <p>Raritan Power Distribution Units (PDUs) are critical devices used for power management in data centers and IT environments. They provide reliable power distribution to network devices and allow remote power control, ensuring efficient and uninterrupted operations. Monitoring Raritan PDU involves tracking metrics such as power usage, voltage, and current, which are essential for maintaining optimal performance and preventing downtime.</p> <h3 id="monitoring-raritan-pdu-with-netdata">Monitoring Raritan PDU With Netdata</h3> <p>To monitor Raritan PDU effectively, Netdata utilizes an openmetrics (Prometheus) exporter. This approach allows Netdata to ingest data seamlessly from any Prometheus exporter. This simplifies the monitoring architecture by removing the need for a standalone Prometheus server or Grafana for visualization. With Netdata, you gain immediate access to automated dashboards and alerts, enabling real-time monitoring of your Raritan PDU.</p>Reading docker system df: where Docker disk usage actually liveshttps://www.netdata.cloud/guides/docker/docker-system-df/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/docker/docker-system-df/<p>You run <code>docker system df</code> but the numbers do not add up to what <code>df -h</code> reports. Maybe the Build Cache row is empty while <code>/var/lib/docker/buildkit/</code> consumes tens of gigabytes. Maybe RECLAIMABLE is high but <code>docker system prune</code> barely frees space because overlay2 layer sharing masks the real unique cost. Or the daemon returns <code>Error response from daemon</code> when the disk is already full. This guide shows how to read <code>docker system df</code> precisely, what it hides, and how to triage the real consumers on the host.</p>Reading EXPLAIN ANALYZE: the operator's guide to PostgreSQL query planshttps://www.netdata.cloud/guides/postgres/postgres-explain-analyze-reading/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/postgres/postgres-explain-analyze-reading/<p>When <code>pg_stat_statements</code> flags a query as a top consumer, <code>EXPLAIN ANALYZE</code> is the operator&rsquo;s ground truth. It shows what the executor did, node by node, buffer by buffer. Misreading the output leads to useless indexes and production changes that make performance worse.</p> <p>This guide covers the mechanics that matter in production: how actual time accumulates through the node tree, why estimated rows diverge from reality, when buffer counts reveal cache misses versus disk reads, and how artifacts like the loops multiplier hide expensive nodes. It is a field manual for deciding, in the next five minutes, whether the problem is a missing index, stale statistics, a bad plan choice, or something deeper.</p>Real-Time Observability ROI Calculatorhttps://www.netdata.cloud/value/roi/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/value/roi/Redis aof_last_write_status:err: AOF write failures and recoveryhttps://www.netdata.cloud/guides/redis/redis-aof-last-write-status-err/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-aof-last-write-status-err/<p><code>INFO persistence</code> showing <code>aof_last_write_status:err</code> means Redis failed to flush its Append-Only File buffer to disk on the last attempt. If you depend on AOF for durability, the instance is no longer persisting writes. With the default <code>appendfsync everysec</code>, Redis logs the failed fsync and retries, but once <code>aof_last_write_status</code> is <code>err</code>, the server rejects mutations. This rejection is independent of <code>stop-writes-on-bgsave-error</code>, which only gates write rejection after a failed RDB background save (with <code>appendfsync always</code>, an unrecoverable AOF write or fsync error makes Redis exit instead). Clients see <code>MISCONF Errors writing to the AOF file: &lt;system error text&gt;</code>, a different message from the RDB-snapshot MISCONF, so the error text names the actual failure.</p>Redis big keys: finding the giant key that blocks the event loophttps://www.netdata.cloud/guides/redis/redis-big-keys-latency/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-big-keys-latency/<p>Application latency spikes while <code>redis-cli PING</code> still returns <code>PONG</code>. Simple <code>GET</code> commands take hundreds of milliseconds. Aggregate <code>used_memory</code> looks stable, <code>instantaneous_ops_per_sec</code> drops, and the slowlog grows. The culprit is often a single oversized key: a sorted set with millions of elements, a hash with millions of fields, or a list fetched with an unbounded range. Redis executes commands sequentially on one main thread; an O(N) command on a giant key blocks every other client until it completes. This guide shows how to find that key and fix it without restarting Redis.</p>Redis BUSY Redis is busy running a script: blocking Lua and how to recoverhttps://www.netdata.cloud/guides/redis/redis-busy-running-script/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-busy-running-script/<p><code>redis-cli</code> returns <code>(error) BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE.</code> Normal commands stall. Redis is not down, but it might as well be: a Lua script is holding the single event loop hostage and will not yield until it finishes or you intervene.</p> <p>Redis executes <code>EVAL</code> and <code>EVALSHA</code> atomically. While a script runs, no other command processes. Once execution exceeds <code>lua-time-limit</code> (default 5000 ms), Redis replies with <code>BUSY</code> to other clients. The script itself continues until it finishes, is killed, or the server shuts down. Whether the script has already performed writes determines whether you can kill it safely or must choose between waiting and a hard shutdown.</p>Redis Can't save in background: fork: Cannot allocate memory - diagnosis and fixhttps://www.netdata.cloud/guides/redis/redis-cant-save-in-background-fork/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-cant-save-in-background-fork/<p>Redis logs <code>Can't save in background: fork: Cannot allocate memory</code>. <code>free -h</code> shows plenty of free RAM, yet <code>BGSAVE</code> or <code>BGREWRITEAOF</code> fails. If <code>stop-writes-on-bgsave-error</code> is <code>yes</code> (default), writes fail too. The gap between free RAM and fork failure is the key.</p> <p>This is not a simple OOM. It is a kernel commit charge failure. Linux <code>fork()</code> must account for the worst case where every copy-on-write page is modified. With <code>vm.overcommit_memory=0</code> (the default), the kernel enforces a heuristic commit limit. When Redis RSS is large, that limit blocks <code>fork()</code> even with free physical memory. The fix is usually one sysctl, but THP, container limits, and actual RAM headroom determine whether it holds.</p>Redis client output buffer overflow: slow consumers and client-output-buffer-limithttps://www.netdata.cloud/guides/redis/redis-client-output-buffer-limit/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-client-output-buffer-limit/<p>Redis accepts commands faster than some clients can read the responses. When a client&rsquo;s read loop stalls, Redis keeps writing into that client&rsquo;s output buffer because there is no backpressure mechanism for normal clients. The buffer grows on the main heap, and that memory counts against <code>maxmemory</code>. Under the right conditions, a single slow consumer can push the server into eviction, OOM rejection, or a crash.</p> <p>The default <code>client-output-buffer-limit normal 0 0 0</code> means unlimited. No hard limit, no soft limit, no timeout. This is a footgun that ships with every Redis instance. Pub/Sub and replica clients get defaults, but normal clients, the vast majority of connections, get nothing.</p>Redis cluster bus port blocked: the port+10000 firewall gotchahttps://www.netdata.cloud/guides/redis/redis-cluster-gossip-port-blocked/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-cluster-gossip-port-blocked/<p><code>CLUSTER INFO</code> reports <code>cluster_state:fail</code>. Nodes show non-zero <code>cluster_slots_pfail</code>. Clients receive <code>CLUSTERDOWN</code>. Yet <code>redis-cli -p 6379 PING</code> returns <code>PONG</code> on every node, application connections are still accepted, and the client port shows no obvious network outage. The cluster behaves like it is partitioned, but only the bus is broken. Port 16379, or your configured client port plus 10000, is missing from a firewall rule, security group, or container port mapping. The cluster bus carries gossip, failure detection, and node discovery over this separate TCP port. When the bus is unreachable, nodes cannot synchronize the cluster map, so they mark peers as failed and withdraw slot coverage even though the data port stays healthy. Because firewall rules often cover the client port but omit the bus port, this failure mode is common after infrastructure changes, node replacements, or environment migrations.</p>Redis cluster_slots_pfail > 0: impending node failure in a clusterhttps://www.netdata.cloud/guides/redis/redis-cluster-slots-pfail/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-cluster-slots-pfail/<p><code>cluster_slots_pfail &gt; 0</code> means at least one hash slot is mapped to a node that a peer suspects is down. In Redis Cluster, PFAIL is unilateral: any node raises it when another stops answering gossip PINGs for longer than <code>cluster-node-timeout</code>. Slots continue to serve traffic; the cluster has not yet agreed the node is dead.</p> <p>Brief spikes are expected during background saves, AOF rewrites, or any main-thread freeze. Sustained non-zero values indicate a real problem: network partition, node crash, or overload. If the majority of masters confirm the suspicion within twice <code>cluster-node-timeout</code>, PFAIL escalates to FAIL. The affected slots become unavailable until a replica wins election. In a three-master cluster, losing two primaries leaves the survivor without quorum. The cluster enters a zombie state where no failover can proceed. Investigate PFAIL while you still have quorum and before automatic escalation.</p>Redis CLUSTERDOWN / cluster_state:fail: slot coverage and recoveryhttps://www.netdata.cloud/guides/redis/redis-cluster-state-fail/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-cluster-state-fail/<p><code>CLUSTERDOWN The cluster is down</code> means at least one of the 16384 hash slots lacks a healthy master. With <code>cluster-require-full-coverage yes</code> (the default), a single missing slot blocks all writes. This guide covers diagnosing the root cause, recovering safely, and preventing recurrence.</p> <h2 id="what-this-means">What this means</h2> <p>Redis Cluster shards the keyspace across 16384 hash slots. Each slot must be assigned to a master node that is reachable and healthy to count toward <code>cluster_slots_ok</code>. When <code>cluster_slots_assigned</code> drops below 16384, or <code>cluster_slots_fail</code> becomes non-zero because a node has been marked FAIL by quorum, the cluster transitions to <code>cluster_state:fail</code>. Clients receive <code>CLUSTERDOWN</code> for operations hashing to affected slots.</p>Redis connected_clients climbing: connection leak detectionhttps://www.netdata.cloud/guides/redis/redis-connected-clients-climbing/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-connected-clients-climbing/<p>A sustained climb in <code>connected_clients</code> over hours or days while application traffic is flat is a classic Redis connection leak. Each connection carries a server-side client object plus a 16 KB output buffer and a query buffer that grows in 16 KB chunks, so idle connections use tens of KB each and far more when replies are large. 10,000 leaked connections can therefore consume hundreds of MB independent of your dataset. If the instance is near <code>maxmemory</code>, that overhead can push Redis into eviction or OOM territory.</p>Redis connection exhaustion: leaks, pools, and the retry stormhttps://www.netdata.cloud/guides/redis/redis-connection-exhaustion/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-connection-exhaustion/<p>Application logs show connection timeouts and Redis returns <code>ERR max number of clients reached</code>. Downstream services fail because they cannot reach the cache. <code>INFO clients</code> shows <code>connected_clients</code> at the hard limit even though traffic has not increased. This is connection exhaustion. The most dangerous response is a retry storm that turns a small leak into a site-wide cascade.</p> <p>Redis enforces a hard upper bound on connections via <code>maxclients</code>. When the sum of <code>connected_clients</code>, <code>connected_slaves</code>, and <code>cluster_connections</code> reaches that limit, Redis rejects every new TCP connection. Applications that retry immediately without backoff create a feedback loop: existing connections age out slowly while new attempts pile up, keeping the server pinned at the limit even after the original leak stops growing.</p>Redis CPU saturation: hitting the single-core throughput ceilinghttps://www.netdata.cloud/guides/redis/redis-cpu-saturation-single-thread/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-cpu-saturation-single-thread/<p>Redis latency climbs. PING returns PONG, but simple GETs take milliseconds instead of microseconds. Host CPU looks moderate - perhaps 25% across eight cores - yet commands queue. The likely cause is main-thread CPU saturation. Redis executes all commands on a single event-loop thread. Once that thread saturates one core, latency rises linearly with queue depth. There is no performance cliff - only a steady ramp that eventually drives client timeouts. On multi-core hosts, aggregate process CPU hides this bottleneck because background children, I/O threads, and system accounting spread usage across cores.</p>Redis event loop blocked: when one slow command freezes everythinghttps://www.netdata.cloud/guides/redis/redis-event-loop-blocked/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-event-loop-blocked/<p>Redis processes every command on a single main thread. Even with Redis 6.0 and later offloading network I/O to threads, command execution itself remains strictly sequential. When one command takes too long, everything behind it waits. You will see clients still connected, but <code>PING</code> stalls and throughput collapses to zero. This is the Slow Command Snowball pattern: a single expensive operation blocks the event loop, the client queue backs up, and latency compounds across every connected application.</p>Redis eviction policy tuning: allkeys-lru vs volatile-ttl vs noevictionhttps://www.netdata.cloud/guides/redis/redis-eviction-policy-tuning/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-eviction-policy-tuning/<p>When Redis reaches <code>maxmemory</code>, it must either reject new writes or delete existing keys. The <code>maxmemory-policy</code> directive decides which path it takes, yet many production instances run with a policy that mismatches the workload. A cache running <code>noeviction</code> returns OOM errors to clients. A database running <code>allkeys-lru</code> silently deletes committed data. A session store running <code>volatile-ttl</code> suddenly rejects writes the moment an application bug omits a TTL.</p> <h2 id="what-it-is-and-why-it-matters">What it is and why it matters</h2> <p>Redis stores data in memory. The <code>maxmemory</code> directive sets the ceiling; when a write would push <code>used_memory</code> over it, Redis evaluates <code>maxmemory-policy</code> before executing the command. Eviction runs synchronously in the command path, consuming main-thread CPU and adding latency to the triggering write.</p>Redis exposed without authentication: the CONFIG SET dir crontab attackhttps://www.netdata.cloud/guides/redis/redis-exposed-without-auth/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-exposed-without-auth/<p>An unauthenticated Redis instance on a public interface is remote code execution. The classic attack chains four commands: <code>CONFIG SET dir</code> to a cron folder, <code>CONFIG SET dbfilename</code> to a valid cron file, <code>SET</code> a malicious payload, and <code>SAVE</code>. If Redis runs as root, the host is compromised immediately. If unprivileged, attackers pivot via SSH keys or systemd timers.</p> <p>This guide is an operational audit and lockdown. It covers how the file-write attack works, how to detect exposure, how to check for active compromise, and how to harden the instance. It also covers the follow-on risk: once authenticated access is gained, recently disclosed authenticated RCE bugs can escalate to full system control.</p>Redis FLUSHALL ran in production: detection, prevention, and recoveryhttps://www.netdata.cloud/guides/redis/redis-flushall-data-loss/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-flushall-data-loss/<p>FLUSHALL deletes every key in every logical database. Under default <code>save</code> policies (3600 1, 300 100, 60 10000), the server schedules a background save of the empty keyspace once a save point condition is met, overwriting the RDB snapshot. There is no undo. If you are responding to an active incident, your priorities are: confirm the scope, isolate unaffected replicas before they process the flush, recover from the freshest intact persistence source, and harden the instance.</p>Redis fork/COW memory storm: why persistence doubles RSS and OOM-kills the boxhttps://www.netdata.cloud/guides/redis/redis-fork-cow-storm/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-fork-cow-storm/<p>Redis disappeared from your container with only an <code>OOMKilled</code> status and a metrics gap that aligns with an RDB snapshot or AOF rewrite. The dataset was under its memory limit moments ago, but during persistence the reported RSS doubled and the kernel killed the process.</p> <p>This is the Redis fork/copy-on-write memory storm. Redis calls <code>fork()</code> to spawn a child process for background RDB snapshots, AOF rewrites, and full replication syncs. After the fork, parent and child share pages through copy-on-write. Pages stay read-only until one process writes. If the parent continues serving writes, every modified page is copied. On a write-heavy instance, this can duplicate the entire dataset, pushing RSS to roughly twice the logical data size. Containers with tight memory limits do not see <code>used_memory</code>; they see RSS. When RSS hits the cgroup ceiling, the OOM killer fires, both processes die, and the instance restarts cold.</p>Redis KEYS command blocking production: why to replace it with SCANhttps://www.netdata.cloud/guides/redis/redis-keys-command-blocking-production/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-keys-command-blocking-production/<p>Redis P99 latency jumps from sub-millisecond to seconds. Clients time out. <code>instantaneous_ops_per_sec</code> drops to near zero while <code>connected_clients</code> stays high. The likely culprit is a single slow command monopolizing the event loop, and <code>KEYS</code> is the classic offender.</p> <p>Redis runs all client commands on one main thread. <code>KEYS</code> scans the entire keyspace synchronously to match a pattern. Time complexity is O(N) where N is the total number of keys. During the scan, nothing else executes. Every client, including replication streams, health checks, and monitoring probes, waits.</p>Redis latest_fork_usec too high: THP, NUMA, and fork latencyhttps://www.netdata.cloud/guides/redis/redis-latest-fork-usec-high/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-latest-fork-usec-high/<p><code>INFO stats</code> shows <code>latest_fork_usec</code> in the hundreds of milliseconds. Every <code>fork()</code> blocks the single event loop, so during that window no commands are processed. Clients time out, replicas disconnect, and a full resync can trigger another fork, creating a loop of latency and reconnection storms. A normal fork costs roughly 10-20ms per gigabyte of resident memory with Transparent Huge Pages disabled. If you are seeing 10-100x that, the culprit is usually THP, NUMA, or memory overcommit policy.</p>Redis MASTERDOWN / master_link_status:down: replication link brokenhttps://www.netdata.cloud/guides/redis/redis-master-link-status-down/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-master-link-status-down/<p>You see <code>MASTERDOWN</code> errors from client libraries, or monitoring shows <code>master_link_status:down</code> on a replica. The replica is still accepting connections and serving reads, but every response is increasingly stale. The primary continues to take writes, so the gap widens. Determine whether this is a transient resync or a real partition, and fix it without forcing an expensive full resync that freezes the primary with a fork.</p> <h2 id="what-this-means">What this means</h2> <p>On the replica, <code>INFO replication</code> reports <code>master_link_status:down</code> whenever the TCP connection to the primary cannot be maintained. The replica retries the connection every second. While the link is down, the replica still accepts reads from its last known dataset. It does not fail queries automatically unless the client is configured to do so, so applications may serve stale data silently.</p>Redis max number of clients reached: maxclients and rejected_connectionshttps://www.netdata.cloud/guides/redis/redis-max-number-of-clients-reached/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-max-number-of-clients-reached/<p>Redis is rejecting new client connections. Applications see connection errors or timeouts. The <code>rejected_connections</code> counter in <code>INFO stats</code> is climbing. These are the hallmarks of hitting the <code>maxclients</code> limit, and the situation can worsen rapidly if client retry logic amplifies the problem.</p> <p>The <code>maxclients</code> directive (default 10,000) sets a hard ceiling on simultaneous connections. When the limit is reached, Redis sends an error to the new client and closes the connection immediately. The <code>rejected_connections</code> counter increments for every refused connection. Because this counter is cumulative, any increase during your monitoring window is an active incident.</p>Redis maxmemory not set: why every production instance needs a memory limithttps://www.netdata.cloud/guides/redis/redis-maxmemory-not-set/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-maxmemory-not-set/<p>A Redis instance with <code>maxmemory</code> set to 0 has no memory limit. On 64-bit builds, this is the default. Redis will keep allocating until the OS runs out of physical RAM, at which point the Linux OOM killer terminates the process. No warning, no graceful degradation, no eviction. The process simply vanishes.</p> <p>What follows is a predictable restart cycle. Redis starts up, loads the last RDB snapshot (which may be stale or large enough to take minutes), and rejects all data commands during the loading phase. Applications see a cold cache with a 100% miss rate. They hammer the backing database to repopulate Redis. Clients reconnect in a thundering herd. If the dataset that caused the OOM is still being written, the instance hits the wall again and the cycle repeats.</p>Redis memory pressure spiral: eviction thrashing and how to break ithttps://www.netdata.cloud/guides/redis/redis-memory-pressure-spiral/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-memory-pressure-spiral/<p>Redis latency climbs, CPU saturates, and cache hit rate falls. <code>evicted_keys</code> rises while application writes increase. The backend database gets hammered. This is not a simple capacity shortage; it is a memory pressure spiral. Redis has reached <code>maxmemory</code> and started evicting keys. The application responds to cache misses by re-fetching from the origin and writing back to Redis. Those writes trigger more evictions, which cause more misses, which cause more writes. Redis does maximum work for minimum value.</p>Redis Monitoringhttps://www.netdata.cloud/monitoring-101/redis-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/redis-monitoring/<h2 id="redis-monitoring">Redis Monitoring</h2> <h3 id="what-is-redis">What Is Redis?</h3> <p>Redis, an in-memory data structure store, is widely used as a distributed, in-memory key-value database, cache, and message broker. With speeds that are difficult to match, Redis plays a crucial role in many real-time applications. You can learn more about Redis on the <a href="https://redis.com/">official Redis website</a>.</p> <h3 id="monitoring-redis-with-netdata">Monitoring Redis With Netdata</h3> <p>Monitoring Redis effectively ensures that your applications run smoothly and that issues are diagnosed before they impact your users. The <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/redis/">$name monitoring tool</a> from Netdata provides real-time, thorough insights into Redis server performance. Netdata automatically detects Redis instances and starts collecting metrics instantly via protocols like TCP or UNIX sockets.</p>Redis monitoring checklist: the signals every production instance needshttps://www.netdata.cloud/guides/redis/redis-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-monitoring-checklist/<p>Redis can return PONG while replicating hours behind, during an OOM kill in a background save, or while a KEYS command wedges the event loop. This checklist structures monitoring into four maturity levels. Level 1 is the survival floor. Level 2 adds workload and resource awareness. Level 3 introduces leading indicators that catch degradation before it becomes an incident. Level 4 exposes allocator and encoding internals for granular diagnostics.</p> <p>Work through the levels in order. Most production incidents are preventable with Level 2 signals that teams never configure. All metrics below are available via standard Redis commands.</p>Redis OOM command not allowed when used memory > 'maxmemory' - causes and fixeshttps://www.netdata.cloud/guides/redis/redis-oom-command-not-allowed/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-oom-command-not-allowed/<p>Redis returns <code>(error) OOM command not allowed when used memory &gt; 'maxmemory'</code>. The server stays online; reads succeed, writes fail. If the client library suppresses errors, the first symptom may be missing data or backend load spikes. This occurs when <code>used_memory</code> reaches <code>maxmemory</code> and the eviction policy cannot free space. Under <code>noeviction</code>, Redis rejects every write and keeps all keys. Under <code>volatile-*</code>, the same happens when no keys carry a TTL. Monitoring often misses this because <code>evicted_keys</code> stays at zero while <code>used_memory</code> sits just below the limit.</p>Redis OOM-killed by the kernel: RSS, overcommit, and recoveryhttps://www.netdata.cloud/guides/redis/redis-out-of-memory-oom-killed/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-out-of-memory-oom-killed/<p>Redis reports <code>used_memory</code> at 60% of <code>maxmemory</code>, then disappears. The container status is <code>OOMKilled</code>, or <code>dmesg</code> shows the kernel OOM killer selected <code>redis-server</code>. The kernel enforces resident memory (RSS), while <code>used_memory</code> and <code>maxmemory</code> track logical allocator state. Fragmentation, copy-on-write pages during persistence, and client buffers inflate RSS above the logical figure most operators monitor. When RSS hits the host or cgroup memory ceiling, the kernel terminates the process even though Redis believes it is within limits.</p>Redis Queue Monitoringhttps://www.netdata.cloud/monitoring-101/redis_queue-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/redis_queue-monitoring/<h2 id="redis-queue-monitoring">Redis Queue Monitoring</h2> <h3 id="what-is-redis-queue">What Is Redis Queue?</h3> <p>Redis Queue (RQ) is a simple Python library for queueing jobs and processing them in the background with workers. It’s designed to have a low barrier to entry and to be easy to use. RQ is built on top of Redis, which is an in-memory data structure store that supports various data structures. It&rsquo;s an ideal option for those who want a straightforward solution for task queues without the complexity of more robust tools.</p>Redis rdb_last_bgsave_status:err: diagnosing failed background saveshttps://www.netdata.cloud/guides/redis/redis-rdb-last-bgsave-status-err/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-rdb-last-bgsave-status-err/<p><code>INFO persistence</code> returning <code>rdb_last_bgsave_status:err</code> means the last background save failed. The flag is sticky: it remains <code>err</code> until a subsequent <code>BGSAVE</code> succeeds, so the failure may be hours old. If <code>stop-writes-on-bgsave-error</code> is enabled (the default), Redis rejects writes and your application sees <code>MISCONF</code> errors. If the setting is disabled, writes continue but durability is broken; the exposure window grows with every update.</p> <p>The failure modes are a narrow set: fork failure, disk full, filesystem write rejection, or child death before completion. Follow this sequence to separate them without restarting Redis.</p>Redis READONLY You can't write against a read only replica - causes and fixeshttps://www.netdata.cloud/guides/redis/redis-readonly-cant-write-against-replica/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-readonly-cant-write-against-replica/<p>Your application hits <code>(error) READONLY You can't write against a read only replica</code>. Writes fail; reads work. The connected Redis instance thinks it is a replica, so it rejects mutating commands. The replica is behaving correctly. The problem is a write-capable client routed to a node that is not the current primary. This typically happens in three situations: a routing bug that sends writes to a replica endpoint, stale client topology after a failover or upgrade, or an instance that was accidentally demoted at runtime.</p>Redis replication backlog overflow: full-resync storms and the 1MB defaulthttps://www.netdata.cloud/guides/redis/redis-replication-backlog-overflow/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-replication-backlog-overflow/<p>Replicas drop and reconnect, but each reconnection triggers a full resync instead of a partial sync. The primary forks for an RDB dump, latency spikes, and other replicas fall behind. Before recovery, another replica exceeds the backlog window and the cycle repeats. The default <code>repl-backlog-size</code> of 1 MB triggers this cascade in most production workloads.</p> <p>The backlog is a fixed-size circular buffer of recent writes that lets a disconnected replica catch up without a full resync. When writes during a blip exceed the 1 MB default, the replica&rsquo;s offset falls outside the window. Recovery requires a full resync, which forks the primary and turns a brief disconnect into a site-wide latency event.</p>Redis replication lag: detection, diagnosis, and fixeshttps://www.netdata.cloud/guides/redis/redis-replication-lag/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-replication-lag/<p>Reads from Redis replicas returning stale data indicate replication lag. Your monitoring shows a growing gap between the primary&rsquo;s replication offset and what the replica has acknowledged. During failover, every byte of that gap is potential data loss.</p> <p>Replication lag in Redis is measured in bytes: the difference between <code>master_repl_offset</code> on the primary and <code>slave_repl_offset</code> on the replica. Small, stable lag is normal in asynchronous replication, but lag that grows continuously or exceeds <code>repl-backlog-size</code> signals a bottleneck that can cascade into full resync storms.</p>Redis sync_full incrementing: diagnosing full resync eventshttps://www.netdata.cloud/guides/redis/redis-full-resync-storms/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/redis/redis-full-resync-storms/<p>Your Redis primary&rsquo;s <code>sync_full</code> counter is climbing. That means replicas are performing full resyncs instead of partial ones. Each full resync forces the primary to fork, write an RDB snapshot, and push it to the replica, which then wipes its own dataset and reloads from scratch. One full resync is a heavy operation. Several in succession, or multiple at once, can freeze the primary&rsquo;s event loop, spike memory via copy-on-write, and trigger a cascade where more replicas fall behind and also need full resyncs.</p>Referralhttps://www.netdata.cloud/referral/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/referral/Response Time Monitoringhttps://www.netdata.cloud/monitoring-101/response-time-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/response-time-monitoring/<h2 id="what-is-response-time-monitoring">What is Response Time Monitoring?</h2> <p>Response time monitoring is the process of measuring the time it takes for a system or application to respond to a request made by a user. This measurement can help identify performance bottlenecks and potential issues with the system, and can be used to optimize its performance.</p> <p>Response time monitoring is a critical aspect of performance monitoring that can benefit a wide range of systems and applications including <strong>web applications</strong>, such as e-commerce sites, social media platforms, enterprise web applications, <strong>mobile applications</strong>, such as gaming apps, social media apps, productivity apps, <strong>API-based systems</strong>, especially microservice architectures, <strong>database systems</strong>, including relational and NoSQL databases.</p>RethinkDB Monitoringhttps://www.netdata.cloud/monitoring-101/rethinkdb-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/rethinkdb-monitoring/<h2 id="rethinkdb-monitoring">RethinkDB Monitoring</h2> <h3 id="what-is-rethinkdb">What Is RethinkDB?</h3> <p><a href="https://rethinkdb.com">RethinkDB</a> is an open-source, distributed database built to easily store JSON documents and effortlessly scale to multiple machines. It offers a robust query language that allows developers to seamlessly deal with highly dynamic modern applications.</p> <h3 id="monitoring-rethinkdb-with-netdata">Monitoring RethinkDB With Netdata</h3> <p>Monitoring RethinkDB using Netdata offers a real-time, comprehensive insight into your database’s performance and health. Netdata’s lightweight architecture and easy-to-use interface make it an exceptional RethinkDB monitoring tool, enabling you to gain actionable alerts and historical data with minimal setup. By leveraging Netdata, you allow your operations team to focus on innovation rather than maintenance.</p>RetroShare Monitoringhttps://www.netdata.cloud/monitoring-101/retroshare-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/retroshare-monitoring/<h2 id="what-is-retroshare">What is RetroShare?</h2> <p>RetroShare is a free, open source, cross-platform software for secure file sharing, chat, and VoIP. It enables users to securely communicate and share files with friends, family, and colleagues, with an emphasis on privacy and security. RetroShare uses end-to-end encryption for all communication, and its decentralized architecture ensures there is no central server that can be compromised.</p> <h2 id="monitoring-retroshare-with-netdata">Monitoring RetroShare with Netdata</h2> <p>Netdata does not currently ship a RetroShare collector. Browse the <a href="https://www.netdata.cloud/integrations/">current collector integrations</a> before planning a deployment, or use Netdata&rsquo;s <a href="https://learn.netdata.cloud/docs/developer-and-contributor-corner/external-plugins">external plugin interfaces</a> to collect RetroShare metrics from a supported endpoint.</p>Riak KV Monitoringhttps://www.netdata.cloud/monitoring-101/riakkv-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/riakkv-monitoring/<h2 id="riak-kv-monitoring">Riak KV Monitoring</h2> <h3 id="what-is-riak-kv">What Is Riak KV?</h3> <p>Riak KV is a distributed NoSQL database designed for high availability, scalability, and fault tolerance. It is built to handle a variety of data types and volumes, making it a popular choice for applications requiring robust data storage solutions. Learn more about Riak KV <a href="https://riak.com/products/riak-kv/index.html">here</a>.</p> <h3 id="monitoring-riak-kv-with-netdata">Monitoring Riak KV With Netdata</h3> <p>Monitoring Riak KV is crucial to ensure it performs optimally under varying load conditions. With Netdata, you gain real-time visibility into your Riak KV instances, allowing you to monitor throughput, latency, and other critical metrics. Netdata&rsquo;s real-time monitoring capabilities make it an ideal Riak KV monitoring tool, giving you detailed insights into your database performance for effective troubleshooting and optimization.</p>RIPE Atlas Monitoringhttps://www.netdata.cloud/monitoring-101/ripe_atlas-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/ripe_atlas-monitoring/<h2 id="ripe-atlas-monitoring">RIPE Atlas Monitoring</h2> <h3 id="what-is-ripe-atlas">What Is RIPE Atlas?</h3> <p>RIPE Atlas is a global network measurement platform that provides real-time insights into Internet connectivity and performance across the world. With thousands of probes distributed globally, RIPE Atlas allows network administrators and IT professionals to perform measurements to assess network health, troubleshoot connectivity issues, and ensure optimal performance.</p> <h3 id="monitoring-ripe-atlas-with-netdata">Monitoring RIPE Atlas With Netdata</h3> <p>When it comes to monitoring RIPE Atlas, Netdata simplifies the process significantly. By utilizing an openmetrics (Prometheus) exporter, such as the <a href="https://github.com/czerwonk/atlas_exporter">RIPE Atlas Exporter</a>, Netdata efficiently collects data from the RIPE Atlas platform. Netdata can ingest data from any Prometheus exporter, allowing you to get automated dashboards, alerts, and more without the need for a standalone Prometheus server or Grafana setup.</p>Rspamd Monitoringhttps://www.netdata.cloud/monitoring-101/rspamd-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/rspamd-monitoring/<h2 id="rspamd-monitoring">Rspamd Monitoring</h2> <h3 id="what-is-rspamd">What Is Rspamd?</h3> <p>Rspamd is a fast, open-source, anti-spam system designed to protect email gateways and filter spam. It offers excellent performance, flexibility, and scalability, using a variety of advanced algorithms and statistical analysis tools.</p> <h3 id="monitoring-rspamd-with-netdata">Monitoring Rspamd With Netdata</h3> <p>Netdata&rsquo;s <a href="https://rspamd.com/">Rspamd monitoring tool</a> provides unparalleled insights into the performance and activity of your Rspamd instance. By using Netdata, you can monitor Rspamd&rsquo;s critical metrics in real-time, gain actionable insights, and troubleshoot issues effectively.</p>S.M.A.R.T. attributes Monitoringhttps://www.netdata.cloud/monitoring-101/smartd-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/smartd-monitoring/<h2 id="what-makes-a-storage-device-smart">What makes a storage device S.M.A.R.T.?</h2> <p><a href="https://en.wikipedia.org/wiki/Self-Monitoring,_Analysis_and_Reporting_Technology">S.M.A.R.T.</a> (Self-Monitoring, Analysis, and Reporting Technology) is a supplementary component built into many modern storage devices through which devices monitor, store, and analyze the health of their operation. Statistics are collected (temperature, number of reallocated sectors, seek errors etc.) which software can use to measure the health of a device, predict possible device failure, and provide notifications on unsafe values.</p> <p>When S.M.A.R.T. data indicates a possible imminent drive failure, software running on the host system may notify the user so preventive action can be taken to prevent data loss, and the failing drive can be replaced and data integrity maintained.</p>S.M.A.R.T. Monitoringhttps://www.netdata.cloud/monitoring-101/smartctl-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/smartctl-monitoring/<h2 id="smart-monitoring">S.M.A.R.T. Monitoring</h2> <h3 id="what-is-smart">What Is S.M.A.R.T.?</h3> <p>S.M.A.R.T. (Self-Monitoring, Analysis, and Reporting Technology) is an integral system used within computers and storage devices to monitor the health and reliability of storage units. Specifically, S.M.A.R.T. helps in foreseeing potential hardware failures and enhances the ability to carry out proactive diagnostics, ultimately saving critical data from unexpected storage disasters. For more technical insight, you can check <a href="https://linux.die.net/man/8/smartd">man page of smartd</a>.</p> <h3 id="monitoring-smart-with-netdata">Monitoring S.M.A.R.T. with Netdata</h3> <p>Netdata provides a robust solution to monitor S.M.A.R.T. Enabled with the <code>go.d.plugin</code> and <code>smartctl</code> module, Netdata seamlessly assesses the health of your storage devices. Without directly executing potentially risky binaries, Netdata utilizes <code>ndsudo</code>, a secure, privileged command execution utility that enhances operational security and smoothens permission challenges. Dive deeper by reading the <a href="https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/s.m.a.r.t./">S.M.A.R.T. collector documentation</a>.</p>SABnzbd Monitoringhttps://www.netdata.cloud/monitoring-101/sabnzbd-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/sabnzbd-monitoring/<h2 id="sabnzbd-monitoring">SABnzbd Monitoring</h2> <h3 id="what-is-sabnzbd">What Is SABnzbd?</h3> <p>SABnzbd is a powerful and user-friendly Usenet client that automates the downloading of binary files from Usenet. It’s a preferred choice for many due to its ease of use, speed, and large number of supported devices and software. By handling NZB files seamlessly, SABnzbd helps users manage their downloads efficiently.</p> <h3 id="monitoring-sabnzbd-with-netdata">Monitoring SABnzbd With Netdata</h3> <p>To effectively monitor SABnzbd, Netdata utilizes an openmetrics (Prometheus) exporter. This approach allows seamless data collection from any Prometheus exporter, providing you with automated dashboards, alerts, and insights without the need for setting up Prometheus servers or Grafana dashboards. With Netdata, monitoring the performance and availability of your SABnzbd instance becomes effortless, ensuring optimal resource management and file downloads.</p>Salicru EQX inverter Monitoringhttps://www.netdata.cloud/monitoring-101/salicru_eqx-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/salicru_eqx-monitoring/<h2 id="salicru-eqx-inverter-monitoring">Salicru EQX inverter Monitoring</h2> <h3 id="what-is-salicru-eqx-inverter">What Is Salicru EQX Inverter?</h3> <p>The Salicru EQX inverter is pivotal in managing solar energy, a cornerstone in modern sustainable energy solutions. These inverters are crucial for converting direct current (DC) generated by solar panels into alternating current (AC) used in homes and industries. Understanding and monitoring their performance is vital for optimizing energy efficiency and maximizing the longevity of your solar infrastructure.</p> <h3 id="monitoring-salicru-eqx-inverters-with-netdata">Monitoring Salicru EQX Inverters With Netdata</h3> <p>To monitor Salicru EQX, Netdata employs an openmetrics (Prometheus) exporter. This method allows users to gather data without the necessity of deploying a separate Prometheus server or Grafana for visualization and alerting. By utilizing <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">Netdata</a>, you get automated dashboards, real-time alerts, and comprehensive visualizations directly out-of-the-box. This efficiency makes Netdata a flexible and powerful tool for monitoring your Salicru EQX inverter.</p>Samba Monitoringhttps://www.netdata.cloud/monitoring-101/samba-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/samba-monitoring/<h2 id="samba-monitoring">Samba Monitoring</h2> <h3 id="what-is-samba">What Is Samba?</h3> <p>Samba is an open-source software suite that provides seamless file and print services to SMB/CIFS clients. It facilitates interoperability between Linux/Unix servers and Windows-based clients, allowing for file sharing and printer services. For detailed information, visit the <a href="https://www.samba.org/samba/">Samba official website</a>.</p> <h3 id="monitoring-samba-with-netdata">Monitoring Samba With Netdata</h3> <p>Netdata offers a comprehensive solution for monitoring Samba by utilizing its advanced collector: the go.d.plugin for Samba. This powerful $name monitoring tool provides real-time insights into Samba operations without the need for cumbersome configurations or extensive permissions, ensuring that you can monitor Samba instances effortlessly.</p>SD-WAN tunnel up but degraded: when the control plane lieshttps://www.netdata.cloud/guides/network/network-sdwan-data-plane-degraded/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-sdwan-data-plane-degraded/<p>The orchestrator shows your SD-WAN tunnel as UP. Control connections to vSmart or vBond are healthy. OMP sessions are Established. But users at the far end report slow applications, dropped voice calls, or timeouts.</p> <p>The control plane reports a healthy tunnel while the data plane is degraded with packet loss, latency spikes, or silent traffic drops. Interface counters show UP/UP because the degradation is on the underlay path or inside the encapsulated data plane, not on the local interface.</p>Sense Energy Monitoringhttps://www.netdata.cloud/monitoring-101/sense_energy-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/sense_energy-monitoring/<h2 id="sense-energy-monitoring">Sense Energy Monitoring</h2> <h3 id="what-is-sense-energy">What Is Sense Energy?</h3> <p>Sense Energy is an advanced, smart home energy monitoring system that helps homeowners understand their electricity usage in real-time. With the integration of devices and IoT technologies, Sense Energy provides detailed insights and data that empower users to optimize energy consumption and reduce utility costs.</p> <h3 id="monitoring-sense-energy-with-netdata">Monitoring Sense Energy With Netdata</h3> <p>When it comes to efficiently monitor Sense Energy, the Netdata monitoring tool stands out as an ideal choice. Netdata utilizes an openmetrics (Prometheus) exporter to collect data. This means that with Netdata, you can ingest data from any Prometheus exporter, allowing you to gain comprehensive insights without the need for a Prometheus server or Grafana setup. Netdata offers automated dashboards, real-time alerts, and health maps that enable proactive energy management. For more technical details, you can check out the <a href="https://learn.netdata.cloud/docs/collecting-metrics/generic-collecting-metrics/prometheus-endpoint/?utm_source=website&amp;utm_content=monitoring101">Netdata documentation</a> and explore the <a href="https://github.com/ejsuncy/sense_energy_prometheus_exporter">community exporter</a> available for Sense Energy.</p>Shelly Humidity Sensor Monitoringhttps://www.netdata.cloud/monitoring-101/shelly-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/shelly-monitoring/<h2 id="shelly-humidity-sensor-monitoring">Shelly Humidity Sensor Monitoring</h2> <h3 id="what-is-shelly-humidity-sensor">What Is Shelly Humidity Sensor?</h3> <p>A Shelly Humidity Sensor is a smart home device that provides precise humidity readings essential for maintaining comfort and optimal conditions in an indoor environment. It is an integral part of modern IoT setups, offering insights into the air quality and automating climate control systems for improved home automation.</p> <h3 id="monitoring-shelly-humidity-sensor-with-netdata">Monitoring Shelly Humidity Sensor With Netdata</h3> <p>To monitor the Shelly Humidity Sensor effectively, Netdata utilizes an openmetrics (Prometheus) exporter. The <a href="https://github.com/aexel90/shelly_exporter">Shelly Exporter</a> collects metrics by periodically sending HTTP requests to the humidity sensor. Netdata can seamlessly ingest data from any Prometheus exporter, providing automated dashboards, alerting mechanisms, and more—all without the need for a Prometheus server or Grafana dashboard.</p>Siemens S7 PLC Monitoringhttps://www.netdata.cloud/monitoring-101/s7_plc-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/s7_plc-monitoring/<h2 id="siemens-s7-plc-monitoring">Siemens S7 PLC Monitoring</h2> <h3 id="what-is-siemens-s7-plc">What Is Siemens S7 PLC?</h3> <p>Siemens S7 Programmable Logic Controllers (PLCs) are used extensively in industrial environments for automation and control. These devices manage operations ranging from simple on-off control to complex continual processes, ensuring efficiency and reliability in factory automation and other industrial systems.</p> <h3 id="monitoring-siemens-s7-plc-with-netdata">Monitoring Siemens S7 PLC With Netdata</h3> <p>To monitor Siemens S7 PLC with Netdata, an openmetrics (Prometheus) exporter is used. Netdata&rsquo;s $name monitoring tool can seamlessly ingest data from any Prometheus exporter, providing you with automated dashboards, customizable alerts, and comprehensive insights—all without the need for a dedicated Prometheus server or Grafana setup. This capability makes Netdata a versatile tool for monitoring Siemens S7 PLC, ensuring you have real-time visibility and control over your industrial operations. To explore how this works, <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">check out the Live Demo</a>.</p>Silent UDP flow data loss: why your NetFlow collector is dropping recordshttps://www.netdata.cloud/guides/network/network-netflow-udp-flow-loss/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-netflow-udp-flow-loss/<p>Your flow analytics show traffic declining on multiple exporters simultaneously. SNMP interface counters say traffic is rising. No device alarms, no exporter config changes, no visible network events. The most likely cause: your collector is silently dropping UDP datagrams at the kernel socket buffer boundary.</p> <p>UDP has no delivery guarantee. When the socket receive buffer fills, the kernel discards incoming datagrams silently. No error is logged. The only signal is <code>UdpRcvbufErrors</code> in <code>/proc/net/snmp</code>, a counter most teams do not monitor. During a traffic spike or DDoS, your charts may show &ldquo;normal&rdquo; or declining traffic while actual packet rates are significantly higher.</p>Site 24x7 Monitoringhttps://www.netdata.cloud/monitoring-101/site24x7-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/site24x7-monitoring/<h2 id="site-24x7-monitoring">Site 24x7 Monitoring</h2> <h3 id="what-is-site-24x7">What Is Site 24x7?</h3> <p>Site 24x7 is a comprehensive solution that focuses on holistic monitoring of websites, servers, applications, and networks. It provides an array of insights into performance, uptime, and user interactions, thus helping technical teams to ensure robust infrastructure consistency and performance.</p> <h3 id="monitoring-site-24x7-with-netdata">Monitoring Site 24x7 With Netdata</h3> <p>To effectively monitor Site 24x7, Netdata utilizes an openmetrics (Prometheus) exporter. This allows Netdata to ingest data from any Prometheus exporter, providing automated dashboards, alerts, and more without necessitating a Prometheus server or Grafana. By using the <a href="https://github.com/svenstaro/site24x7_exporter">Site 24x7 exporter</a>, teams can effortlessly capture key monitoring metrics, ensuring seamless performance and diagnostic interventions. With Netdata, monitoring Site 24x7 transforms into a streamlined process with precise and real-time analytics that boost operational efficiency.</p>Slurm Monitoringhttps://www.netdata.cloud/monitoring-101/slurm-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/slurm-monitoring/<h2 id="slurm-monitoring">Slurm Monitoring</h2> <h3 id="what-is-slurm">What Is Slurm?</h3> <p>Slurm, also known as the Simple Linux Utility for Resource Management, is an open-source workload management system that is specifically tailored for high-performance computing (HPC) and cluster environments. It efficiently allocates resources such as CPU and memory to various jobs, ensuring optimal use of available resources across clustered nodes.</p> <h3 id="monitoring-slurm-with-netdata">Monitoring Slurm With Netdata</h3> <p>To effectively monitor Slurm, Netdata utilizes an openmetrics (Prometheus) exporter called the <a href="https://github.com/vpenso/prometheus-slurm-exporter">Prometheus Slurm Exporter</a>. With Netdata, you can ingest data from any Prometheus exporter, streamlining the process by providing automated dashboards, real-time alerts, and comprehensive insights without the need for setting up a standalone Prometheus server or configuring Grafana.</p>SMA Inverters Monitoringhttps://www.netdata.cloud/monitoring-101/sma_inverter-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/sma_inverter-monitoring/<h2 id="sma-inverters-monitoring">SMA Inverters Monitoring</h2> <h3 id="what-is-sma-inverters">What Is SMA Inverters?</h3> <p>SMA Inverters are a crucial component in solar energy systems, converting the variable direct current (DC) output of a solar panel into alternating current (AC) that can be fed into the electrical grid or used by a local, off-grid network. Ensuring their optimal performance is vital for the efficient management of solar energy resources.</p> <h3 id="monitoring-sma-inverters-with-netdata">Monitoring SMA Inverters With Netdata</h3> <p>Monitor SMA Inverters seamlessly using Netdata&rsquo;s powerful monitoring tool. Netdata leverages an OpenMetrics (Prometheus) exporter to gather solar inverter metrics. It can ingest data from any Prometheus exporter, providing users with automated dashboards, alerts, and more—all without the need for a separate Prometheus server or Grafana instance. For a versatile monitoring solution, <a href="https://github.com/dr0ps/sma_inverter_exporter">check out the community exporter</a> used to monitor SMA Inverters, which integrates seamlessly with Netdata.</p>Smart meters SML Monitoringhttps://www.netdata.cloud/monitoring-101/sml-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/sml-monitoring/<h2 id="smart-meters-sml-monitoring">Smart meters SML Monitoring</h2> <h3 id="what-is-smart-meters-sml">What Is Smart meters SML?</h3> <p>Smart meters SML (Smart Message Language) is a protocol designed for efficient smart metering and energy management. It plays a crucial role in the Internet of Things (IoT) ecosystem by transmitting detailed data regarding energy consumption and other utilities.</p> <h3 id="monitoring-smart-meters-sml-with-netdata">Monitoring Smart meters SML With Netdata</h3> <p>To effectively monitor Smart meters SML, Netdata leverages an openmetrics (prometheus) exporter. This integration allows Netdata to ingest data from any Prometheus exporter, providing fully automated dashboards, real-time alerts, and granular insights without needing a Prometheus server or Grafana. This seamless monitoring capability makes Netdata an ideal tool for the continuous surveillance of smart metering systems. For a hands-on experience, check out our <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">Live Demo</a>.</p>SNMP counter rollover: fake traffic spikes from 32-bit countershttps://www.netdata.cloud/guides/network/network-snmp-counter-rollover/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-snmp-counter-rollover/<p>A bandwidth chart suddenly shows a multi-terabit spike on a 10G interface. The on-call engineer investigates and finds the link was nearly idle. The spike is a math artifact: a 32-bit SNMP counter wrapped from near its maximum value (4,294,967,295) back to zero between two polls, and the collector&rsquo;s differencing algorithm produced a nonsensical delta.</p> <p>Depending on how the collector handles the wrap, the symptom differs: a fake spike (when the negative delta is treated as unsigned) or a fake traffic drop to zero (when treated as signed and clamped). Both hide real traffic patterns and train operators to ignore chart anomalies, including genuine ones.</p>SNMP Monitoringhttps://www.netdata.cloud/monitoring-101/snmp-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/snmp-monitoring/<h2 id="snmp-monitoring">SNMP Monitoring</h2> <h3 id="what-is-snmp">What Is SNMP?</h3> <p>SNMP (Simple Network Management Protocol) is a protocol used for managing devices on IP networks, such as routers, switches, servers, and workstations. By utilizing an SNMP monitoring tool like Netdata, network administrators are able to collect and organize information about devices in real-time to ensure efficient functioning and to identify issues before they escalate.</p> <h3 id="monitoring-snmp-with-netdata">Monitoring SNMP With Netdata</h3> <p>Netdata allows you to seamlessly monitor SNMP-enabled devices by leveraging its SNMP collector module. Whether you&rsquo;re looking to track network interface traffic, errors, or overall uptime, Netdata provides tools for monitoring SNMP with minute precision. For those interested in configuring the monitoring setup for their SNMP devices, check out the <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/snmp/">SNMP Collector Documentation</a>.</p>SNMP poller falling behind: the polling-storm cascade and how to catch ithttps://www.netdata.cloud/guides/network/network-snmp-polling-storm/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-snmp-polling-storm/<p>A single slow device is all it takes. Your SNMP poller queue drifts past its scheduled interval. Within minutes, 30 devices show as DOWN in your NMS dashboard. Every one of them responds to ping. The network is fine; your poller is the problem.</p> <p>Scheduler fall-behind is the most common false &ldquo;device down&rdquo; trigger in network monitoring. When a poller cannot complete its collection cycle within the configured interval, every subsequent cycle inherits the debt. Devices that are reachable and healthy appear DOWN because their next poll slot arrives late relative to the alerting threshold. The cascade is self-reinforcing: missed polls generate retries, retries consume worker threads, fewer workers means slower polls for all other devices, more devices time out, and queue depth grows unboundedly.</p>SNMP timeouts and retries: why devices show as down when they aren'thttps://www.netdata.cloud/guides/network/network-snmp-timeouts-retries/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-snmp-timeouts-retries/<p>SNMP runs over UDP port 161, a transport with no delivery guarantee. When your monitoring platform reports that devices are down, the first question is not &ldquo;why is the network broken&rdquo; but &ldquo;is this actually a network problem, or is my polling stack the problem.&rdquo; SNMP timeout and retry behavior is one of the most common causes of false-positive &ldquo;device down&rdquo; alerts, and it is also one of the most misdiagnosed.</p>SNMP trap receiver dropping traps: silent UDP/162 losshttps://www.netdata.cloud/guides/network/network-snmp-trap-receiver-drops/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-snmp-trap-receiver-drops/<p>When SNMP traps silently disappear, the first place to look is rarely the device. SNMP traps are push-based UDP datagrams on port 162. The kernel buffers them, and the receiver application (typically <code>snmptrapd</code> or a commercial collector) must drain that buffer faster than it fills. If it does not, the kernel silently drops datagrams and increments a counter the application never sees. No error is logged, and no alert fires.</p>SoftEther VPN Server Monitoringhttps://www.netdata.cloud/monitoring-101/softether-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/softether-monitoring/<h2 id="softether-vpn-server-monitoring">SoftEther VPN Server Monitoring</h2> <h3 id="what-is-softether-vpn-server">What Is SoftEther VPN Server?</h3> <p>SoftEther VPN Server is a robust and flexible Virtual Private Network (VPN) tool renowned for its scalability and variety of protocols support. It&rsquo;s frequently deployed in business environments looking to secure connections across multiple network endpoints, provide remote access to corporate resources, and implement secure communication channels.</p> <h3 id="monitoring-softether-vpn-server-with-netdata">Monitoring SoftEther VPN Server With Netdata</h3> <p>When it comes to monitoring SoftEther VPN Server, Netdata stands out by utilizing an openmetrics (Prometheus) exporter facilitated by the <a href="https://github.com/dalance/softether_exporter">SoftEther Exporter</a>. This exporter provides an efficient and precise way to gather critical metrics from your SoftEther VPN deployments.</p>Solar Logging Stick Monitoringhttps://www.netdata.cloud/monitoring-101/lsx-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/lsx-monitoring/<h2 id="solar-logging-stick-monitoring">Solar Logging Stick Monitoring</h2> <h3 id="what-is-solar-logging-stick">What Is Solar Logging Stick?</h3> <p>The Solar Logging Stick is a device that facilitates the monitoring of solar energy metrics, contributing to efficient solar energy management and monitoring. As the global shift towards sustainable energy grows, devices like the Solar Logging Stick become crucial in tracking how well solar panels perform, how much energy they produce, and how they contribute to reducing carbon footprints.</p> <h3 id="monitoring-solar-logging-stick-with-netdata">Monitoring Solar Logging Stick With Netdata</h3> <p>To monitor the Solar Logging Stick, Netdata uses an OpenMetrics (Prometheus) exporter. This approach allows Netdata to ingest data from any Prometheus exporter and provide automated dashboards, alerts, and more, without needing a Prometheus server or Grafana setup. With Netdata, you can quickly set up comprehensive monitoring tools for the Solar Logging Stick, giving you real-time insights into your solar energy operations and helping ensure optimal performance.</p>Solis Ginlong 5G Inverters Monitoringhttps://www.netdata.cloud/monitoring-101/solis-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/solis-monitoring/<h2 id="solis-ginlong-5g-inverters-monitoring">Solis Ginlong 5G Inverters Monitoring</h2> <h3 id="what-is-solis-ginlong-5g-inverters">What Is Solis Ginlong 5G Inverters?</h3> <p>Solis Ginlong 5G inverters are a sophisticated component of solar energy systems that help convert the direct current electricity generated by solar panels into alternating current electricity. This conversion is essential for feeding energy into the grid or using it for home or business consumption. Ensuring these inverters function optimally is crucial for the efficiency and efficacy of solar energy systems.</p>Solr Monitoringhttps://www.netdata.cloud/monitoring-101/solr-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/solr-monitoring/<h2 id="what-is-solr">What is Solr?</h2> <p><a href="https://solr.apache.org/">Apache Solr</a> is an open source search platform built on top of Apache Lucene. It is used to quickly and easily search large volumes of data. It provides powerful features such as faceting, text analysis, and geo-spatial search. Solr is highly scalable and can be used in a wide variety of applications.</p> <h2 id="monitoring-solr-with-netdata">Monitoring Solr with Netdata</h2> <p>The prerequisites for monitoring Solr with Netdata are to have Solr and <a href="https://learn.netdata.cloud/docs/cloud/get-started/">Netdata installed</a> on your system.</p>SONiC NOS Monitoringhttps://www.netdata.cloud/monitoring-101/sonic-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/sonic-monitoring/<h2 id="sonic-nos-monitoring">SONiC NOS Monitoring</h2> <h3 id="what-is-sonic-nos">What Is SONiC NOS?</h3> <p>SONiC NOS (Software for Open Networking in the Cloud) is an open-source network operating system that enables the community to innovate across network hardware and software layers. It provides scalable and high-performance networking solutions, making it an essential asset in the modern data centers and cloud environments.</p> <h3 id="monitoring-sonic-nos-with-netdata">Monitoring SONiC NOS With Netdata</h3> <p>To effectively monitor SONiC NOS, Netdata uses an openmetrics (Prometheus) exporter. This integration allows Netdata to ingest data from any Prometheus exporter, providing automated dashboards, customized alerts, and in-depth insights without necessitating a Prometheus server or Grafana.</p>Spacelift Monitoringhttps://www.netdata.cloud/monitoring-101/spacelift-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/spacelift-monitoring/<h2 id="spacelift-monitoring">Spacelift Monitoring</h2> <h3 id="what-is-spacelift">What Is Spacelift?</h3> <p>Spacelift is a powerful infrastructure-as-code (IaC) platform designed to manage and automate your infrastructure efficiently. It offers robust solutions for DevOps teams and IT professionals looking to streamline their workflows. By integrating with popular version control systems, Spacelift makes it easy to manage infrastructure modifications and deployments.</p> <h3 id="monitoring-spacelift-with-netdata">Monitoring Spacelift With Netdata</h3> <p>To monitor Spacelift effectively, Netdata utilizes an openmetrics (Prometheus) exporter, specifically the <a href="https://github.com/spacelift-io/prometheus-exporter">Spacelift Exporter</a>. This approach enables the aggregation and visualization of crucial metrics without needing a standalone Prometheus server or Grafana dashboard. Netdata supports data ingestion from any Prometheus exporter, providing automated dashboards, alerts, and insightful analytics to keep your Spacelift environment running smoothly.</p>Sphinx Monitoringhttps://www.netdata.cloud/monitoring-101/sphinx-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/sphinx-monitoring/<h2 id="sphinx-monitoring">Sphinx Monitoring</h2> <h3 id="what-is-sphinx">What Is Sphinx?</h3> <p>Sphinx is an open-source full-text search engine that provides powerful search capabilities with high-performance indexing. It&rsquo;s designed to handle extensive data search requirements efficiently, making it an excellent choice for developers and organizations looking to enhance their data retrieval processes.</p> <h3 id="monitoring-sphinx-with-netdata">Monitoring Sphinx With Netdata</h3> <p>Monitoring Sphinx effectively is crucial for ensuring optimal performance in data search and indexing. Netdata offers a robust solution for Sphinx monitoring by utilizing an openmetrics (Prometheus) exporter. This approach allows Netdata to ingest data seamlessly from any Prometheus exporter, offering automated dashboards, alerts, and more without the need for a Prometheus server or Grafana. The <a href="https://github.com/foxdalas/sphinx_exporter">Sphinx Exporter</a> enables you to gather valuable metrics about your Sphinx instance, providing insights into performance bottlenecks and resource usage.</p>SpigotMC Monitoringhttps://www.netdata.cloud/monitoring-101/spigotmc-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/spigotmc-monitoring/<h2 id="spigotmc-monitoring">SpigotMC Monitoring</h2> <h3 id="what-is-spigotmc">What Is SpigotMC?</h3> <p>SpigotMC is a high-performance Minecraft server platform that is synonymous with ease of customization and optimization, making it a popular choice among Minecraft server administrators. Whether you&rsquo;re running a private server for friends or a large public server, maintaining optimal performance with SpigotMC requires careful monitoring of various metrics.</p> <h3 id="monitoring-spigotmc-with-netdata">Monitoring SpigotMC With Netdata</h3> <p>Netdata offers a robust and user-friendly monitoring solution for SpigotMC servers. As a comprehensive tool for monitoring SpigotMC, Netdata provides real-time insights into server performance and helps detect potential issues before they escalate. By using the <a href="https://www.netdata.cloud/integrations/data-collection/applications/spigotmc/">SpigotMC monitoring tool</a>, administrators can track crucial metrics and maintain peak server performance effortlessly.</p>SQL Database agnostic Monitoringhttps://www.netdata.cloud/monitoring-101/sql-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/sql-monitoring/<h2 id="sql-database-agnostic-monitoring">SQL Database agnostic Monitoring</h2> <h3 id="what-is-sql-database-monitoring">What Is SQL Database Monitoring?</h3> <p>SQL databases are an integral part of most modern applications, serving as the backbone for data storage and management. Monitoring SQL databases involves tracking performance metrics, uptime, and other critical parameters to ensure database queries run smoothly and efficiently. It helps in preemptively identifying issues such as slow queries, connection bottlenecks, or resource exhaustion.</p> <h3 id="monitoring-sql-databases-with-netdata">Monitoring SQL Databases With Netdata</h3> <p>To effectively monitor SQL databases, <a href="https://app.netdata.cloud/?utm_source=website&amp;utm_content=monitoring101">Netdata</a> utilizes an openmetrics (Prometheus) exporter. Netdata can ingest data from any Prometheus exporter, allowing users to set up automated dashboards, alerts, and more. This is achieved without needing a dedicated Prometheus server or Grafana, making it an efficient and streamlined solution for your database monitoring needs. With <a href="https://github.com/free/sql_exporter">Netdata&rsquo;s integration</a>, you can maintain real-time insights into your database health and performance seamlessly.</p>SQL Server AG send and redo queues growing: replication lag and failover RTOhttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-ag-send-redo-queue-growing/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-ag-send-redo-queue-growing/<p>Two queues decide whether your Always On Availability Group can actually fail over: the send queue (log generated on the primary but not yet shipped to the secondary) and the redo queue (log received by the secondary but not yet replayed). When either grows without bound, replication lag is the visible symptom, but the hidden cost is failover RTO. On forced or automatic failover, the new primary must drain the entire redo queue before it accepts writes, so a queue that looks tolerable during steady state can turn a 30-second failover into a 30-minute one.</p>SQL Server Availability Group not synchronizing: NOT_HEALTHY replicas and failover riskhttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-ag-not-synchronizing/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-ag-not-synchronizing/<p>The symptom arrives as an alert or a dashboard color change: a synchronous-commit secondary replica is reporting <code>synchronization_health_desc = NOT_HEALTHY</code> or <code>connected_state_desc = DISCONNECTED</code> in <code>sys.dm_hadr_availability_replica_states</code>. The primary is still accepting writes, but the protection you assumed is degraded or gone.</p> <p>In synchronous-commit mode, the primary waits for the secondary to harden log records before acknowledging commits. When the secondary drops or stops keeping up, the primary either continues unprotected or stops accepting writes entirely, depending on <code>required_synchronized_secondaries_to_commit</code>. Either way, your recovery point objective and your recovery time objective are both at risk.</p>SQL Server backup freshness: the recovery point you only discover you lack during an incidenthttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-backup-freshness/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-backup-freshness/<p>The recovery point you actually have is the recovery point you can restore to, not the one your schedule promises. Backup freshness is the gap between those two, measured as the time since the last successful full, differential, and transaction log backup per database. When that gap is wrong, you find out during restore: either an analyst files a ticket for missing data, or an incident forces point-in-time recovery and the chain breaks.</p>SQL Server blocking chains: finding the head blocker before workers run outhttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-blocking-chain/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-blocking-chain/<p>SQL Server is unresponsive. CPU and I/O counters are low. Connections succeed but queries hang. Timeouts and login failures follow. This is the shape of a blocking chain that has crossed into worker-thread exhaustion.</p> <p>One session holds a lock. Conflicting sessions queue behind it, each waiting on an <code>LCK_M_*</code> wait and each pinning a worker from SQL Server&rsquo;s fixed-size pool. As the chain deepens, the worker pool drains. Once exhausted, new requests get <code>THREADPOOL</code> waits and the instance appears down to applications, even though the OS shows <code>sqlservr</code> healthy and storage idle.</p>SQL Server CPU utilization high: telling query load apart from a bad planhttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-cpu-utilization-high/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-cpu-utilization-high/<p>Your monitoring says the SQL Server host is at 98% CPU. Before you page anyone or start killing sessions: SQL Server is designed to use available CPU. A cold buffer pool after restart, backup compression, an ETL window, or a well-parallelized reporting query will all legitimately pin CPU at 90%+. High CPU is a symptom with no severity attached until you answer two questions: who is burning the CPU (SQL Server or something else on the host), and is the work useful (throughput) or wasted (a bad plan, a compilation storm, or spinlock contention).</p>SQL Server CXPACKET and CXCONSUMER waits: parallelism, MAXDOP, and what is actually wronghttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-cxpacket-cxconsumer-waits/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-cxpacket-cxconsumer-waits/<p>You opened <code>sys.dm_os_wait_stats</code>, excluded the idle noise, and CXPACKET is sitting at the top consuming 40, 50, maybe 70 percent of total wait time. The first search result tells you parallelism is out of control. The second tells you to set MAXDOP to 1. Both are usually wrong.</p> <p>CXPACKET is routinely the number one wait on healthy systems. Its presence alone means parallel queries are running, and parallel threads spend much of their existence waiting for each other. The wait is a side effect of work being done in parallel, not the disease. The real questions are whether that parallel work is skewed, whether the queries going parallel should be parallel at all, and whether the engine is burning worker threads and CPU on plans that would be faster serial.</p>SQL Server database in SUSPECT or RECOVERY_PENDING: an offline database and how to recover ithttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-database-suspect-recovery-pending/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-database-suspect-recovery-pending/<p>A production database is showing <code>state_desc = SUSPECT</code> or <code>RECOVERY_PENDING</code> in <code>sys.databases</code>. Applications cannot open connections to that database. Users are seeing login failures, query timeouts, or generic &ldquo;database cannot be opened&rdquo; errors. The SQL Server instance itself is up, and every other database on it may be fine.</p> <p><code>RECOVERY_PENDING</code> rarely means corruption. It usually means SQL Server could not get the resources it needed during recovery: a missing file, a full log volume, a permissions change, or a transient I/O failure at startup. <code>SUSPECT</code> is more serious because recovery actually ran and failed, but it still does not automatically mean data loss. The wrong move is to jump straight to <code>DBCC CHECKDB</code> with <code>REPAIR_ALLOW_DATA_LOSS</code>. The right move is to fix the underlying resource, re-run recovery, and only fall back to repair or restore when that fails.</p>SQL Server Error 1205: transaction was deadlocked and chosen as the deadlock victimhttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-error-1205-deadlock-victim/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-error-1205-deadlock-victim/<p>The error text returned to the client is explicit:</p> <blockquote> <p>Transaction (Process ID %d) was deadlocked on %.*ls resources with another process and has been chosen as the deadlock victim. Rerun the transaction.</p> </blockquote> <p><code>%d</code> is the SPID. <code>%.*ls</code> names the resource type, typically <code>lock</code>. The message tells the application to rerun the transaction but not why the deadlock happened, which resource was contended, or which other session was involved. To answer those questions you need the deadlock graph.</p>SQL Server Error 18456: login failed for user, and what the state code meanshttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-error-18456-login-failed/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-error-18456-login-failed/<p>SQL Server Error 18456 is the universal &ldquo;Login failed for user X&rdquo; message. It is deliberately vague: every client, from <code>sqlcmd</code> to the application&rsquo;s connection pool, sees the same string with severity 14 and state 1. The client never learns whether the password was wrong, the login does not exist, the database is offline, or the account is disabled. That information lives only in the SQL Server error log, encoded as a state code.</p>SQL Server Error 701: there is insufficient system memory to run this queryhttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-error-701-insufficient-memory/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-error-701-insufficient-memory/<p>Error 701 is one of SQL Server&rsquo;s bluntest messages: &ldquo;There is insufficient system memory in resource pool &lsquo;default&rsquo; to run this query.&rdquo; When it fires, the engine could not satisfy an allocation. Queries that were running fine seconds ago start failing, and the failure cascades into application timeouts, retry storms, and a flood of related errors (17890, 8645).</p> <p>The error itself tells you very little. It does not say whether the buffer pool is starved, whether a single query is hoarding a memory grant, whether an Extended Events ring buffer has eaten 50 GB, or whether the OS is reclaiming memory from a VM balloon driver. Investigate by source.</p>SQL Server Error 823 and 824: I/O and logical consistency errorshttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-error-823-824-io-errors/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-error-823-824-io-errors/<p>Errors 823 and 824 are SQL Server&rsquo;s severity-24 storage integrity alarms. 823 means the operating system reported a hard failure on a file API call. 824 means the call succeeded but the page failed an internal integrity check. Both are PAGE-worthy the moment they appear; they do not self-resolve, and continued use of the affected files risks losing data that was fine minutes earlier.</p> <p>Error 825 is the soft warning that usually precedes both: SQL Server retried a read that initially failed and eventually succeeded. The query did not fail and no connection was killed, which is why most teams do not alert on it. It is also the most reliable predictor that an 823 or 824 is coming.</p>SQL Server Error 825: read-retry succeeded and the disk is failinghttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-error-825-read-retry/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-error-825-read-retry/<p>Error 825 is what SQL Server writes to the error log when a disk read failed on the first attempt but succeeded on a retry (attempt 2, 3, or 4). The query completes. The application sees no failure. But the storage underneath just told you it is failing.</p> <p>Most monitoring setups never surface Error 825. It is a severity-10 informational message, and typical SQL Server Agent alert configurations target severity 20 and above. The error sits quietly in the log until something harder arrives: an 823 (hard I/O error) or an 824 (logical consistency error). By then the page may already be unreadable.</p>SQL Server Error 9002: the transaction log for the database is fullhttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-error-9002-transaction-log-full/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-error-9002-transaction-log-full/<p>Your application is throwing write failures and the SQL Server error log shows: &ldquo;The transaction log for database &lsquo;X&rsquo; is full due to &lsquo;LOG_BACKUP&rsquo;&rdquo; (or ACTIVE_TRANSACTION, AVAILABILITY_REPLICA, REPLICATION, or another reason in quotes). Every INSERT, UPDATE, and DELETE against that database now fails with error 9002. Read-only queries may still work, which makes the outage look confusingly partial from the outside.</p> <p>This is the most common unexpected SQL Server outage, and it is preventable. It is also frequently mishandled: the instinctive responses, &ldquo;add more disk space&rdquo; and &ldquo;shrink the log,&rdquo; treat the symptom while the log keeps growing. The log is full because it cannot be truncated, and the reason it cannot be truncated is stated explicitly in <code>sys.databases.log_reuse_wait_desc</code>. Read that first, fix that, then deal with the space.</p>SQL Server instance down: no response on port 1433 and where to look firsthttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-instance-down/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-instance-down/<p>Your availability probe just fired: TCP connect plus <code>SELECT 1</code> against port 1433 has failed three or more times over at least 60 seconds. Before you restart anything, separate the two failure modes that get lumped together as &ldquo;SQL Server is down&rdquo;. They have different causes, different fixes, and different blast radii.</p> <p>Mode one: no TCP connect at all. The listener is not accepting connections on 1433 (or the named instance&rsquo;s dynamic port). The service is stopped, the host is down, the network path is broken, or the listener is misconfigured, commonly after an AlwaysOn failover. The engine is not there to talk to.</p>SQL Server PAGEIOLATCH waits: the buffer pool waiting on slow storagehttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-pageiolatch-waits/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-pageiolatch-waits/<p>Your top wait type is <code>PAGEIOLATCH_SH</code> or <code>PAGEIOLATCH_EX</code>. Queries that used to be sub-50ms now take seconds. CPU may be low. There are no blocking chains. The buffer pool is waiting on disk.</p> <p>PAGEIOLATCH waits are the direct fingerprint of physical I/O. A worker needs an 8KB data page that is not in the buffer pool, takes an in-memory latch on the buffer descriptor, and waits for storage to return the page. When the read completes, the worker continues. Sustained PAGEIOLATCH time means the engine is spending wall-clock time waiting on disk.</p>SQL Server RESOURCE_SEMAPHORE waits: queries stuck waiting for a memory granthttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-resource-semaphore-waits/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-resource-semaphore-waits/<p>RESOURCE_SEMAPHORE is the wait type SQL Server records when a worker thread cannot get a query memory grant. Before a query runs a sort, hash, or certain joins, the optimizer estimates how much workspace memory it needs and asks the grant pool for it. When the pool is exhausted, parsed-and-optimized queries sit in a queue. To the application they look hung.</p> <p>CPU may be low. Disk I/O may be low. Buffer pool may look fine. Users report &ldquo;the database is slow&rdquo; and standard dashboards do not explain why. RESOURCE_SEMAPHORE only shows up clearly if you sample wait stats on a short interval and watch the Memory Grants Pending counter. Both are routinely missed.</p>SQL Server SOS_SCHEDULER_YIELD waits: CPU scheduler pressure explainedhttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-sos-scheduler-yield-waits/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-sos-scheduler-yield-waits/<p>When SOS_SCHEDULER_YIELD dominates <code>sys.dm_os_wait_stats</code>, the reflex is to assume CPU pressure and start hunting for bad queries. That reflex is right about half the time. The other half, you are chasing a signal that is doing exactly what it was designed to do: recording every time a worker voluntarily yielded its 4ms quantum because other runnable workers were queued.</p> <p>The wait type has existed in SQL Server since the SQLOS era and the 4ms quantum is fixed in every version. It cannot be tuned. What you can tune is your interpretation. A workload doing efficient set-based scans of pages already in memory will yield constantly and rack up enormous SOS_SCHEDULER_YIELD numbers without anything being wrong. A VM on an oversubscribed host reports the same wait type while the hypervisor silently steals CPU cycles SQL Server cannot see.</p>SQL Server TempDB full: the shared scratch database that halts every queryhttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-tempdb-full/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-tempdb-full/<p>Applications start failing with error 1105 (&ldquo;could not allocate space for object in database &rsquo;tempdb&rsquo; because the &lsquo;PRIMARY&rsquo; filegroup is full&rdquo;) or error 3958, and the failures are not limited to one database. Every query on the instance that needs a temp table, a sort or hash spill, a worktable, or a row version touches TempDB. When TempDB cannot allocate space, all of them fail at once.</p> <p>This is an instance-wide outage with a single shared point of failure, and it usually has one dominant consumer. The diagnostic job is short: identify which of the three consumer categories filled TempDB, find the sessions responsible, relieve the space pressure, then fix the root cause so it does not recur tomorrow.</p>SQL Server THREADPOOL waits: worker thread exhaustion and refused connectionshttps://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-threadpool-waits/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/microsoft-sql-server/microsoft-sql-server-threadpool-waits/<p>Your monitoring says the SQL Server host is fine: CPU at 15%, disk latency normal, memory steady. But the application is timing out, new connections hang, and the instance might as well be down. When you finally get in, the wait stats tell the story: THREADPOOL.</p> <p>THREADPOOL means every worker thread in the SQLOS pool is busy, and new requests are queuing for a thread that does not exist. From the client&rsquo;s perspective this is equivalent to connection refusal. The server is not slow. It is not accepting work at all.</p>Squid Monitoringhttps://www.netdata.cloud/monitoring-101/squid-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/squid-monitoring/<h2 id="squid-monitoring">Squid Monitoring</h2> <h3 id="what-is-squid">What Is Squid?</h3> <p>Squid is a caching proxy for the web, supporting HTTP, HTTPS, FTP, and more. It reduces bandwidth and improves response times by caching and reusing frequently-requested web pages. Squid is a critical component in managing data collection and efficiency for web servers and web proxies.</p> <h3 id="monitoring-squid-with-netdata">Monitoring Squid With Netdata</h3> <p>Monitor your Squid infrastructure effectively with <a href="https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/squid/">Netdata&rsquo;s Squid monitoring tool</a>. Netdata provides real-time monitoring with interactive visualizations, enabling you to keep tabs on all Squid instances whether they&rsquo;re locally or remotely hosted. This allows you to instantly detect performance bottlenecks and operational issues.</p>Squid Monitoringhttps://www.netdata.cloud/monitoring-101/squidlog-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/squidlog-monitoring/<h2 id="squid-monitoring">Squid Monitoring</h2> <h3 id="what-is-squid">What Is Squid?</h3> <p>Squid is a caching and forwarding web proxy that optimizes web delivery and reduces bandwidth. By storing copies of frequently requested web content, Squid enhances response times and reduces server loads. With a rich feature set supporting HTTP, HTTPS, FTP, and more, Squid plays a crucial role in optimizing web proxies.</p> <h3 id="monitoring-squid-with-netdata">Monitoring Squid With Netdata</h3> <p>To effectively monitor Squid log files, Netdata offers an insightful solution through its go.d.plugin. The Squid monitoring tool from Netdata focuses on parsing access log files to give you real-time visibility into your Squid server operations. This ensures that you can track server responses, bandwidth usage, and client interaction in real-time.</p>Stale FDB/MAC tables: why endpoint location is wronghttps://www.netdata.cloud/guides/network/network-fdb-mac-staleness/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-fdb-mac-staleness/<p>Your topology platform says endpoint <code>aa:bb:cc:dd:ee:ff</code> is on switch port <code>Gi1/0/24</code>. Your security team sends someone to that port. The endpoint is not there. It moved hours ago, or it went offline, or it vMotioned to a different host. The FDB entry was stale and the platform presented it as current.</p> <p>The Forwarding Database (FDB), also called the MAC address table or CAM table, maps MAC addresses to switch ports. Topology inference engines use FDB data, cross-referenced with ARP tables and CDP/LLDP neighbor data, to deduce where endpoints are physically connected. The inference is probabilistic. It degrades as input data freshness degrades.</p>Starlink (SpaceX) Monitoringhttps://www.netdata.cloud/monitoring-101/starlink-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/starlink-monitoring/<h2 id="starlink-monitoring">Starlink Monitoring</h2> <h3 id="what-is-starlink-spacex">What Is Starlink (SpaceX)?</h3> <p>Starlink, developed by SpaceX, is an ambitious project aimed at providing high-speed satellite internet across the globe. By deploying a constellation of small satellites in low Earth orbit, Starlink aims to deliver reliable internet connectivity even in the most remote areas. With its advanced technology, monitoring is crucial to maintain and optimize internet service management and performance.</p> <h3 id="monitoring-starlink-with-netdata">Monitoring Starlink With Netdata</h3> <p>To effectively monitor Starlink, Netdata utilizes an openmetrics (Prometheus) exporter. The <a href="https://github.com/danopstech/starlink_exporter">Starlink Exporter</a> integrates seamlessly with Netdata, allowing for the collection and visualization of Starlink satellite internet metrics. Netdata excels in aggregating data from any Prometheus exporter, offering automated dashboards and alerts without the need for a dedicated Prometheus server or Grafana. This streamlined process ensures real-time and comprehensive monitoring of your Starlink connection.</p>StatusPage Monitoringhttps://www.netdata.cloud/monitoring-101/statuspage-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/statuspage-monitoring/<h2 id="statuspage-monitoring">StatusPage Monitoring</h2> <h3 id="what-is-statuspage">What Is StatusPage?</h3> <p>StatusPage is an effective tool for incident management and communication. It allows you to inform your users about the status of your services, incidents in real time, and updates about resolutions. With StatusPage, you have a centralized method to keep your operations transparent. Understanding how to monitor it effectively can significantly improve your incident response times and service communication.</p> <h3 id="monitoring-statuspage-with-netdata">Monitoring StatusPage With Netdata</h3> <p>Monitoring StatusPage with Netdata is both simple and powerful. Utilize the StatusPage Exporter, available <a href="https://github.com/vladvasiliu/statuspage-exporter">here</a>, to transform StatusPage data into openmetrics compatible format. Netdata can ingest metrics from any Prometheus exporter, allowing you to monitor StatusPage without needing to set up a Prometheus server or Grafana. This means you get out-of-the-box dashboards, alerts, and visualization for immediate insights, all available on the same network without additional configurations.</p>Steam Monitoringhttps://www.netdata.cloud/monitoring-101/steam_a2s-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/steam_a2s-monitoring/<h2 id="steam-monitoring">Steam Monitoring</h2> <h3 id="what-is-steam">What Is Steam?</h3> <p>Steam is a leading platform for digital distribution of video games and related media, a community space for gamers, and a tool for multiplayer gaming. With millions of concurrent users, monitoring Steam servers is crucial for maintaining seamless gaming experiences.</p> <h3 id="monitoring-steam-with-netdata">Monitoring Steam With Netdata</h3> <p>To efficiently monitor Steam, Netdata employs an openmetrics (Prometheus) exporter, specifically tailored to the Steam A2S-supported game servers. This allows you to gather insightful metrics on performance and availability. Netdata&rsquo;s versatility shines through as it can ingest data from any Prometheus exporter, providing automated dashboards, alerts, and more—eliminating the need for a standalone Prometheus server or Grafana. Discover the ease and efficiency with which you can monitor Steam with <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">Netdata&rsquo;s Live Demo</a>.</p>StoreCLI RAID Monitoringhttps://www.netdata.cloud/monitoring-101/storcli-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/storcli-monitoring/<h2 id="storecli-raid-monitoring">StoreCLI RAID Monitoring</h2> <h3 id="what-is-storecli-raid">What Is StoreCLI RAID?</h3> <p>StoreCLI RAID is a powerful tool that manages and monitors your RAID (Redundant Array of Independent Disks) setup. It allows you to oversee the performance and health of your storage system by tracking RAID adapters, physical drives, and backup batteries using the StorCLI command line interface. For more details, refer to the official <a href="https://docs.broadcom.com/doc/12352476">StoreCLI RAID documentation</a>.</p> <h3 id="monitoring-storecli-raid-with-netdata">Monitoring StoreCLI RAID With Netdata</h3> <p>Netdata enhances the way you monitor StoreCLI RAID by enabling real-time insights to help you understand your storage system&rsquo;s health and performance. Using Netdata, you can leverage a seamless experience to track your RAID arrays without executing binaries directly, improving both security and ease of use. Interested in trying it out? <a href="https://app.netdata.cloud/?utm_source=website&amp;utm_content=monitoring101">Sign up for a Free Trial</a>.</p>Storidge Monitoringhttps://www.netdata.cloud/monitoring-101/storidge-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/storidge-monitoring/<h2 id="storidge-monitoring">Storidge Monitoring</h2> <h3 id="what-is-storidge">What Is Storidge?</h3> <p>Storidge is an innovative solution designed to simplify storage management and deliver high-performance, scalable storage services within enterprise environments. By offering exceptional operational efficiency, Storidge aims to streamline the storage process and enhance data handling capabilities.</p> <h3 id="monitoring-storidge-with-netdata">Monitoring Storidge With Netdata</h3> <p>To monitor Storidge effectively, Netdata leverages an openmetrics (Prometheus) exporter. Netdata is a robust Storidge monitoring tool that can seamlessly ingest data from any Prometheus exporter, allowing users to visualize metrics through automated dashboards and receive real-time alerts. What sets Netdata apart is that you can achieve all of this without the need for a separate Prometheus server or Grafana setup, simplifying the monitoring journey for DevOps, SREs, developers, and IT admins.</p>STP topology-change storms: reconvergence cascades explainedhttps://www.netdata.cloud/guides/network/network-stp-topology-change-storm/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-stp-topology-change-storm/<p>A topology-change notification (TCN) is not itself a failure. STP generates one every time a non-edge port transitions up or down. That is normal during maintenance, link recovery, or device boot. The problem is what happens next. When TCNs fire repeatedly, or when a single TCN hits a large Layer 2 domain with thousands of MAC addresses, the protocol&rsquo;s designed response becomes a self-inflicted traffic event.</p> <p>The cascade is mechanical. Every switch that receives the topology-change flag shortens its MAC address aging timer from the default (typically 300 seconds) to the Forward Delay value (15 seconds by default). This forces unknown-unicast flooding until endpoints re-announce their MACs through normal traffic. In a VLAN with thousands of entries, that flooding saturates links, spikes latency, and consumes switch CPU. The blast radius is the entire broadcast domain, not the switch where the port flapped.</p>strongSwan Monitoringhttps://www.netdata.cloud/monitoring-101/strongswan-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/strongswan-monitoring/<h2 id="strongswan-monitoring">strongSwan Monitoring</h2> <h3 id="what-is-strongswan">What Is strongSwan?</h3> <p>strongSwan is an open-source implementation of IPSec, a key protocol used to secure virtual private networks (VPNs). It’s distinctive for its focus on encryption standards, scalability, and cross-platform capability. strongSwan enables developers and IT admins to create secure network connections and enforce security policies efficiently.</p> <h3 id="monitoring-strongswan-with-netdata">Monitoring strongSwan With Netdata</h3> <p>To effectively monitor strongSwan, Netdata utilizes an openmetrics exporter, specifically structured to integrate seamlessly with any Prometheus exporter, including the <a href="https://github.com/jlti-dev/ipsec_exporter">strongSwan/IPSec/vici Exporter</a>. This powerful capability ensures users can collect VPN performance metrics and manage system health without requiring a centralized Prometheus server or Grafana setup. By incorporating Netdata, IT engineers can automatically generate dashboards and receive proactive alerts, significantly simplifying the tasks of monitoring and troubleshooting.</p>Sunspec Solar Energy Monitoringhttps://www.netdata.cloud/monitoring-101/sunspec-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/sunspec-monitoring/<h2 id="sunspec-solar-energy-monitoring">Sunspec Solar Energy Monitoring</h2> <h3 id="what-is-sunspec-solar-energy">What Is Sunspec Solar Energy?</h3> <p>Sunspec Solar Energy refers to the standardized protocols and metrics developed by the SunSpec Alliance to ensure interoperability in monitoring and managing solar energy systems. These standards are critical for efficient solar energy management, enabling seamless communication between devices, improving data accuracy, and enhancing system reliability.</p> <h3 id="monitoring-sunspec-solar-energy-with-netdata">Monitoring Sunspec Solar Energy With Netdata</h3> <p>To monitor Sunspec Solar Energy effectively, Netdata leverages an openmetrics (Prometheus) exporter. This means that Netdata can gather and visualize metrics from the <a href="https://github.com/inosion/prometheus-sunspec-exporter">Sunspec Solar Energy Exporter</a> without needing a separate Prometheus server or Grafana dashboard setup. Netdata&rsquo;s powerful monitoring capabilities allow users to create automated dashboards and set up alerts, providing real-time insights into their solar energy systems.</p>Supervisor Monitoringhttps://www.netdata.cloud/monitoring-101/supervisord-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/supervisord-monitoring/<h2 id="supervisor-monitoring">Supervisor Monitoring</h2> <h3 id="what-is-supervisor">What Is Supervisor?</h3> <p>Supervisor is a client/server system that allows its users to monitor and control a number of processes on UNIX-like operating systems. Its primary function is to ensure that processes start, restart, and run as they should, providing the user with feedback about the status and error messages of the monitored programs.</p> <h3 id="monitoring-supervisor-with-netdata">Monitoring Supervisor With Netdata</h3> <p>Netdata offers a comprehensive Supervisor monitoring tool that provides deep insights into your system&rsquo;s processes. Using this tool allows you to gain real-time visibility into all processes managed by Supervisor, ensuring seamless operation and quick troubleshooting of any irregularities. For full documentation, visit our <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/supervisord/">Supervisor collector documentation</a>.</p>Suricata Monitoringhttps://www.netdata.cloud/monitoring-101/suricata-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/suricata-monitoring/<h2 id="suricata-monitoring">Suricata Monitoring</h2> <h3 id="what-is-suricata">What Is Suricata?</h3> <p>Suricata is an open-source network threat detection engine that features intrusion detection (IDS), intrusion prevention (IPS), and network security monitoring capabilities. It analyzes network traffic and identifies suspicious activities by utilizing data collection methods, such as deep packet inspection and pattern matching.</p> <h3 id="monitoring-suricata-with-netdata">Monitoring Suricata With Netdata</h3> <p>Monitoring Suricata with Netdata offers an unparalleled view into your network&rsquo;s security apparatus. Netdata utilizes an openmetrics (Prometheus) exporter, the <a href="https://github.com/corelight/suricata_exporter">Suricata Exporter</a>, to gather metrics efficiently. Unlike traditional setups requiring a Prometheus server or Grafana for display, Netdata handles it all seamlessly. It ingests data from any Prometheus exporter, automatically presenting intuitive dashboards, real-time alerts, and in-depth analyses without the complexity typically involved.</p>Synology ActiveBackup Monitoringhttps://www.netdata.cloud/monitoring-101/synology_activebackup-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/synology_activebackup-monitoring/<h2 id="synology-activebackup-monitoring">Synology ActiveBackup Monitoring</h2> <h3 id="what-is-synology-activebackup">What Is Synology ActiveBackup?</h3> <p>Synology ActiveBackup is a comprehensive data backup solution designed for efficient data protection and management. This tool allows IT professionals to back up critical data across multiple environments, ensuring file security and rapid recovery capabilities, crucial for any business continuity plan.</p> <h3 id="monitoring-synology-activebackup-with-netdata">Monitoring Synology ActiveBackup With Netdata</h3> <p>When it comes to monitor Synology ActiveBackup, Netdata provides an effortless and robust solution. Netdata uses an openmetrics (Prometheus) exporter to collect detailed metrics from Synology ActiveBackup. Unlike traditional methods requiring standalone Prometheus server installations and extensive configurations with Grafana, Netdata simplifies this by ingesting data directly from any Prometheus exporter, providing automated dashboards and alerting mechanisms. This streamlined process ensures you can focus more on analyzing the metrics rather than setting up complex monitoring infrastructure.</p>Sysload Monitoringhttps://www.netdata.cloud/monitoring-101/sysload-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/sysload-monitoring/<h2 id="sysload-monitoring">Sysload Monitoring</h2> <h3 id="what-is-sysload">What Is Sysload?</h3> <p>Sysload is a monitoring solution designed to collect and analyze system load metrics. It provides detailed insights into the performance and resource management of your systems, essential for efficient system operations.</p> <h3 id="monitoring-sysload-with-netdata">Monitoring Sysload With Netdata</h3> <p>Netdata offers a powerful and seamless way to monitor Sysload using the openmetrics (Prometheus) exporter. This integration allows you to monitor Sysload effectively without needing a dedicated Prometheus server or Grafana setup. By ingesting data from any Prometheus exporter, Netdata automatically creates dashboards and alerts, allowing you to stay on top of your system&rsquo;s performance metrics effortlessly. To get started, you only need to configure the Sysload Exporter and Netdata will handle the rest.</p>Systemd Units Monitoringhttps://www.netdata.cloud/monitoring-101/systemdunits-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/systemdunits-monitoring/<h2 id="systemd-units-monitoring">Systemd Units Monitoring</h2> <h3 id="what-is-systemd-units">What Is Systemd Units?</h3> <p>Systemd Units represent the entities managed by systemd, a powerful init system and service manager for Linux operating systems. It is at the core of various Linux distributions and offers a suite of functionalities for managing system services. Understanding and monitoring Systemd Units is crucial for ensuring the health and performance of your operating systems as they define how a service is started, stopped, and managed.</p>systemd-logind users Monitoringhttps://www.netdata.cloud/monitoring-101/logind-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/logind-monitoring/<h2 id="systemd-logind-users-monitoring">systemd-logind users Monitoring</h2> <h3 id="what-is-systemd-logind-users">What Is systemd-logind users?</h3> <p>Systemd-logind is a system service in Linux operating systems that manages user logins. This service is part of the larger systemd suite, which is essential for resource management, session tracking, and user processes control. Monitoring systemd-logind users involves tracking active sessions and users, ensuring seamless operation across different systems.</p> <h3 id="monitoring-systemd-logind-users-with-netdata">Monitoring systemd-logind users With Netdata</h3> <p>Monitoring systemd-logind users is made efficient and straightforward with Netdata. Netdata’s real-time monitoring capabilities provide comprehensive insights into session activities and user states, making it an ideal systemd-logind users monitoring tool. By utilizing Netdata, you can gain instant visualization of key metrics and receive alerts on any unusual activities.</p>TACACS Monitoringhttps://www.netdata.cloud/monitoring-101/tacas-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/tacas-monitoring/<h2 id="tacacs-monitoring">TACACS Monitoring</h2> <h3 id="what-is-tacacs">What Is TACACS?</h3> <p>The Terminal Access Controller Access-Control System (TACACS) is a protocol developed for network authentication and authorization management. It&rsquo;s widely used to manage authentication tasks and provide detailed accounting information. TACACS plays a crucial role in securing network environments by efficiently tracking access, thus maintaining the integrity of IT infrastructures.</p> <h3 id="monitoring-tacacs-with-netdata">Monitoring TACACS With Netdata</h3> <p>To monitor TACACS, Netdata leverages a robust openmetrics (Prometheus) exporter. This setup allows Netdata to seamlessly ingest data from any Prometheus exporter. Users can enjoy automated dashboards and alerts, all without the necessity of maintaining a separate Prometheus server or Grafana instance. This integration simplifies the monitoring process while providing real-time insights into your TACACS system.</p>Tado Smart Heating Solution Monitoringhttps://www.netdata.cloud/monitoring-101/tado-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/tado-monitoring/<h2 id="tado-smart-heating-solution-monitoring">Tado Smart Heating Solution Monitoring</h2> <h3 id="what-is-tado-smart-heating-solution">What Is Tado Smart Heating Solution?</h3> <p>Tado is a cutting-edge smart heating solution designed to optimize the efficiency and comfort of home heating and cooling management. By connecting thermostats to an intelligent, internet-based platform, Tado provides users with precise control over their home temperatures, adapting dynamically to the needs of the household.</p> <h3 id="monitoring-tado-smart-heating-solution-with-netdata">Monitoring Tado Smart Heating Solution With Netdata</h3> <p>Monitoring Tado smart heating solution is a critical aspect of ensuring your home stays comfortable and energy-efficient. For seamless monitoring, Netdata uses an openmetrics (Prometheus) exporter. The <a href="https://github.com/eko/tado-exporter">Tado Exporter</a> is employed to collect various metrics necessary for maintaining an efficient Tado environment.</p>Talk to a member of our Sales team!https://www.netdata.cloud/contact-sales/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/contact-sales/Tankerkoenig API Monitoringhttps://www.netdata.cloud/monitoring-101/tankerkoenig-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/tankerkoenig-monitoring/<h2 id="tankerkoenig-api-monitoring">Tankerkoenig API Monitoring</h2> <h3 id="what-is-tankerkoenig-api">What Is Tankerkoenig API?</h3> <p>Tankerkoenig API is a powerful tool that provides fuel price data, allowing developers and organizations to collect real-time and historical data on fuel prices across various regions. It&rsquo;s crucial for businesses that rely on fuel data for logistics, analysis, or reporting to stay informed and make data-driven decisions.</p> <h3 id="monitoring-tankerkoenig-api-with-netdata">Monitoring Tankerkoenig API With Netdata</h3> <p>Netdata offers an elegant solution for real-time monitoring of the Tankerkoenig API. By leveraging an openmetrics (Prometheus) exporter, Netdata is capable of seamlessly ingesting data from any Prometheus exporter to provide automated dashboards, alerts, and comprehensive insights, all without the need for a separate Prometheus server or Grafana. With the <a href="https://github.com/lukasmalkmus/tankerkoenig_exporter">Tankerkoenig API exporter</a>, integrating and monitoring your Tankerkoenig API becomes more efficient and hassle-free.</p>TCP endpoints Monitoringhttps://www.netdata.cloud/monitoring-101/tcpendpoints-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/tcpendpoints-monitoring/<h2 id="what-is-tcp-endpoint">What is TCP endpoint?</h2> <p>A TCP endpoint is a combination of an IP address and a port number that identifies a specific process or service running on a computer or other network device. It is used to establish and manage an end-to-end connection between two applications, typically over the Internet. The TCP protocol provides a reliable, ordered delivery of data between the two endpoints.</p> <h2 id="monitoring-tcp-endpoint-with-netdata">Monitoring TCP endpoint with Netdata</h2> <p>The prerequisites for monitoring TCP endpoint is to have <a href="https://learn.netdata.cloud/docs/cloud/get-started/">Netdata installed</a> on your system.</p>TCP/UDP Endpoints Monitoringhttps://www.netdata.cloud/monitoring-101/portcheck-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/portcheck-monitoring/<h2 id="tcpudp-endpoints-monitoring">TCP/UDP Endpoints Monitoring</h2> <h3 id="what-is-tcpudp-endpoints">What Is TCP/UDP Endpoints?</h3> <p>Understanding TCP/UDP Endpoints involves recognizing the critical roles these protocols play in network communications. TCP stands for Transmission Control Protocol, managing data delivery through acknowledgment and retransmission processes. Conversely, UDP, the User Datagram Protocol, is connectionless, meaning it caters to applications where speed trumps reliability.</p> <h3 id="monitoring-tcpudp-endpoints-with-netdata">Monitoring TCP/UDP Endpoints With Netdata</h3> <p>When it comes to efficient and real-time monitoring, Netdata offers a profound solution. The <a href="https://app.netdata.cloud/?utm_source=website&amp;utm_content=monitoring101">Netdata platform</a> monitors TCP/UDP endpoints efficiently, helping you track the availability and responsiveness of your network services. Netdata’s <code>portcheck</code> monitoring tool checks the availability of specific ports, which is crucial for assessing service health.</p>Temperature, fan, and PSU monitoring: predicting hardware failurehttps://www.netdata.cloud/guides/network/network-device-environment-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-device-environment-monitoring/<p>Environmental sensors on network devices are the earliest leading indicators of hardware failure. Temperature trends, fan state changes, and PSU status transitions often precede field-replaceable unit failures by hours or days. The data is not hard to collect, but the MIB landscape is fragmented across vendors, thresholds vary by platform, and inherited polling templates frequently target deprecated OIDs. A template that worked on a Catalyst 3560 can silently return nothing on a Catalyst 8500.</p>Tengine Monitoringhttps://www.netdata.cloud/monitoring-101/tengine-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/tengine-monitoring/<h2 id="tengine-monitoring">Tengine Monitoring</h2> <h3 id="what-is-tengine">What Is Tengine?</h3> <p>Tengine is a high-performance web server and reverse proxy, based on Nginx, engineered for greater scalability and enhanced security. It is widely used in large-scale websites to manage traffic, reduce load, and ensure improved web performance. Learn more about Tengine on <a href="https://tengine.taobao.org/">their official site</a>.</p> <h3 id="monitoring-tengine-with-netdata">Monitoring Tengine With Netdata</h3> <p>Monitoring Tengine is crucial for DevOps and IT administrators seeking to optimize web performance. Netdata offers a robust Tengine monitoring tool that provides real-time insights into your server’s performance, enabling prompt issue diagnosis and efficient resource management. By utilizing Netdata&rsquo;s comprehensive monitoring capabilities, you can seamlessly monitor Tengine instances, from basic network metrics to advanced performance statistics.</p>Terms of Servicehttps://www.netdata.cloud/service-terms/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/service-terms/Terms of Usehttps://www.netdata.cloud/terms/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/terms/Tesla Vehicle Monitoringhttps://www.netdata.cloud/monitoring-101/tesla_vehicle-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/tesla_vehicle-monitoring/<h2 id="tesla-vehicle-monitoring">Tesla Vehicle Monitoring</h2> <h3 id="what-is-tesla-vehicle-monitoring">What Is Tesla Vehicle Monitoring?</h3> <p>Tesla vehicle monitoring involves tracking various metrics essential for managing and optimizing the performance of electric vehicles. These metrics can include battery health, energy consumption, charging status, and more, providing valuable insights for efficient vehicle management.</p> <h3 id="monitoring-tesla-vehicles-with-netdata">Monitoring Tesla Vehicles With Netdata</h3> <p>To monitor Tesla vehicles, Netdata employs an openmetrics (Prometheus) exporter. This enables the collection of key metrics without the need for a dedicated Prometheus server or Grafana. With Netdata, you can ingest data from any Prometheus exporter, receiving automated dashboards, alerts, and anomaly detection tailored to Tesla vehicle metrics. By using the <a href="https://github.com/wywywywy/tesla-prometheus-exporter">Tesla Prometheus Exporter</a>, you can seamlessly integrate and visualize important data, optimizing the use and management of your Tesla vehicles.</p>Tesla Wall Connector Monitoringhttps://www.netdata.cloud/monitoring-101/tesla_wall_connector-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/tesla_wall_connector-monitoring/<h2 id="tesla-wall-connector-monitoring">Tesla Wall Connector Monitoring</h2> <h3 id="what-is-tesla-wall-connector">What Is Tesla Wall Connector?</h3> <p>Tesla Wall Connector is an advanced charging station specifically designed for Tesla electric vehicles, allowing users to efficiently manage their vehicle&rsquo;s charging. As electric vehicle adoption grows, ensuring that charging infrastructure is reliable and efficient becomes crucial. Monitoring the Tesla Wall Connector becomes an essential part of maintaining an optimal charging setup.</p> <h3 id="monitoring-tesla-wall-connector-with-netdata">Monitoring Tesla Wall Connector With Netdata</h3> <p>To effectively monitor the Tesla Wall Connector, Netdata utilizes an OpenMetrics (Prometheus) exporter. The <a href="https://github.com/benclapp/tesla_wall_connector_exporter">Tesla Wall Connector Exporter</a> collects a wide range of metrics that can be processed by Netdata&rsquo;s state-of-the-art monitoring solutions. With Netdata, you can ingest data from any Prometheus exporter, granting you access to automated dashboards, real-time alerts, and insightful analytics without needing a Prometheus server or Grafana configuration. View Netdata&rsquo;s capabilities in this <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">live demo</a>.</p>Tomcat Monitoringhttps://www.netdata.cloud/monitoring-101/tomcat-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/tomcat-monitoring/<h2 id="tomcat-monitoring">Tomcat Monitoring</h2> <h3 id="what-is-tomcat">What Is Tomcat?</h3> <p>Tomcat, a robust servlet container by Apache, is a critical component enabling Java-based web applications to run seamlessly. As a cornerstone in the Java EE ecosystem, it facilitates the execution of servlets and Java Server Pages (JSP) and supports the deployment of dynamic applications. For more details, visit the <a href="https://tomcat.apache.org/">Apache Tomcat official website</a>.</p> <h3 id="monitoring-tomcat-with-netdata">Monitoring Tomcat With Netdata</h3> <p>Monitoring Tomcat effectively requires a comprehensive toolset, and Netdata stands out by offering real-time, extensive insights into Tomcat&rsquo;s performance metrics. By leveraging <a href="https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/tomcat/">Netdata&rsquo;s Tomcat monitoring tool</a>, you can gain visibility into various operational metrics like bandwidth, threads, and processing time. Netdata enables seamless integration with your existing systems, providing a holistic view of your infrastructure.</p>Tor Monitoringhttps://www.netdata.cloud/monitoring-101/tor-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/tor-monitoring/<h2 id="tor-monitoring">Tor Monitoring</h2> <h3 id="what-is-tor">What Is Tor?</h3> <p>Tor, short for The Onion Router, is a free and open-source software that allows anonymous communication over the internet. Created by the Tor Project, it directs internet traffic through a free, worldwide, volunteer overlay network consisting of more than seven thousand relays. This conceals a user&rsquo;s location and usage from network surveillance or traffic analysis.</p> <h3 id="monitoring-tor-with-netdata">Monitoring Tor With Netdata</h3> <p>To monitor Tor effectively, it&rsquo;s crucial to use a tool designed for real-time performance monitoring, and that&rsquo;s where the <a href="https://app.netdata.cloud/?utm_source=website&amp;utm_content=monitoring101">Netdata monitoring tool</a> comes in. Netdata offers seamless and robust monitoring capabilities, designed to gather and analyze the most relevant metrics for maintaining optimal performance.</p>Traefik Monitoringhttps://www.netdata.cloud/monitoring-101/traefik-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/traefik-monitoring/<h2 id="traefik-monitoring">Traefik Monitoring</h2> <h3 id="what-is-traefik">What Is Traefik?</h3> <p>Traefik is a popular open-source edge router and load balancer that helps manage your API traffic seamlessly. It provides an easy way to access your services by automatically configuring routes and managing the flow of requests between clients and your microservices. With its capabilities to handle dynamic adaptive routing, it is a suitable choice for containerized environments and microservices architectures.</p> <h3 id="monitoring-traefik-with-netdata">Monitoring Traefik With Netdata</h3> <p>Monitoring Traefik with Netdata is a straightforward process that allows you to leverage real-time data visualization and comprehensive monitoring. Netdata’s <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/traefik/">Traefik monitoring tool</a> is designed specifically to monitor the performance and health of your Traefik instances. By utilizing Netdata, you can gain insight into traffic patterns, server load, and potential bottlenecks with minimal configuration.</p>Trap and syslog flood from link flaps: surviving the stormhttps://www.netdata.cloud/guides/network/network-trap-syslog-flood/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-trap-syslog-flood/<p>A single bad SFP starts flapping. Within seconds, your trap receiver is processing hundreds of linkDown/linkUp pairs per second, your syslog pipeline is drowning in LINK-3-UPDOWN messages, and STP topology change notifications are cascading across the L2 domain. The kernel socket buffer on UDP 162 overflows, and the root-cause hardware alarm is as likely to be dropped as any other datagram in the flood.</p> <p>The core problem is architectural. Traps and syslog arrive over UDP, a lossy transport with no retransmission. When a receiver socket buffer fills, the kernel silently discards datagrams. There is no per-source accounting. You cannot tell which device&rsquo;s traps were dropped, only that some were. During a flood, any datagram arriving during the overflow window can vanish, including the one that matters most.</p>Twitch Monitoringhttps://www.netdata.cloud/monitoring-101/twitch-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/twitch-monitoring/<h2 id="twitch-monitoring">Twitch Monitoring</h2> <h3 id="what-is-twitch">What Is Twitch?</h3> <p>Twitch is a leading live streaming platform primarily for gamers, but it is also home to other types of creative content and interactive entertainment. With massive live audiences and real-time interaction possibilities, ensuring optimal performance and smooth streaming experiences for both broadcasters and viewers is crucial.</p> <h3 id="monitoring-twitch-with-netdata">Monitoring Twitch With Netdata</h3> <p>To monitor Twitch effectively, Netdata employs an openmetrics (Prometheus) exporter. The <a href="https://github.com/damoun/twitch_exporter">Twitch exporter</a> collects essential metrics, providing a comprehensive overview of the performance and health of your Twitch streams. Netdata excels in leveraging this data by offering automated dashboards, alerts, and insights, all without the need for a dedicated Prometheus server or Grafana setup. This means you can monitor Twitch streams efficiently, gaining crucial insights with minimal setup, directly from the Netdata platform.</p>Typesense Monitoringhttps://www.netdata.cloud/monitoring-101/typesense-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/typesense-monitoring/<h2 id="typesense-monitoring">Typesense Monitoring</h2> <h3 id="what-is-typesense">What Is Typesense?</h3> <p>Typesense is an open-source, in-memory search engine that delivers fast, instant search results right out of the box. It is designed to help you build typo-tolerant and real-time search experiences without the complexity that comes with integrating with heavyweight traditional search engines. With robust features like multi-tenant service, extensive language support, and real-time search updates, Typesense is a preferred choice for many developers.</p> <h3 id="monitoring-typesense-with-netdata">Monitoring Typesense With Netdata</h3> <p>Netdata offers an innovative and user-friendly experience for monitoring Typesense. As a comprehensive monitoring tool, Netdata allows you to gain insights into the health and performance of your Typesense servers, with real-time data collection and visualization. With <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">Netdata&rsquo;s live demo</a>, you can see Netdata&rsquo;s capabilities in action.</p>Ubiquiti UFiber OLT Monitoringhttps://www.netdata.cloud/monitoring-101/ubiquity_ufiber-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/ubiquity_ufiber-monitoring/<h2 id="ubiquiti-ufiber-olt-monitoring">Ubiquiti UFiber OLT Monitoring</h2> <h3 id="what-is-ubiquiti-ufiber-olt">What Is Ubiquiti UFiber OLT?</h3> <p>Ubiquiti UFiber OLT is a robust solution for fiber-optic communication networks, designed to connect with multiple endpoints. It&rsquo;s essential for managing and maintaining high-performance fiber-to-the-premises installations efficiently.</p> <h3 id="monitoring-ubiquiti-ufiber-olt-with-netdata">Monitoring Ubiquiti UFiber OLT With Netdata</h3> <p>Monitoring Ubiquiti UFiber OLT with Netdata provides invaluable insights into network performance and reliability. Netdata uses an openmetrics (Prometheus) exporter to monitor Ubiquiti UFiber OLT. It can ingest data seamlessly from any Prometheus exporter, allowing for automated dashboards, alerts, and more, without the need for a Prometheus server or Grafana. This integration empowers users to have real-time monitoring capabilities with comprehensive metrics analysis.</p>Udp_RcvbufErrors: tuning kernel receive buffers for flow, trap, and syslog collectorshttps://www.netdata.cloud/guides/network/network-udp-rcvbuf-errors/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-udp-rcvbuf-errors/<p><code>Udp_RcvbufErrors</code> is incrementing on your flow collector. Flow charts show traffic declining during what is actually a traffic spike. The kernel is receiving datagrams from exporters but the socket receive buffer is full, so it drops them silently. No application-level counter moves. No error log fires. The dashboards lie downward while the real traffic goes upward.</p> <p>Flow collectors (NetFlow v5/v9, IPFIX, sFlow), SNMP trap receivers (UDP 162), and syslog receivers (UDP 514) all depend on UDP socket buffers. When the buffer overflows, the kernel increments <code>Udp_RcvbufErrors</code> in <code>/proc/net/snmp</code> and discards the datagram. The application never sees it.</p>Unbound Monitoringhttps://www.netdata.cloud/monitoring-101/unbound-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/unbound-monitoring/<h2 id="unbound-monitoring">Unbound Monitoring</h2> <h3 id="what-is-unbound">What Is Unbound?</h3> <p>Unbound is a validating, recursive, and caching DNS resolver designed to provide robust DNS security features. As a part of network infrastructure, it plays a crucial role in efficiently resolving domain names to IP addresses while keeping caches of previous queries to expedite future lookups. Learn more about <a href="https://nlnetlabs.nl/projects/unbound/about/">Unbound</a>.</p> <h3 id="monitoring-unbound-with-netdata">Monitoring Unbound With Netdata</h3> <p>To effectively monitor Unbound, Netdata provides a comprehensive solution with its powerful <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/unbound/">Unbound monitoring tool</a>. Netdata&rsquo;s real-time metrics and beautiful visualizations help DevOps, SREs, developers, IT admins, and engineers maintain optimal DNS performance. Explore the <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">Live Demo</a> to see Netdata&rsquo;s capabilities in action.</p>UPS (NUT) Monitoringhttps://www.netdata.cloud/monitoring-101/upsd-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/upsd-monitoring/<h2 id="ups-nut-monitoring">UPS (NUT) Monitoring</h2> <h3 id="what-is-ups-nut">What Is UPS (NUT)?</h3> <p>UPS (NUT) Monitoring involves overseeing the Uninterruptible Power Supplies that keep your systems operational during power outages. Utilizing the Network UPS Tools (NUT) framework, it enables monitoring and management of power devices from widely-used brands, ensuring that your infrastructure remains protected even when the power grid fails.</p> <h3 id="monitoring-ups-nut-with-netdata">Monitoring UPS (NUT) With Netdata</h3> <p>Netdata&rsquo;s comprehensive and intuitive monitoring tool offers real-time insights into your power systems by seamlessly integrating with the UPS daemon via the NUT protocol. With Netdata, you can monitor critical parameters like load, battery status, temperature, and input/output voltages in real-time, empowering you to maintain optimal power conditions and prevent unexpected downtimes.</p>Uptimerobot Monitoringhttps://www.netdata.cloud/monitoring-101/uptimerobot-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/uptimerobot-monitoring/<h2 id="uptimerobot-monitoring">Uptimerobot Monitoring</h2> <h3 id="what-is-uptimerobot">What Is Uptimerobot?</h3> <p>Uptimerobot is a popular service that provides website uptime monitoring to ensure that your applications and services are available and performing optimally. It&rsquo;s an essential tool for DevOps, Site Reliability Engineers (SREs), and IT administrators seeking to maintain high availability and reduce downtime.</p> <h3 id="monitoring-uptimerobot-with-netdata">Monitoring Uptimerobot With Netdata</h3> <p>Monitoring Uptimerobot with Netdata allows you to maintain a reliable overview of your website&rsquo;s uptime metrics. To monitor Uptimerobot, Netdata employs an OpenMetrics (Prometheus) exporter which can seamlessly ingest data from any Prometheus exporter. This provides users with automated dashboards and alerts, enabling real-time monitoring and troubleshooting without the need for a dedicated Prometheus server or Grafana.</p>uWSGI Monitoringhttps://www.netdata.cloud/monitoring-101/uwsgi-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/uwsgi-monitoring/<h2 id="uwsgi-monitoring">uWSGI Monitoring</h2> <h3 id="what-is-uwsgi">What Is uWSGI?</h3> <p>uWSGI is an application server used to manage and serve web applications, primarily written in the Python programming language. It is widely used in production environments to facilitate reliable communication between web servers and application code by acting as a middle layer.</p> <h3 id="monitoring-uwsgi-with-netdata">Monitoring uWSGI With Netdata</h3> <p>Monitoring uWSGI is crucial for maintaining optimal application performance. Netdata offers a comprehensive uWSGI monitoring tool that provides real-time insights into server and application health. By utilizing Netdata, you can monitor key metrics such as requests, transmitted data, and exceptions to ensure your web applications run smoothly.</p>Varnish Monitoringhttps://www.netdata.cloud/monitoring-101/varnish-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/varnish-monitoring/<h2 id="varnish-monitoring">Varnish Monitoring</h2> <h3 id="what-is-varnish">What Is Varnish?</h3> <p>Varnish is a robust open-source HTTP accelerator, often used as a web cache. It efficiently stores copies of web pages and serves them to users quickly, reducing the time to render a requested web page. Whether supporting large-scale web operations or aiding e-commerce sites, Varnish effectively manages load and improves site performance.</p> <h3 id="monitoring-varnish-with-netdata">Monitoring Varnish With Netdata</h3> <p>Netdata offers an easy-to-use Varnish monitoring tool that keeps you informed on metrics essential to your infrastructure&rsquo;s performance and efficiency. By presenting data on client sessions, cache hits and misses, thread activities, and more, Netdata provides a comprehensive view of your Varnish instances&rsquo; health in real time. Explore more through our <a href="https://app.netdata.cloud/spaces/netdata-demo/?utm_source=website&amp;utm_content=monitoring101">Live Demo</a> or <a href="https://app.netdata.cloud/?utm_source=website&amp;utm_content=monitoring101">sign up for a free trial</a>.</p>Vault PKI Monitoringhttps://www.netdata.cloud/monitoring-101/vault_pki-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/vault_pki-monitoring/<h2 id="vault-pki-monitoring">Vault PKI Monitoring</h2> <h3 id="what-is-vault-pki">What Is Vault PKI?</h3> <p>Vault PKI refers to the Public Key Infrastructure provided by HashiCorp Vault, a powerful system designed to manage sensitive information like secrets, encryption keys, and certificates. It&rsquo;s an essential component in ensuring secure communication, especially when dealing with distributed systems. Vault PKI helps automate certificate management, making it a crucial element for security.</p> <h3 id="monitoring-vault-pki-with-netdata">Monitoring Vault PKI With Netdata</h3> <p>To effectively monitor Vault PKI, Netdata leverages an openmetrics exporter called the <a href="https://github.com/aarnaud/vault-pki-exporter">Vault PKI Exporter</a>. This exporter collects critical metrics on your Vault PKI setup, and Netdata can seamlessly ingest this data without relying on a separate Prometheus server or Grafana dashboards. With Netdata, you get automated dashboards, real-time alerts, and comprehensive visibility into your Vault PKI metrics and beyond, enabling proactive monitoring and troubleshooting.</p>vCenter '503 Service Unavailable': the vSphere Client will not loadhttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-vcenter-503-service-unavailable/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-vcenter-503-service-unavailable/<p>A 503 from the vSphere Client means the reverse HTTP proxy (<code>rhttpproxy</code>) accepted the TLS connection but could not reach the backend it routes to. The proxy itself is healthy. One of its dependents, typically <code>vpxd</code>, <code>vmware-vapi-endpoint</code>, <code>vmware-stsd</code> (STS), or the HTML5 client backend (<code>vsphere-ui</code>), is stopped, still starting, or crash-looping. The error string often reads &ldquo;Initialization of one of the components failed.&rdquo;</p> <p>Running VMs are unaffected. The hypervisor plane keeps scheduling and serving I/O. What you lose is the management plane: DRS stops rebalancing, HA cannot be reconfigured, vMotion orchestration is gone, and provisioning is blocked. The urgency is operational visibility and control, not workload survival.</p>vCenter 'Cannot complete login due to an incorrect user name or password': SSO failureshttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-vcenter-cannot-login/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-vcenter-cannot-login/<p>The &ldquo;Cannot complete login due to an incorrect user name or password&rdquo; string is the exact message operators see in the vSphere Client, in PowerCLI sessions, and in API responses when SSO authentication fails. The text is misleading: the cause is rarely a typo. For a single user it is usually a credential or permission problem. For every account at once it is an SSO/STS infrastructure failure.</p> <p>The first triage question is scope: does the local SSO administrator account (<code>administrator@vsphere.local</code>) still work? If yes, the STS signing certificate and token service are healthy, and the problem is in an identity source (AD/LDAP) or a service account. If <code>administrator@vsphere.local</code> also fails, the STS infrastructure itself is broken: expired STS signing certificate, clock skew rejecting SAML tokens, or STS memory pressure.</p>vCenter /storage/db full: vPostgres stops and the whole management plane dieshttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-vcenter-storage-db-full/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-vcenter-storage-db-full/<p>The vSphere Client returns 503 Service Unavailable. PowerCLI sessions hang and time out. DRS has stopped evaluating, vMotion orchestration is gone, and provisioning fails. Running VMs on the ESXi hosts continue to operate, but the management plane is gone.</p> <p>The root cause is almost certainly the <code>/storage/db</code> partition on the vCenter Server Appliance (VCSA). This is where vPostgres keeps its data files. At 95% utilization on any partition, VMware automatically shuts down <code>vmware-vpxd</code> to protect the database from corruption. At 100%, vPostgres cannot extend a data file or write a WAL record and crashes. Once vPostgres is down, <code>vpxd</code> has no database and cannot restart.</p>vCenter /storage/log full: the log-bomb disk death spiralhttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-vcenter-storage-log-full/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-vcenter-storage-log-full/<p>You log in to the vSphere Client and get a 503, or the UI hangs mid-task. You SSH into the VCSA and run <code>df -h</code>: <code>/storage/log</code> is at 100%. The root filesystem may still have plenty of free space, which is why a generic disk-space alert missed it. The VCSA has many dedicated partitions, and they fill independently.</p> <p>A single failing service can write gigabytes of logs per hour. STS authentication failures, database connection errors, alarm flapping, or a misbehaving SDK client flooding vpxd with errors will take <code>/storage/log</code> from 40% to 100% within hours. Once the partition is full, services that try to log crash. vmon restarts them. The restart itself generates more log lines as the service hits the same fault and tries to log it again. The loop is self-reinforcing, and clearing space temporarily makes the next iteration worse because the service can write again, refilling the partition faster.</p>vCenter /storage/seat full: stats, events, alarms, and tasks outgrowing their partitionhttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-vcenter-storage-seat-full/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-vcenter-storage-seat-full/<p>The <code>/storage/seat</code> partition on the vCenter Server Appliance (VCSA) holds the vPostgres tables for Stats, Events, Alarms, and Tasks: <code>vpx_event</code>, <code>vpx_event_arg</code>, <code>vpx_task</code>, and the <code>vpxd_hist_stat*</code> rollup tables. In modern VCSA it is a dedicated mount, so it can fill while <code>/storage/db</code>, <code>/storage/log</code>, and <code>/</code> all show healthy utilization. Operators checking only <code>/</code> or the VAMI dashboard&rsquo;s &ldquo;VCDB&rdquo; usage will miss it until vpxd refuses to start.</p> <p>When <code>/storage/seat</code> crosses 95% utilization, vpxd refuses to come up to avoid database corruption. Without vCenter: DRS stops scheduling, vMotion is gone, HA cannot be reconfigured, no provisioning, no management operations. VMs on ESXi hosts keep running because the data plane is independent of vCenter, but everything that touches vCenter is broken.</p>vCenter certificate expired: the STS signing cert outage nobody saw cominghttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-vcenter-certificate-expired/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-vcenter-certificate-expired/<p>vCenter is down. Not &ldquo;slow&rdquo; or &ldquo;degraded.&rdquo; Down. The vSphere Client shows a white screen or a 503. PowerCLI sessions fail to connect. API calls return authentication errors. ESXi hosts show as disconnected in bulk. Every integration that depends on vCenter (NSX, vRA, SRM, backup products) has lost connectivity simultaneously. VMs on the hosts are still running, but you cannot manage, migrate, or orchestrate anything.</p> <p>You check the browser certificate on the vCenter URL. It looks fine. Months left. You check NTP. Synchronized. You check disk space. Plenty. Nothing in your standard monitoring explains why the entire management plane went dark at once.</p>vCenter Server Appliance Monitoringhttps://www.netdata.cloud/monitoring-101/vcsa-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/vcsa-monitoring/<h2 id="vcenter-server-appliance-monitoring">vCenter Server Appliance Monitoring</h2> <h3 id="what-is-vcenter-server-appliance">What Is vCenter Server Appliance?</h3> <p>vCenter Server Appliance (vCSA) is a powerful, preconfigured Linux-based virtual machine optimized for running VMware vCenter Server and associated services. It is a vital component in managing virtualized environments, providing centralized management of virtualized hosts and virtual machines from a single console.</p> <h3 id="monitoring-vcenter-server-appliance-with-netdata">Monitoring vCenter Server Appliance With Netdata</h3> <p>Netdata offers a seamless and efficient way to monitor vCenter Server Appliance. As a comprehensive monitoring tool, it provides real-time insights and detailed metrics that are crucial for maintaining the health and performance of your vCSA environment. With Netdata’s <a href="https://www.netdata.cloud/">free and open-source platform</a>, you get simple configurations, interactive visualizations, and a low-overhead monitoring solution.</p>vCenter vpxd crash loop: the core service that keeps restartinghttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-vpxd-crash-loop/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-vpxd-crash-loop/<p>vpxd is the C++ core of vCenter Server. It holds the entire managed inventory in memory, dispatches every management task to ESXi hosts via hostd, runs DRS, executes statistics rollups, and serves every SDK client (vSphere Client, PowerCLI, Veeam, NSX Manager, Aria Operations, custom automation). When vpxd dies, vCenter is functionally down: no provisioning, no vMotion orchestration, no DRS, no HA reconfiguration. VMs already running on hosts keep running, and FDM still restarts them after a host failure, because HA does not depend on vpxd.</p>Vendor API silent data gap: HTTP 200 with an empty payloadhttps://www.netdata.cloud/guides/network/network-vendor-api-silent-gap/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/network/network-vendor-api-silent-gap/<p>Your SD-WAN controller dashboard shows flat lines. The Meraki organization API has not updated in twenty minutes. The PAN-OS firewall telemetry stopped at 03:00. Your collector logs show zero errors, every request returned HTTP 200, and no 5xx or timeout appears anywhere. But the data is gone.</p> <p>The API endpoint is reachable, the TCP connection succeeds, the HTTP status code says OK, and the response body is empty, null, or contains an error wrapped inside a success envelope. Your collector accepted the response as valid because it checked the status code and nothing else. Many API adapters treat a 200 with an empty payload as &ldquo;no data to report&rdquo; rather than &ldquo;the API is broken.&rdquo; Charts go flat, but no error fires. If the API is your only telemetry source for an SD-WAN overlay or a cloud-managed firewall estate, you are blind without knowing it.</p>VerneMQ Monitoringhttps://www.netdata.cloud/monitoring-101/vernemq-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/vernemq-monitoring/<h2 id="vernemq-monitoring">VerneMQ Monitoring</h2> <h3 id="what-is-vernemq">What Is VerneMQ?</h3> <p><a href="https://vernemq.com">VerneMQ</a> is a high-performance, distributed MQTT broker implemented in Erlang/OTP. It&rsquo;s designed to handle large numbers of concurrent clients and is particularly well-suited for applications requiring low latency. Utilizing the full power of Erlang, VerneMQ offers a robust and scalable solution for message brokering.</p> <h3 id="monitoring-vernemq-with-netdata">Monitoring VerneMQ With Netdata</h3> <p>Netdata provides a comprehensive VerneMQ monitoring tool, which is part of its suite of monitoring solutions. By integrating VerneMQ monitoring, you can track important performance metrics in real-time, allowing you to proactively manage system health and diagnose potential issues before they become critical.</p>Vertica Monitoringhttps://www.netdata.cloud/monitoring-101/vertica-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/vertica-monitoring/<h2 id="vertica-monitoring">Vertica Monitoring</h2> <h3 id="what-is-vertica">What Is Vertica?</h3> <p>Vertica is an advanced analytics database platform designed to handle large volumes of data, providing fast query performance and real-time analytics. It&rsquo;s typically used in data-intensive environments where speed and efficiency are crucial.</p> <h3 id="monitoring-vertica-with-netdata">Monitoring Vertica With Netdata</h3> <p>To monitor Vertica, Netdata leverages an openmetrics (Prometheus) exporter, specifically the <a href="https://github.com/vertica/vertica-prometheus-exporter">vertica-prometheus-exporter</a>. Netdata can ingest data from any Prometheus exporter, enabling comprehensive monitoring without the need for a Prometheus server or Grafana. This approach offers users automated dashboards, alerts, and extensive insights, facilitating seamless database performance management.</p>VMware vCenter Server Monitoringhttps://www.netdata.cloud/monitoring-101/vsphere-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/vsphere-monitoring/<h2 id="vmware-vcenter-server-monitoring">VMware vCenter Server Monitoring</h2> <h3 id="what-is-vmware-vcenter-server">What Is VMware vCenter Server?</h3> <p>VMware vCenter Server is a centralized platform for managing VMware vSphere environments. It allows administrators to automate and deliver a virtual infrastructure with confidence. vCenter Server provides essential vSphere and ESXi host management capabilities for IT teams.</p> <h3 id="monitoring-vmware-vcenter-server-with-netdata">Monitoring VMware vCenter Server With Netdata</h3> <p>Netdata offers a real-time monitoring solution for VMware vCenter Server with its robust <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/vsphere/?utm_source=website&amp;utm_content=monitoring101">vSphere collector</a>. This powerful tool allows you to track host and virtual machine (VM) performance statistics, providing valuable insights into your virtual environments.</p>VSCode Monitoringhttps://www.netdata.cloud/monitoring-101/vscode-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/vscode-monitoring/<h2 id="vscode-monitoring">VSCode Monitoring</h2> <h3 id="what-is-vscode">What Is VSCode?</h3> <p>Visual Studio Code (VSCode) is a highly popular source-code editor developed by Microsoft. It includes key features like support for debugging, syntax highlighting, intelligent code completion, snippets, and code refactoring. It&rsquo;s vital for developers who require a streamlined and extensible environment to accelerate productivity and efficiency in coding tasks.</p> <h3 id="monitoring-vscode-with-netdata">Monitoring VSCode With Netdata</h3> <p>Monitoring VSCode is crucial for maintaining optimal performance and ensuring a seamless coding experience. Netdata facilitates this by utilizing an openmetrics (Prometheus) exporter to collect comprehensive metrics. Whether you are a developer or an IT professional, the flexibility of Netdata allows you to ingest data from any Prometheus exporter. Thus, you can access automated dashboards, real-time alerts, and comprehensive visualizations without needing to set up a standalone Prometheus server or Grafana. This streamlined monitoring solution increases efficiency and helps detect issues promptly in your development environment.</p>vSphere 'Virtual machine disks consolidation is needed': clearing the warning without stunning the VMhttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-snapshot-consolidation-needed/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-snapshot-consolidation-needed/<p>The &ldquo;Virtual machine disks consolidation is needed&rdquo; warning means the VMkernel left delta VMDKs on the datastore after a snapshot delete that did not fully commit. The VM is still running, but its writes are going through delta files that were never meant to persist.</p> <p>The warning is set by <code>VirtualMachine.runtime.consolidationNeeded</code> in the vCenter inventory. It is distinct from the Snapshot Manager view: a VM can have this flag set while showing zero snapshots in the manager, because the flag tracks orphaned files on the datastore, not the snapshot tree.</p>vSphere active vs consumed vs granted memory: why the percentage lieshttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-active-vs-consumed-memory/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-active-vs-consumed-memory/<p>The &ldquo;Memory Usage&rdquo; percentage on a vSphere host summary is one of the most misread signals in infrastructure monitoring. An 85% number that pages you at 3 a.m. may represent a healthy host with no reclamation at all. The same number on a different host may mean VMs are being actively swapped to disk. The percentage alone tells you nothing useful about either state.</p> <p>The host summary percentage is computed from consumed memory divided by physical RAM. Operators interpret this as demand, but consumed is not demand. It is a high water mark that includes idle pages. To reason about memory pressure you must read consumed alongside active, granted, and the reclamation signals (balloon, compression, swap). This article explains what each metric actually measures, why consumed greater than active is normal and expected, and how to tell a healthy 85% from a crisis 85%.</p>vSphere CPU co-stop high (%CSTP): the SMP vCPU co-scheduling penaltyhttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-cpu-co-stop-high/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-cpu-co-stop-high/<p><code>%CSTP</code> in esxtop is the time a vCPU in a multi-vCPU VM sits halted because the ESXi scheduler is waiting to co-schedule the VM&rsquo;s other vCPUs. In a healthy environment it is essentially zero. Sustained above a few percent on modern ESXi means a sizing or topology problem, not a performance problem you can tune away.</p> <p>The classic shape: you give a database 16 vCPUs and it gets slower. The guest OS reports low CPU utilization because the vCPUs are not doing work. They are parked in COSTOP waiting for their siblings. From inside the VM this is invisible. The application runs slowly while the OS reports idle capacity.</p>vSphere CPU limit hit (%MLMTD): the forgotten MHz cap that silently throttles a VMhttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-cpu-limit-maxlimited/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-cpu-limit-maxlimited/<p>A VM is slow. The application team reports degraded throughput. You check the usual suspects: guest CPU utilization is high, but that is expected for a busy workload. Host CPU utilization is moderate, nowhere near saturated. %RDY, the standard vSphere CPU contention signal, is moderate. Everything looks healthy from the hypervisor&rsquo;s perspective, yet the VM is underperforming.</p> <p>The missing signal is %MLMTD, the CPU max-limited counter. A CPU limit is an administrative MHz ceiling that silently throttles the VM. The guest OS cannot see it. The host has spare capacity. The scheduler is not contended. The VM hit a cap that someone configured and forgot about.</p>vSphere CPU ready time high (%RDY): VMs starved while the guest looks idlehttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-cpu-ready-time-high/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-cpu-ready-time-high/<p>A database VM takes twice as long to run its nightly batch. Application latency pings fire. You SSH into the guest, run <code>top</code>, and CPU utilization sits at 25%. Memory is fine. Disk I/O looks normal. Nothing inside the VM explains the slowdown.</p> <p>This is the classic signature of CPU ready time in vSphere. The guest OS has no visibility into hypervisor scheduling decisions. When the ESXi CPU scheduler cannot find a free physical CPU for a runnable vCPU, the vCPU waits in the READY state. The guest never learns it was descheduled, so from inside the VM everything looks idle while the hypervisor sees a starved VM.</p>vSphere datastore full: 'No space left on device', paused VMs, and power-on failureshttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-datastore-full/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-datastore-full/<p>A vSphere datastore hitting 100% is a cliff-edge failure. Below 100%, VM performance is unaffected. At 100%, every VM that needs to write to the datastore stops: running VMs pause with the &ldquo;There is no more space for virtual disk&rdquo; dialog, thin-provisioned VMDKs cannot extend, snapshot deltas cannot grow, and power-on operations fail because the per-VM <code>.vswp</code> swap file cannot be created.</p> <p>The vmkernel log records the kernel&rsquo;s view with <code>No space left on device</code>. The most common root cause is unattended snapshot growth: a delta VMDK consumes the same datastore as the base disk and grows with every guest write. A VM with a 200 GB base disk and an active snapshot can grow its delta to 200 GB.</p>vSphere datastore latency high: reading GAVG, DAVG, and KAVGhttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-datastore-latency-high/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-datastore-latency-high/<p>High datastore latency is the single most common cause of &ldquo;everything is slow&rdquo; in vSphere. Applications time out, guest iowait climbs, and in severe cases VMs lose heartbeats. Storage I/O traverses guest OS, virtual SCSI adapter, VMkernel SCSI stack, storage driver, fabric, and array. A single &ldquo;latency is high&rdquo; reading does not tell you where the time is going.</p> <p>Three counters slice that path into layers: GAVG is what the guest sees, DAVG is what the array reports, KAVG is what the VMkernel adds in between. The relationship among the three is the diagnostic.</p>vSphere dropped packets (%DRPRX/%DRPTX): ring buffers, CPU, and uplink backpressurehttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-dropped-packets/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-dropped-packets/<p>%DRPRX and %DRPTX in esxtop are usually the first sign a VM is losing packets inside the host. They should be zero at steady state. When they are not, the guest retransmits, latency climbs, and for latency-sensitive workloads (IP-based storage, databases, replicated queues) the impact can be severe well before the drop rate looks alarming.</p> <p>The distinction that matters: %DRPRX and %DRPTX count drops at the virtual switch port, between the vSwitch and the guest OS driver. They are not physical NIC drops. The uplink vmnic can report zero drops via <code>esxcli network nic stats get</code> while %DRPRX is non-zero on the VM attached to it. Treating them as the same counter is the most common diagnostic mistake.</p>vSphere HA 'Insufficient resources to satisfy configured failover level': admission controlhttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-ha-insufficient-resources/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-ha-insufficient-resources/<p>The error &ldquo;Insufficient resources to satisfy configured failover level for vSphere HA&rdquo; is admission control refusing a VM power-on, vMotion, or reservation change because granting it would leave the cluster without enough spare capacity to honor the configured HA failover policy. Admission control is doing its job: protecting the restart guarantee after a host failure.</p> <p>The cluster may physically hold more capacity than admission control lets you commit. A cluster with 500 GHz of CPU and 2 TB of RAM may only let you deploy against roughly 70% of that, with the rest held in reserve so HA can restart protected VMs after a host failure. Operators who bought hardware expecting to use all of it hit this wall during provisioning and reach for the disable switch.</p>vSphere host swapping (SWCUR/SWW/s): hypervisor swap and the memory death spiralhttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-host-swapping/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-host-swapping/<p>When <code>SWR/s</code> is sustained above zero on an ESXi host, the VMkernel is actively reading VM memory pages back from <code>.vswp</code> files on the datastore. That is not a warning state. It is an active performance emergency. Every swapped-in page costs roughly 100x DRAM latency, and the swap I/O itself competes with VM disk I/O on the same datastore, producing a double penalty that degrades every VM on the host simultaneously.</p>vSphere memory ballooning (MCTLSZ): the host is reclaiming guest RAMhttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-memory-ballooning/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-memory-ballooning/<p>You open esxtop, switch to the memory view, and a VM&rsquo;s MCTLSZ column is no longer zero. A few hundred megabytes or several gigabytes, the VMkernel has inflated the vmmemctl balloon driver inside that guest and is forcing the guest OS to hand back memory it thought it owned. From the host&rsquo;s perspective this is gentle reclamation. From the guest&rsquo;s and the application&rsquo;s perspective, it is often the start of a silent performance decline.</p>vSphere monitoring checklist: the signals every host, VM, and vCenter needshttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-monitoring-checklist/<p>Send this to someone standing up vSphere monitoring for the first time, or rebuilding an alerting setup that pages too often and misses real incidents. It lists the signals worth collecting across the hypervisor plane (ESXi hosts and VMs) and the management plane (vCenter Server Appliance).</p> <p>vSphere does not fail like a generic Linux box. CPU contention is invisible from inside the guest. Memory goes from fine to catastrophic in minutes once host swapping starts. A datastore at 99% full looks identical to one at 5% full from inside a VM, until every VM on it halts. And vCenter can degrade for weeks before anyone notices, because DRS, HA, and the API quietly keep working until they don&rsquo;t. Generic CPU/disk/network dashboards miss most of this.</p>vSphere PSOD (purple screen of death): diagnosing an ESXi host crashhttps://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-host-psod/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/vmware-vsphere/vmware-vsphere-host-psod/<p>A purple screen of death (PSOD) is the ESXi VMkernel&rsquo;s deliberate halt. When the kernel detects an unrecoverable condition, an uncorrectable machine check, a driver panic, or a corrupted data structure, it stops the host on purpose, paints the purple diagnostic screen, and writes a core dump if a target is configured. Every VM on that host dies instantly. There is no graceful shutdown and no live migration off the host.</p>Warp10 Monitoringhttps://www.netdata.cloud/monitoring-101/warp10-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/warp10-monitoring/<h2 id="warp10-monitoring">Warp10 Monitoring</h2> <h3 id="what-is-warp10">What Is Warp10?</h3> <p>Warp10 is a robust open-source platform tailored for managing time-series data. It allows users to collect, store, and analyze massive amounts of time-stamped information. With its unique approach to time-series management, Warp10 offers unparalleled performance and efficiency, making it an ideal choice for scenarios requiring fast data collection and real-time analytics.</p> <h3 id="monitoring-warp10-with-netdata">Monitoring Warp10 With Netdata</h3> <p>To monitor Warp10 effectively, Netdata leverages an openmetrics (Prometheus) exporter approach. This setup allows seamless integration, where Netdata collects data from any Prometheus exporter. Unlike traditional solutions requiring multiple software components, Netdata provides automated dashboards, real-time alerts, and comprehensive insights without needing a full-stack setup like Prometheus server or Grafana.</p>Web server log files Monitoringhttps://www.netdata.cloud/monitoring-101/weblog-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/weblog-monitoring/<h2 id="web-server-log-files-monitoring">Web Server Log Files Monitoring</h2> <h3 id="what-is-web-server-log-files-monitoring">What Is Web Server Log Files Monitoring?</h3> <p>Monitoring web server log files is crucial for understanding the performance and health of a web server. Web logs contain detailed information about HTTP requests and responses, including metadata like client IP, request URI, response time, and status codes. Monitoring these files can help diagnose issues in real-time, optimize server performance, and improve user experience.</p> <h3 id="monitoring-web-server-log-files-with-netdata">Monitoring Web Server Log Files With Netdata</h3> <p>Netdata provides a comprehensive solution for web server log monitoring with its <a href="https://www.netdata.cloud/integrations/data-collection/web-servers-and-proxies/web-server-log-files/">web_log</a> module. This $name monitoring tool automatically detects log files from popular web servers like Nginx and Apache and parses them to provide detailed metrics. With Netdata, you can easily monitor web server logs in real time, visualize data, and receive actionable insights.</p>Web Servers Log Monitoringhttps://www.netdata.cloud/monitoring-101/webserverslog-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/webserverslog-monitoring/<h2 id="why-monitor-web-servers">Why monitor Web servers?</h2> <p>Web servers are among the most important components in modern IT infrastructures. They host the websites, web services, and web applications that we use on a daily basis. Social networking, media streaming, software as a service (SaaS), and other activities wouldn’t be possible without the use of web servers. And with the advent of cloud computing and the movement of more services online, web servers and their monitoring are only becoming more important. Given the extensive usage of Web servers, Sysadmins and SREs should monitor web servers as a key aspect for performance.</p>Webinar: Actionable Network Device Monitoring With AIhttps://www.netdata.cloud/webinars/network-device-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/webinars/network-device-monitoring/Webinar: Cloud MCP Server – AI-Powered Monitoringhttps://www.netdata.cloud/webinars/netdata-cloud-mcp-server/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/webinars/netdata-cloud-mcp-server/Webinar: Fleet Monitoring with Netdatahttps://www.netdata.cloud/webinars/fleet-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/webinars/fleet-monitoring/Webinar: Introducing Distributed Tracing in Netdatahttps://www.netdata.cloud/webinars/distributed-tracing/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/webinars/distributed-tracing/Webinar: Kubernetes Throttling? It Doesn't Have to Suck!https://www.netdata.cloud/webinars/kubernetes-cpu-throttling/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/webinars/kubernetes-cpu-throttling/Webinar: Live Database & Network Diagnosticshttps://www.netdata.cloud/webinars/live-functions-database-network-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/webinars/live-functions-database-network-monitoring/Webinar: Maximize Uptime With Powerful Monitoringhttps://www.netdata.cloud/webinars/maximize-uptime-monitoring-solutions/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/webinars/maximize-uptime-monitoring-solutions/Webinar: Netdata AI Now Talks to Your Other Tools to Find Root Cause Fasterhttps://www.netdata.cloud/webinars/netdata-ai-mcp-client-root-cause/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/webinars/netdata-ai-mcp-client-root-cause/Webinar: Network Topology Maps and NetFlow Analysishttps://www.netdata.cloud/webinars/network-topology-maps-netflow/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/webinars/network-topology-maps-netflow/Webinar: OpenTelemetry Monitoring with Netdatahttps://www.netdata.cloud/webinars/opentelemetry-monitoring-with-netdata/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/webinars/opentelemetry-monitoring-with-netdata/Webinar: Real-Time Windows Server Monitoringhttps://www.netdata.cloud/webinars/windows-server-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/webinars/windows-server-monitoring/Webinar: The Runbook is Dead, the Agent is Alivehttps://www.netdata.cloud/webinars/runbook-is-dead-agent-is-alive/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/webinars/runbook-is-dead-agent-is-alive/Whois domain expiry Monitoringhttps://www.netdata.cloud/monitoring-101/whois-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/whois-monitoring/<h2 id="what-is-whois-domain-expiry">What is Whois domain expiry?</h2> <p>WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block or an autonomous system, but is also used for a wider range of other information. The protocol stores and delivers database content in a human-readable format.</p> <p>Among other things WHOIS can be used to query for domain expiry.</p>Windows Monitoringhttps://www.netdata.cloud/monitoring-101/windows-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/windows-monitoring/<h2 id="note-learn-more-about-netdata"><em><strong>Note: Learn more about Netdata&rsquo;s <a href="https://www.netdata.cloud/solutions/technologies/windows-monitoring/">Native Windows Agent here</a>.</strong></em></h2> <h2 id="effective-windows-server-monitoring">Effective Windows Server Monitoring</h2> <p>If you are a Windows System Administrator or developer you know how important it is to monitor your Windows Servers and make sure they&rsquo;re up and running, smoothly.</p> <p>And you also know that sometimes things go south and your servers go kaput leaving you in the dark as to what really went wrong.</p> <ul> <li>Was it that rogue process that ate up all the CPU cycles?</li> <li>Did your server hit a memory bottleneck and start swapping like mad?</li> <li>Or maybe there was a disk error or a network glitch that you missed?</li> </ul> <p>Effective Windows server monitoring requires the following:</p>WireGuard Monitoringhttps://www.netdata.cloud/monitoring-101/wireguard-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/wireguard-monitoring/<h2 id="wireguard-monitoring">WireGuard Monitoring</h2> <h3 id="what-is-wireguard">What Is WireGuard?</h3> <p>WireGuard is a high-performance VPN technology designed for ease of use and simple configuration while ensuring secure communications. Unlike traditional VPNs, WireGuard operates at the network layer and utilizes state-of-the-art cryptography. This makes it stand out as a modern and efficient solution for secure network connectivity.</p> <h3 id="monitoring-wireguard-with-netdata">Monitoring WireGuard With Netdata</h3> <p>Monitoring WireGuard with Netdata provides deep insights into the VPN device and peer traffic. Netdata&rsquo;s comprehensive monitoring dashboard displays real-time performance metrics that are vital for maintaining optimal system and network operations. To monitor WireGuard effectively, <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/wireguard/">Netdata&rsquo;s WireGuard integration</a> is an indispensable tool that automatically detects instances to ensure seamless data collection.</p>X.509 Certificate Monitoringhttps://www.netdata.cloud/monitoring-101/x509check-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/x509check-monitoring/<h2 id="x509-certificate-monitoring">X.509 Certificate Monitoring</h2> <h3 id="what-is-an-x509-certificate">What Is an X.509 Certificate?</h3> <p>X.509 certificates are critical to internet security, setting the foundation for a secure online experience. These certificates verify identities through digital signatures, establishing secure communication channels via protocols like SSL/TLS.</p> <h3 id="monitoring-x509-certificates-with-netdata">Monitoring X.509 Certificates with Netdata</h3> <p>With Netdata, monitoring X.509 certificates becomes an intuitive and streamlined process. Netdata&rsquo;s <a href="https://learn.netdata.cloud/docs/agent/collectors/go.d.plugin/modules/x509check/">X.509 certificate monitoring tool</a> stands out by providing real-time insights into your certificates’ expiration times and revocation statuses.</p>X.509 certificates Monitoringhttps://www.netdata.cloud/monitoring-101/x509-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/x509-monitoring/<h2 id="what-are-x509-certificates">What are X.509 certificates?</h2> <p>X.509 is an International Telecommunication Union (ITU) standard defining the format of public key certificates. X.509 certificates are used in many Internet protocols, including TLS/SSL, which is the basis for HTTPS, the secure protocol for browsing the web. They are also used in offline applications, like electronic signatures.</p> <h2 id="monitoring-x509-certificates-with-netdata">Monitoring X.509 certificates with Netdata</h2> <p>The prerequisites for monitoring x509certificates with Netdata are to have x509certificates and <a href="https://learn.netdata.cloud/docs/cloud/get-started/">Netdata installed</a> on your system.</p>Xiaomi Mi Flora Monitoringhttps://www.netdata.cloud/monitoring-101/xiaomi_mi_flora-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/xiaomi_mi_flora-monitoring/<h2 id="xiaomi-mi-flora-monitoring">Xiaomi Mi Flora Monitoring</h2> <h3 id="what-is-xiaomi-mi-flora">What Is Xiaomi Mi Flora?</h3> <p>Xiaomi Mi Flora is an IoT device designed for plant care, providing insights into essential metrics such as soil moisture, temperature, and sunlight exposure. Ideal for horticulturists and plant enthusiasts, this nifty gadget ensures optimal plant growth and health by relaying real-time data to your chosen monitoring platform.</p> <h3 id="monitoring-xiaomi-mi-flora-with-netdata">Monitoring Xiaomi Mi Flora With Netdata</h3> <p>Netdata offers a seamless solution to monitor Xiaomi Mi Flora using an openmetrics (Prometheus) exporter. By leveraging an exporter specifically designed for Mi Flora, such as the <a href="https://github.com/xperimental/flowercare-exporter">MiFlora/Flower Care Exporter</a>, Netdata ingests data effortlessly, eliminating the need for dedicated Prometheus servers or complex Grafana setups. With Netdata, users gain access to automated dashboards and instant alerts, optimizing their experience with Xiaomi Mi Flora monitoring tools.</p>YOURLS URL Shortener Monitoringhttps://www.netdata.cloud/monitoring-101/yourls-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/yourls-monitoring/<h2 id="yourls-url-shortener-monitoring">YOURLS URL Shortener Monitoring</h2> <h3 id="what-is-yourls-url-shortener">What Is YOURLS URL Shortener?</h3> <p>YOURLS, or Your Own URL Shortener, is a self-hosted URL shortening service built on open-source principles. It provides the flexibility to create and manage custom short URLs, perfect for anyone wanting full control over their URL shortening service without relying on third-party platforms.</p> <h3 id="monitoring-yourls-with-netdata">Monitoring YOURLS With Netdata</h3> <p>Monitoring YOURLS is crucial to ensure its uptime, reliability, and performance. Netdata makes it easy to monitor YOURLS by utilizing an OpenMetrics (Prometheus) exporter, specifically the <a href="https://github.com/just1not2/prometheus-exporter-yourls">YOURLS exporter</a>. With Netdata, you can ingest data from any Prometheus exporter, enabling automated dashboards and real-time alerts without the need for a standalone Prometheus server or Grafana setup. This seamless integration ensures you have the insights you need to keep YOURLS running optimally.</p>YugabyteDB Monitoringhttps://www.netdata.cloud/monitoring-101/yugabytedb-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/yugabytedb-monitoring/<h2 id="yugabytedb-monitoring">YugabyteDB Monitoring</h2> <h3 id="what-is-yugabytedb">What Is YugabyteDB?</h3> <p><a href="https://www.yugabyte.com/yugabytedb">YugabyteDB</a> is a high-performance, distributed database built for cloud-native applications. It offers the scalability and resilience of NoSQL databases while maintaining the ACID transactions and functionality of traditional relational databases. As a result, it&rsquo;s a popular choice for organizations needing to scale rapidly without compromising on data integrity.</p> <h3 id="monitoring-yugabytedb-with-netdata">Monitoring YugabyteDB With Netdata</h3> <p>Netdata is a comprehensive real-time monitoring solution ideal for monitoring YugabyteDB. With its ability to provide a plethora of performance metrics out-of-the-box, you can seamlessly track the health and performance of your YugabyteDB instances. Whether you need to dig deep into database operations or monitor general server health, Netdata has you covered.</p>Zerto Monitoringhttps://www.netdata.cloud/monitoring-101/zerto-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/zerto-monitoring/<h2 id="zerto-monitoring">Zerto Monitoring</h2> <h3 id="what-is-zerto">What Is Zerto?</h3> <p>Zerto is a disaster recovery and data protection platform designed to orchestrate backup and recovery processes across complex IT environments. It provides seamless integration for data backup, recovery, and efficient management of your IT infrastructure. By ensuring data integrity and continuity, businesses can minimize downtime and ensure smooth operations even in the face of unexpected disruptions.</p> <h3 id="monitoring-zerto-with-netdata">Monitoring Zerto With Netdata</h3> <p>When it comes to monitor Zerto performance and reliability, Netdata provides an unparalleled advantage with its openmetrics (Prometheus) exporter capabilities. By leveraging the <a href="https://github.com/claranet/zerto-exporter">Zerto Exporter</a>, Netdata enables the seamless ingestion of data from any Prometheus exporter. Users benefit from automated dashboards that offer real-time insights, alerts, and more—all without the need for a Prometheus server or Grafana.</p>ZFS Pools Monitoringhttps://www.netdata.cloud/monitoring-101/zfspool-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/zfspool-monitoring/<h2 id="zfs-pools-monitoring">ZFS Pools Monitoring</h2> <h3 id="what-is-zfs-pools">What Is ZFS Pools?</h3> <p>ZFS Pools are a high-performance, robust storage platform that combines a file system and logical volume manager designed to simplify data management and scaling. They are central to the ZFS ecosystem, enabling advanced data integrity, scalability, and reliability features.</p> <h3 id="monitoring-zfs-pools-with-netdata">Monitoring ZFS Pools With Netdata</h3> <p>To monitor ZFS Pools effectively, using a comprehensive tool like Netdata is crucial. Netdata provides real-time insights into the health and performance of ZFS Pools, including key metrics such as space utilization, fragmentation, and health states. By deploying <a href="https://www.netdata.cloud/integrations/data-collection/storage-and-filesystems/zfs-pools/">Netdata&rsquo;s ZFS Pools monitoring tool</a>, you gain access to detailed visualizations and alerts to help you proactively manage your ZFS systems.</p>ZooKeeper "Cannot open channel to N at election address": the blocked election porthttps://www.netdata.cloud/guides/zookeeper/zookeeper-cannot-open-channel-at-election-address/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-cannot-open-channel-at-election-address/<p>The log line is <code>Cannot open channel to &lt;id&gt; at election address /host:3888</code>. It is emitted by <code>QuorumCnxManager.initiateConnection()</code> when <code>Socket.connect()</code> to a peer&rsquo;s leader election port fails with <code>ConnectException</code> (refused) or <code>SocketTimeoutException</code> (timed out). The error is harmless during steady state and fatal during an election.</p> <p>ZooKeeper ensembles use two inter-server TCP ports. Port 2888 (the quorum port) carries the ZAB proposal/ACK/commit stream between followers and the active leader. Port 3888 (the leader election port) is touched only when <code>FastLeaderElection</code> needs pairwise TCP channels to every voting peer. If 2888 is reachable but 3888 is not, the ensemble runs fine until the leader is lost, at which point no new leader can be elected.</p>ZooKeeper "Client session timed out, have not heard from server": the heartbeat misshttps://www.netdata.cloud/guides/zookeeper/zookeeper-client-session-timed-out/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-client-session-timed-out/<p>A <code>Client session timed out, have not heard from server in &lt;ms&gt;ms for session id 0x..., closing socket connection and attempting reconnect</code> log line is the client&rsquo;s <code>SendThread</code> reporting that no PING response arrived inside its heartbeat window. This is a client-side symptom of a heartbeat miss. It is not the server expiring the session, and it is not yet <code>SessionExpired</code>. The client closes its socket and tries another ensemble member.</p>ZooKeeper "Detected pause in JVM or host machine (eg GC)": the pause-monitor warninghttps://www.netdata.cloud/guides/zookeeper/zookeeper-detected-pause-in-jvm/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-detected-pause-in-jvm/<p>The log line looks like this:</p> <pre><code>Detected pause in JVM or host machine (eg GC): pause of approximately 5234 ms, total pause: info level: 0, warn level: 0 </code></pre> <p>ZooKeeper&rsquo;s JvmPauseMonitor emits that line when the process froze longer than its configured threshold. The monitor thread sleeps for a fixed interval, wakes, and measures how long the sleep actually took. Anything beyond the expected sleep plus the warn threshold gets logged. If the JVM was not in a visible GC at that moment, the line ends with &ldquo;No GCs detected&rdquo;, which is the operator&rsquo;s cue that something else on the host stole CPU.</p>ZooKeeper "fsync-ing the write ahead log took too long": the disk warning behind most write stallshttps://www.netdata.cloud/guides/zookeeper/zookeeper-fsync-warning-adversely-affect-latency/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-fsync-warning-adversely-affect-latency/<p>The warning:</p> <pre tabindex="0"><code>fsync-ing the write ahead log in SyncThread:0 took 1234ms which will adversely effect operation latency... </code></pre><p>fires when fsync on the transaction log exceeds <code>fsync.warningthresholdms</code> (default 1000ms). The wording is deliberate: every write in ZooKeeper blocks on a quorum of fsyncs. If fsync takes a second, every write takes a second. If fsync takes 10 seconds, you are one missed heartbeat away from a leader election.</p> <p>This is the canary for the failure pattern the playbook calls &ldquo;Disk Sync Deadlock&rdquo;: the single most common cause of ZooKeeper outages, more than GC, more than network. When you see this warning, the bottleneck is almost never ZooKeeper itself. It is the disk under <code>dataLogDir</code>. The fix is usually storage, not config.</p>ZooKeeper "Packet len is out of range": jute.maxbuffer and oversized znodeshttps://www.netdata.cloud/guides/zookeeper/zookeeper-packet-len-out-of-range/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-packet-len-out-of-range/<p><code>Packet len &lt;N&gt; is out of range!</code> looks like a network framing problem. It is not. The ZooKeeper client is telling you the server&rsquo;s serialized response exceeded the client&rsquo;s maximum deserialization buffer, and the client closed the connection rather than read a truncated packet.</p> <p>On the server side, the same condition produces a terser log line: <code>Len error</code>. That appears when a client attempts a write whose payload exceeds the server&rsquo;s configured buffer limit. Both sides are governed by one Java system property: <code>jute.maxbuffer</code>, which defaults to <code>0xfffff</code> (1048575 bytes, just under 1 MB).</p>ZooKeeper "Too many connections from /IP - max is 60": maxClientCnxns rejecting clientshttps://www.netdata.cloud/guides/zookeeper/zookeeper-too-many-connections-max-is/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-too-many-connections-max-is/<p><code>WARN ... Error accepting new connection: Too many connections from /1.2.3.4 - max is 60</code> is ZooKeeper&rsquo;s <code>maxClientCnxns</code> limiter refusing a new TCP connection from a specific source IP. By the time it appears in the server log, the client has already been denied.</p> <p>The first trap: <code>maxClientCnxns</code> is enforced per source IP, not as a total. A single ZooKeeper node can hold thousands of healthy sessions while still refusing every new connection from one IP. <code>zk_num_alive_connections</code>, the metric most teams watch, is a total. It can look completely normal while clients behind a shared host IP are being silently turned away.</p>ZooKeeper "Unable to load database on disk": corrupt snapshot on startuphttps://www.netdata.cloud/guides/zookeeper/zookeeper-unable-to-load-database-on-disk/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-unable-to-load-database-on-disk/<p>The startup error <code>Unable to load database on disk</code> (logged by <code>QuorumPeer</code> when the database load fails) means ZooKeeper cannot reconstruct its in-memory data tree from the on-disk snapshot and transaction log. The node refuses to join the ensemble and exits before serving traffic. You typically see this only on the next restart after the corruption happened, often days later.</p> <p>The failure is nasty because the running process looks fine until it does not. The corruption was already on disk; the restart made it impossible to ignore. A node that was serving requests an hour ago can refuse to come back after an unclean shutdown, an OOMKill, or a full <code>dataDir</code> disk.</p>ZooKeeper "X is not executed because it is not in the whitelist": four-letter-word commands blockedhttps://www.netdata.cloud/guides/zookeeper/zookeeper-command-not-in-whitelist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-command-not-in-whitelist/<p>The error string is exact. When you run <code>echo mntr | nc localhost 2181</code> against a ZooKeeper 3.5.3+ server that has not been configured for it, the server replies:</p> <pre tabindex="0"><code>mntr is not executed because it is not in the whitelist. </code></pre><p>Same shape for <code>ruok</code>, <code>isro</code>, <code>stat</code>, <code>conf</code>, <code>envi</code>, <code>cons</code>, <code>wchs</code>, and the rest of the four-letter-word (4lw) command set. Only <code>srvr</code> works out of the box, because the bundled <code>zkServer.sh</code> status check depends on it.</p>ZooKeeper autopurge not configured: snapshots and logs filling the disk over monthshttps://www.netdata.cloud/guides/zookeeper/zookeeper-autopurge-not-configured/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-autopurge-not-configured/<p><code>autopurge.purgeInterval</code> defaults to <code>0</code>, meaning snapshots and transaction logs accumulate forever. On a quiet ensemble the growth is slow enough that nobody notices for months, then the <code>dataLogDir</code> partition hits 100%, ZooKeeper cannot fsync the next write, and the process dies. The leader throws an <code>IOException</code> on the transaction log and the ensemble loses a member, or quorum if more than one node fills simultaneously.</p> <p>This article covers how to confirm autopurge is the cause, clean up safely without forcing followers into expensive SNAP syncs, and set <code>autopurge.purgeInterval</code> and <code>autopurge.snapRetainCount</code> so it does not recur.</p>ZooKeeper avg_latency hides write stalls: why the headline number lieshttps://www.netdata.cloud/guides/zookeeper/zookeeper-avg-latency-hiding-write-stalls/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-avg-latency-hiding-write-stalls/<p>The dashboard says <code>zk_avg_latency</code> is 1.2 ms. Clients are timing out on writes. Both can be true. On a read-heavy ZooKeeper ensemble, the headline latency number can look healthy while the write path is stalled.</p> <p>Two properties cause this. First, <code>zk_avg_latency</code>, <code>zk_min_latency</code>, and <code>zk_max_latency</code> aggregate reads and writes into one number. Reads are served from local memory and complete in microseconds. Writes require a quorum round-trip plus a transaction log fsync before acknowledgment. When reads dominate the request mix, a severe write stall is diluted by thousands of cheap reads and disappears into the average.</p>ZooKeeper data tree digest mismatch: detecting corruption before it spreadshttps://www.netdata.cloud/guides/zookeeper/zookeeper-digest-mismatch/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-digest-mismatch/<p>When <code>zk_digest_mismatches_count</code> increments on a ZooKeeper node, the in-memory data tree on that node has diverged from the checksum ZooKeeper expects. This is a data-integrity alarm, not a performance signal. Clients reading from that node may be receiving wrong answers, and if the divergence came from a ZAB replication bug rather than local corruption, the same divergence may be propagating to other ensemble members.</p> <p>The digest feature (enabled by default since ZooKeeper 3.6.0) computes a running checksum of the entire data tree using an incremental adHash scheme. On every write, ZooKeeper updates the hash and compares it against the expected digest attached to the transaction. When the comparison fails, the counter ticks up and ZooKeeper logs a &ldquo;First digest mismatch on txn&rdquo; message. A single increment is enough to page.</p>ZooKeeper dataLogDir sharing a disk with snapshots: the #1 fsync-latency footgunhttps://www.netdata.cloud/guides/zookeeper/zookeeper-datalogdir-not-separated/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-datalogdir-not-separated/<p>You are chasing intermittent ZooKeeper write-latency spikes that appear to have no cause. Average latency is fine most of the time. Then, every few minutes, p99 update latency jumps by an order of magnitude, <code>zk_outstanding_requests</code> briefly climbs, and clients on tight timeouts see a flicker of connection churn. By the time you SSH in, the cluster looks healthy again.</p> <p>The disk is not full, <code>iostat</code> averages look reasonable, and the spikes do not line up with any obvious workload change. The transaction log and snapshot directory are both on the same volume, and that is exactly the problem.</p>ZooKeeper KeeperErrorCode = ConnectionLoss: the transient disconnect every client hitshttps://www.netdata.cloud/guides/zookeeper/zookeeper-connectionloss/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-connectionloss/<p><code>KeeperErrorCode = ConnectionLoss</code> is the error every ZooKeeper client eventually logs. It means the TCP connection between the client and the server it was talking to broke before the operation&rsquo;s response arrived. It does not mean the operation failed, and it does not mean the session is gone. The outcome of the in-flight operation is unknown, and the correct response is an idempotent retry.</p> <p>The most common confusion is treating ConnectionLoss like SessionExpired. They are different things. ConnectionLoss is a transient client-side condition: the TCP link is down but the session may still be alive on the ensemble. SessionExpired is an ensemble-level verdict: the cluster has declared the session dead and deleted its ephemerals. The cluster owns the expiry decision, and the client only learns about it after it reconnects.</p>ZooKeeper KeeperErrorCode = NoAuth: ACL denials on protected znodeshttps://www.netdata.cloud/guides/zookeeper/zookeeper-noauth-error/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-noauth-error/<p><code>KeeperErrorCode = NoAuth for /path</code> appears in client logs when a ZooKeeper operation is rejected because the calling session lacks the ACL permission required for that operation on that znode. ZooKeeper does not log the denial server-side by default; to record it, enable audit logging (<code>audit.enable=true</code>, ZooKeeper 3.6+). NoAuth is not a transient connectivity issue. The request reached a server, the server evaluated the znode&rsquo;s ACL, and the session did not match.</p>ZooKeeper KeeperErrorCode = NoNode: operating on a path that doesn't existhttps://www.netdata.cloud/guides/zookeeper/zookeeper-nonode-error/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-nonode-error/<p>A client logs <code>KeeperErrorCode = NoNode for /some/path</code>. The server returned <code>Code.NONODE</code> (integer -101), which the Java client surfaces as <code>KeeperException.NoNodeException</code>. The failed operation was a <code>getData</code>, <code>getChildren</code>, <code>setData</code>, <code>delete</code>, or <code>create</code> against a znode that is not currently in the data tree.</p> <p><code>NoNode</code> is not a server fault. It is the API contract enforced correctly: ZooKeeper refuses to operate on a missing path. The operator&rsquo;s job is to find out why the path is missing. Three cases cover almost every incident: the path was never created (usually a missing parent), the path was deleted by the server (an ephemeral tied to an expired session, or a container/TTL node auto-cleaned), or a deploy changed the znode layout clients expect.</p>ZooKeeper KeeperErrorCode = Session expired: ephemeral nodes gone, clients evictedhttps://www.netdata.cloud/guides/zookeeper/zookeeper-session-expired/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-session-expired/<p>The exact error clients log is <code>KeeperErrorCode = Session expired</code>. On the ZooKeeper side you see <code>Expiring session 0x... timeout of Nms exceeded</code>. Once that line lands, the client&rsquo;s ZooKeeper handle is dead and every piece of state it owned through that session is gone: ephemeral znodes deleted, watches invalidated, ACLs no longer enforceable. The client cannot reconnect on the same handle. It must build a new ZooKeeper object, negotiate a new session, and recreate every ephemeral node it relied on.</p>ZooKeeper Monitoringhttps://www.netdata.cloud/monitoring-101/zookeeper-monitoring/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/monitoring-101/zookeeper-monitoring/<h2 id="zookeeper-monitoring">ZooKeeper Monitoring</h2> <h3 id="what-is-zookeeper">What Is ZooKeeper?</h3> <p>ZooKeeper is a high-performance coordination service for distributed applications, developed as a project of the Apache Software Foundation. It provides a reliable, centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. Whether you’re using it for service discovery or to build resilient distributed locks, understanding its operations can ensure high availability and performance of your applications.</p> <h3 id="monitoring-zookeeper-with-netdata">Monitoring ZooKeeper With Netdata</h3> <p>Monitoring ZooKeeper effectively is crucial for ensuring the health and performance of your distributed systems. The Netdata agent makes this process straightforward by automatically detecting ZooKeeper instances running on known TCP sockets such as <code>127.0.0.1:2181</code>. To get started, you&rsquo;ll need to <a href="https://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_4lw">add <code>mntr</code> to ZooKeeper&rsquo;s 4lw.commands.whitelist</a>. Once set up, Netdata provides real-time monitoring capabilities, making it the ideal ZooKeeper monitoring tool.</p>ZooKeeper monitoring checklist: the signals every production ensemble needshttps://www.netdata.cloud/guides/zookeeper/zookeeper-monitoring-checklist/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-monitoring-checklist/<p>A reference checklist for engineers running production ZooKeeper ensembles. Signals are organized into four maturity levels: survival, operational, mature, and expert. Each level adds visibility for failure modes the previous level cannot see.</p> <p>The levels are cumulative. Level 2 assumes Level 1 is covered. Skipping to Level 4 without Levels 1 through 3 leaves gaps in the signals that actually page you during incidents: disk stalls, GC cascades, and quorum loss.</p>ZooKeeper OutOfMemoryError: Java heap space - the OOM that kills the whole ensemble at oncehttps://www.netdata.cloud/guides/zookeeper/zookeeper-heap-exhaustion-oom/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-heap-exhaustion-oom/<p>You grep the ZooKeeper log and find <code>java.lang.OutOfMemoryError: Java heap space</code>. The process is gone. A minute later another node dies with the same error, then the third. The whole ensemble went down inside a single window, not as a rolling failure. That simultaneity is the signature, not a cascade.</p> <p>ZooKeeper holds the entire data tree on the JVM heap: every znode, its data, ACL references, children lists, stat structures, plus session state, watch tables, and request queues. Every ensemble member holds the same tree. Whatever fills the heap on one node fills it on all of them at roughly the same rate, so when the tree finally exceeds the heap they OOM near-simultaneously. This is a single-cause total outage.</p>ZooKeeper quorum loss: no leader elected and every write is failinghttps://www.netdata.cloud/guides/zookeeper/zookeeper-quorum-loss-no-writes/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-quorum-loss-no-writes/<p>Every write to your ZooKeeper ensemble is timing out. Clients report <code>ConnectionLoss</code> and <code>SessionExpired</code>. Downstream systems that depend on ZK for coordination, such as Kafka controller elections or HBase region assignment, are cascading into failure. On the surviving ZK nodes, <code>ruok</code> still returns <code>imok</code>. The process is alive; the ensemble is not.</p> <p>Quorum loss is ZooKeeper&rsquo;s worst-case availability scenario. When fewer than <code>floor(N/2)+1</code> voting members can communicate, no leader can be elected and every write fails. Surviving nodes sit in <code>LOOKING</code> state, unable to make progress through ZAB.</p>ZooKeeper transaction log disk full: the crash with no graceful degradationhttps://www.netdata.cloud/guides/zookeeper/zookeeper-disk-full-txnlog/Mon, 01 Jan 0001 00:00:00 +0000https://www.netdata.cloud/guides/zookeeper/zookeeper-disk-full-txnlog/<p>ZooKeeper has no graceful degradation path for a full <code>dataLogDir</code> partition. When the WAL append fails, the server throws an IOException and dies. There is no read-only fallback, no throttling, and no <code>mntr</code> warning that precedes the crash. The same applies to the snapshot directory when the next snapshot write or pre-allocation fails.</p> <p>The most common root cause is broken or disabled autopurge. With <code>autopurge.purgeInterval</code> defaulting to <code>0</code> (disabled) and <code>autopurge.snapRetainCount</code> defaulting to <code>3</code>, an ensemble that has never been explicitly configured will accumulate transaction logs and snapshots forever. Disk consumption is silent and cliff-edge. By the time <code>ruok</code> fails, the process is already gone.</p>