Ilya Mashchenko 7772d35db6 fix(cgroup.plugin): read k8s_cluster_name label from the correct file (#13062) 2 years ago
..
apps.plugin 1498952b69 Update apps_groups.conf (#13033) 2 years ago
cgroups.plugin 7772d35db6 fix(cgroup.plugin): read k8s_cluster_name label from the correct file (#13062) 2 years ago
charts.d.plugin 2104bf90c4 feat(charts.d/apcupds): add load usage chart (Watts) (#12965) 2 years ago
checks.plugin c7f2647a62 Docs: Removed Google Analytics tags (#12145) 3 years ago
cups.plugin 7784a16cc7 Dictionary with JudyHS and double linked list (#13032) 2 years ago
diskspace.plugin 7784a16cc7 Dictionary with JudyHS and double linked list (#13032) 2 years ago
ebpf.plugin a16fbcef16 Fix disabled apps (ebpf.plugin) (#13044) 2 years ago
fping.plugin 9e85e48799 chore(fping.plugin): bump default fping version to 5.1 (#12930) 2 years ago
freebsd.plugin 8720c4ceb3 Fix compilation warnings in FreeBSD (#12887) 2 years ago
freeipmi.plugin eb216a1f4b Workers utilization charts (#12807) 2 years ago
idlejitter.plugin eb216a1f4b Workers utilization charts (#12807) 2 years ago
ioping.plugin 54ef002004 Remove check for config file in stock conf dir (#12327) 3 years ago
macos.plugin eb216a1f4b Workers utilization charts (#12807) 2 years ago
nfacct.plugin eb216a1f4b Workers utilization charts (#12807) 2 years ago
perf.plugin eb216a1f4b Workers utilization charts (#12807) 2 years ago
plugins.d 77b30d25d8 Optimize the dimensions option store to the metadata database (#12952) 2 years ago
proc.plugin 7784a16cc7 Dictionary with JudyHS and double linked list (#13032) 2 years ago
python.d.plugin 044d4c9d91 add note about anomaly advisor (#13042) 2 years ago
slabinfo.plugin eb216a1f4b Workers utilization charts (#12807) 2 years ago
statsd.plugin 81832edce2 coverity fixes about statsd; removal of strsame (#13049) 2 years ago
tc.plugin eb216a1f4b Workers utilization charts (#12807) 2 years ago
timex.plugin eb216a1f4b Workers utilization charts (#12807) 2 years ago
xenstat.plugin eb216a1f4b Workers utilization charts (#12807) 2 years ago
COLLECTORS.md dd313048f6 docs: fix unresolved file references (#12872) 2 years ago
Makefile.am 22863c42b9 Remove node.d.plugin and relevant files (#12769) 2 years ago
README.md 3a0eccafeb Update README.md (#12868) 2 years ago
REFERENCE.md 0fa55c7dce feat: move dirs, logs, and env vars config options to separate sections (#12935) 2 years ago
all.h eb216a1f4b Workers utilization charts (#12807) 2 years ago

README.md

Collecting metrics

Netdata can collect metrics from hundreds of different sources, be they internal data created by the system itself, or external data created by services or applications. To see all of the sources Netdata collects from, view our list of supported collectors.

There are two essential points to understand about how collecting metrics works in Netdata:

  • All collectors are installed by default with every installation of Netdata. You do not need to install collectors manually to collect metrics from new sources.
  • Upon startup, Netdata will auto-detect any application or service that has a collector, as long as both the collector and the app/service are configured correctly.

Most users will want to enable a new Netdata collector for their app/service. For those details, see our collectors' configuration reference.

Take your next steps with collectors

Supported collectors list

Collectors configuration reference

Guides

Monitor Nginx or Apache web server log files with Netdata

Monitor CockroachDB metrics with Netdata

Monitor Unbound DNS servers with Netdata

Monitor a Hadoop cluster with Netdata

Related features

Dashboards: Visualize your newly-collect metrics in real-time using Netdata's built-in dashboard.

Exporting: Extend our built-in database engine, which supports long-term metrics storage, by archiving metrics to external databases like Graphite, Prometheus, MongoDB, TimescaleDB, and more. It can export metrics to multiple databases simultaneously.