← Directory

Netdata-glibc

A deprecated containerized Netdata build with glibc for monitoring hosts and NVIDIA GPUs on Unraid, superseded by Netdata v1.43.0 and later's native GPU…

Tools & Utilities

A deprecated containerized Netdata build with glibc for monitoring hosts and NVIDIA GPUs on Unraid, superseded by Netdata v1.43.0 and later's native GPU support.

Platform availability

Available on 1 of 9 platforms

Unraid
TrueNAS (not listed)
Umbrel (not listed)
ZimaOS (not listed)
Proxmox (not listed)
Helm (not listed)
Mac (not listed)
Windows (not listed)
Linux (not listed)

Health score?

24/100 Low

Maintained: 0GitHub repository is archived
Popular: 2721 GitHub stars
Easy to install: 351 install platform, install notes, Docker image
Light to run: 701 GB minimum RAM

Availability: platform listings confirmed today, links checked 15 days ago

GitHub stars: 21
Open issues: 0
Last commit: 2024-01-14
License: GPL-3.0
Activity: stale

Checked 7 days ago - source: GitHub (D34DC3N73R/netdata-glibc)

Resources & Compatibility

Minimum requirements: 1 GB RAM. ARM (e.g. Raspberry Pi) is not supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

Install extra packages in the container If Netdata needs extra Linux tools, set the NETDATA_EXTRA_DEB_PACKAGES environment variable when you start the container, for example with lm-sensors and netcat-openbsd. This makes Netdata install those packages at startup, so features that depend on them do not fail from missing tools. source
Deprecation Deprecated since Netdata v1.43.0, which supports NVIDIA GPUs in the native netdata/netdata image; this glibc image is no longer needed for GPU monitoring. source
Replacement image Since Netdata v1.43.0, the native Debian-based netdata/netdata image supports NVIDIA GPUs, so this glibc image is no longer needed. source
Use official Netdata This image is deprecated. From Netdata v1.43.0 onward, use the official netdata/netdata image for native GPU (graphics processing unit) monitoring. source
Repository archived The source repository is archived and the image is deprecated because Netdata v1.43.0+ supports NVIDIA GPUs natively; use the official Netdata image. source

Fetched today - each note links to its source

Alternatives (12)

Beszel - A lightweight server monitoring hub with historical data, docker stats, and alerts.
Better Stack - AI-driven monitoring platform providing incident management, real-time logs, uptime, traces, error tracking, infrastructure analytics, and…
Datadog - Datadog Agent is an on-host monitoring agent that collects metrics, logs, and traces from hosts, containers, and Kubernetes clusters and se…
Grafana - Grafana allows you to query, visualize, alert on and understand your metrics no matter where they are stored.
Monitorix - Monitorix is a system monitoring tool designed to monitor as many services and system resources as possible.
Munin - Munin is a networked resource monitoring tool that can help analyze resource trends and "what just happened to kill our performance?&q…
Nagios - Nagios is an open-source monitoring system that checks hosts, network services, and IT infrastructure resources so IT administrators can id…
NetAlertX - NetAlertX is a self-hosted network presence scanner and alert framework that monitors Wi-Fi or LAN devices, detects new, disconnected, or c…
New Relic - Pinpoint and solve performance issues in your Ruby, Java, .NET, PHP and Python apps with real user, application and server monitoring.
Paessler PRTG Network Monitor - Comprehensive network monitoring includes up/downtime tracking, traffic analysis, and performance metrics using SNMP, WMI, and NetFlow prot…
SigNoz - SigNoz is a self-hostable open-source observability platform that unifies logs, metrics, traces, alerts, and dashboards using OpenTelemetry…
VictoriaMetrics - Cost-effective easy to use monitoring solution and time series database.

Checked 14 days ago - source: AlternativeTo

Common questions

How do I migrate Netdata-glibc to the native Netdata image for NVIDIA GPU monitoring?

Use netdata/netdata:stable instead of the glibc image and pass --gpus all with --cap-add SYS_PTRACE and --security-opt apparmor=unconfined. In Docker Compose, reserve the nvidia driver with count all and capabilities gpu.

Why was a separate glibc build needed for NVIDIA GPU support?

The standard Netdata container was based on Alpine/musl, while the NVIDIA container toolkit requires a glibc distribution. The glibc image added the GNU C library so GPU-enabled Netdata could run.

Does the Netdata-glibc container include nvidia-smi?

No, it does not contain nvidia-smi. It is compatible with nvidia-container-toolkit and the Unraid Nvidia Plugin.

What mounts and permissions should I preserve when running the Netdata container?

Expose port 19999 and mount /proc, /sys, /etc/os-release, /etc/passwd, and /etc/group read-only. Persist /netdata/config, /var/lib/netdata, and /var/lib/cache/netdata; add /var/run/docker.sock read-only if you monitor containers.

How can I give Netdata Docker access without mounting the host Docker socket directly?

Run a Docker socket proxy such as tecnativa/docker-socket-proxy, mount /var/run/docker.sock only into the proxy, and set DOCKER_HOST to proxy:2375 in Netdata. Set the proxy environment variable CONTAINERS=1 if you only need container information.

What changed after Netdata moved to a full glibc base image?

The NETDATA_EXTRA_APK_PACKAGES environment variable is no longer needed. The maintainer planned to update the app despite the name being redundant.

Answers sourced from forums.unraid.net, github.com

Community

[Support] D34DC3N73R - Netdata GLIBC (GPU Enabled) (forum)
Netdata autoupdate causes kernel, glibc, etc. to update? (other)
D34DC3N73R - Unraid (forum)
Netdata glibc - GPU Enabled : r/unRAID - Reddit (reddit)
Self hosting netdata : r/netdata - Reddit (reddit)
r/selfhosted on Reddit: Anyone else using netdata over other ... (reddit)

Collected 9 days ago - public community threads