Home Explore Help
Sign In
SMusatov
/
netdata
mirror of https://github.com/netdata/netdata.git
1
0
Fork 0
Files Wiki
Tree: 811028aea2
Branches Tags
netdata
/
collectors
Costa Tsaousis 2e874e7916 replication fixes #6 (#14046) 2 years ago
..
apps.plugin 9370299c25 apps.plugin function processes: keys should not have spaces (#13980) 2 years ago
cgroups.plugin 2d5f3acf71 Do not force internal collectors to call rrdset_next. (#13926) 2 years ago
charts.d.plugin 1ab62f364e Improve intro paragraph (#13906) 2 years ago
cups.plugin cb7af25c09 RRD structures managed by dictionaries (#13646) 2 years ago
diskspace.plugin d628eecf9d Don't let slow disk plugin thread delay shutdown (#14044) 2 years ago
ebpf.plugin 870acd6112 Improve eBPF exit (#14012) 2 years ago
fping.plugin 4521b76927 Update fping plugin documentation with better details about the required version. (#13765) 2 years ago
freebsd.plugin 2d5f3acf71 Do not force internal collectors to call rrdset_next. (#13926) 2 years ago
freeipmi.plugin 69ad057b0d Update FreeIPMI and CUPS plugin documentation. (#13526) 2 years ago
idlejitter.plugin 2d5f3acf71 Do not force internal collectors to call rrdset_next. (#13926) 2 years ago
ioping.plugin 54ef002004 Remove check for config file in stock conf dir (#12327) 3 years ago
macos.plugin 2d5f3acf71 Do not force internal collectors to call rrdset_next. (#13926) 2 years ago
nfacct.plugin eb216a1f4b Workers utilization charts (#12807) 2 years ago
perf.plugin c3dfbe52a6 netdata doubles (#13217) 2 years ago
plugins.d 2e874e7916 replication fixes #6 (#14046) 2 years ago
proc.plugin 2d5f3acf71 Do not force internal collectors to call rrdset_next. (#13926) 2 years ago
python.d.plugin d15f36d73e remove python.d/nginx_plus (#13995) 2 years ago
slabinfo.plugin eb216a1f4b Workers utilization charts (#12807) 2 years ago
statsd.plugin 2d5f3acf71 Do not force internal collectors to call rrdset_next. (#13926) 2 years ago
tc.plugin 2d5f3acf71 Do not force internal collectors to call rrdset_next. (#13926) 2 years ago
timex.plugin 2d5f3acf71 Do not force internal collectors to call rrdset_next. (#13926) 2 years ago
xenstat.plugin ecc549f5b0 Fix a crash when xen libraries are misconfigured (#13535) 2 years ago
COLLECTORS.md 2d5f3acf71 Do not force internal collectors to call rrdset_next. (#13926) 2 years ago
Makefile.am 2d5f3acf71 Do not force internal collectors to call rrdset_next. (#13926) 2 years ago
README.md 3a0eccafeb Update README.md (#12868) 2 years ago
REFERENCE.md 2d5f3acf71 Do not force internal collectors to call rrdset_next. (#13926) 2 years ago
all.h 08c3d24f79 Add ZFS rate charts (#13757) 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.