netdata is auto-detecting everything when it starts. The default configuration supplied by netdata attempts for detect all the supported applications, running on
By default, if you want to monitor e.g. a postgres server, you only need to allow local user
netdata connect to your local postgres server (i.e. configure your postgres server). If you need to define a password for this, netdata provides plenty of configuration files for each plugin and application in
This is the list of available external netdata plugins. netdata also has dozens of internal plugins for collecting system metrics from the system (Linux, FreeBSD, MacOS).
Everything monitored by netdata is based on templates. So, all disks are the same, all network interfaces are the same, all nginx web servers are the same, all postgres servers are the same. Since each netdata can monitor many instances of each kind (ie one netdata can monitor X postgres servers, local and remote), there is little
tag that differentiates them.
So, if you know that
tag, you can easily predict all the metrics this application will have. The default tag for localhost applications is:
For prometheus backends, netdata sends all the metrics utilizing labels for differentiating hosts, application instances, etc. For graphite and opentsdb, they are integrated into the metrics names.
netdata collects 1k to 5k high resolution metrics per server (and per second, by default), but it is capable sending metrics to backends at a lower rate (to avoid congesting these servers with too much detail). and can also filter metrics sent to backends (to avoid congesting these servers with too many metrics).
I you need more information, I’ll be glad to help…