netdata/netdata
The official image for monitoring systems, containers and applications with Netdata.
100M+
Netdata is a high-performance, cloud-native, and on-premises observability platform designed to monitor metrics and logs with unparalleled efficiency. It delivers a simpler, faster, and significantly easier approach to real-time, low-latency monitoring for systems, containers, and applications.
What sets Netdata apart is its cost-efficient, distributed design. Unlike traditional monitoring solutions that centralize data, Netdata distributes the code. Instead of funneling all data into a few central databases, Netdata processes data at the edge, keeping it close to the source. The smart open-source Netdata Agent acts as a distributed database, enabling the construction of complex observability pipelines with modular, Lego-like simplicity.
Netdata also incorporates A.I. insights for all monitored data, training machine learning models directly at the edge. This allows for fully automated and unsupervised anomaly detection, and with the provided APIs and UIs, users can quickly spot correlations and gain deeper insights.
This Docker image includes:
The Netdata Agent: responsible for data collection, storage (embedded database), querying, machine learning, exporting, and alerting of observability data.
The Netdata UI: The user interface that powers the dashboards, data visualization, and configuration.
While closed-source, it is free to use with Netdata Agents.
GitHub : https://github.com/netdata/netdata
Documentation: https://learn.netdata.cloud
We provide the following tags in this repository:
stable
: The stable tag will always point to the most recently published stable build.edge
: The edge tag will always point ot the most recently published nightly build. In most cases, this is updated daily at around 01:00 UTC.latest
: The latest tag will always point to the most recently published build, whether it’s a stable build or a nightly build. This is what Docker will use by default if you do not specify a tag.Additionally, for each stable release, three tags are pushed, one with the full version of the release (for example, v1.30.0
), one with just the major and minor version (for example, v1.30
), and one with just the major version (for example, v1
). The tags for the minor versions and major versions are updated whenever a release is published that would match that tag (for example, if v1.30.1
were to be published, the v1.30
tag would be updated to point to that instead of v1.30.0
).
Please see the official documentation.
docker pull netdata/netdata