-
Notifications
You must be signed in to change notification settings - Fork 1
Log Files
There are 3 kinds of log files:
error.logaccess.logdebug.log
Any of them can be disabled by setting it to /dev/null or none in the Configuration.
By default error.log and access.log are enabled. debug.log is only enabled if debugging/tracing is also enabled.
Log files are stored in /var/log/netdata/ by default.
The error.log is the stderr of the netdata daemon and all external plugins run by netdata.
So if any process, in the netdata process tree, writes anything to its standard error, it will appear in error.log.
For most netdata programs (including standard external plugins shipped by netdata), the following lines may appear:
| tag | description |
|---|---|
INFO |
Something important the user should know. |
ERROR |
Something that might disable a part of netdata. The log line includes errno (if it is not zero). |
FATAL |
Something prevented a program from running. The log line includes errno (if it is not zero) and the program exited. |
So, when auto-detection of data collection fail, ERROR lines are logged and the relevant modules are disabled, but the program continues to run. When a netdata program cannot run at all, a FATAL line is logged.
The access.log logs web requests. The format is:
DATE: ID: (sent/all = SENT_BYTES/ALL_BYTES bytes PERCENT_COMPRESSION%, prep/sent/total PREP_TIME/SENT_TIME/TOTAL_TIME ms): ACTION CODE URLwhere:
-
IDis the client ID. Client IDs are auto-incremented every time a client connects to netdata. -
SENT_BYTESis the number of bytes sent to the client, without the HTTP response header. -
ALL_BYTESis the number of bytes of the response, before compression. -
PERCENT_COMPRESSIONis the percentage of traffic saved due to compression. -
PREP_TIMEis the time in milliseconds needed to prepared the response. -
SENT_TIMEis the time in milliseconds needed to sent the response to the client. -
TOTAL_TIMEis the total time the request was inside netdata (from the first byte of the request to the last byte of the response). -
ACTIONcan befilecopy,options(used in CORS),data(API call).
Check the Tracing Options section.
General
- Home
- Why netdata
- Installation
- Installation with docker
- Command Line Options
- Configuration
- Log Files
- Tracing Options
Running Netdata
Special Uses
-
netdata for IoT
lower netdata resource utilization -
high performance netdata
netdata public on the internet
Notes on memory management
-
Memory deduplication
half netdata memory requirements - netdata virtual memory size
Database Replication and Mirroring
- Replication Overview
-
monitoring ephemeral nodes
Use netdata to monitor auto-scaled cloud servers. -
netdata proxies
Streaming netdata metrics between netdata servers.
Backends
archiving netdata collected metrics to a time-series database
-
netdata-backends
graphite,opentsdb,kairosdb,influxdb,elasticsearch,blueflood - netdata with prometheus
- Walk Through: netdata with prometheus and grafana
Health monitoring - Alarms
alarms and alarm notifications in netdata
- Overview
-
Reference
reference for writing alarms -
Examples
simple how-to for writing alarms -
Notifications Configuration
- health API calls
- troubleshooting alarms
Netdata Registry
Monitoring Info
-
Monitoring web servers
The spectacles of a web server log file -
monitoring ephemeral containers
Use netdata to monitor auto-scaled containers. - monitoring systemd services
-
monitoring cgroups
Use netdata to monitor containers and virtual machines. -
monitoring IPMI
Use netdata to monitor enterprise server hardware - Monitoring disks
- Monitoring Go Applications
Netdata Badges
Data Collection
- Add more charts to netdata
- Internal Plugins
- External Plugins
-
statsd
netdata is a fully featured statsd server -
Third Party Plugins
netdata plugins distributed by third parties
Binary Modules
Python Modules
- How to write new module
- apache
- beanstalk
- bind_rndc
- ceph
- couchdb
- cpuidle
- cpufreq
- dns_query_time
- dovecot
- elasticsearch
- exim
- fail2ban
- freeradius
- go_expvar
- haproxy
- hddtemp
- httpcheck
- icecast
- ipfs
- isc_dhcpd
- litespeed
- mdstat
- megacli
- memcached
- mongodb
- mysql
- nginx
- nginx_plus
- nsd
- ntpd
- ovpn_status_log
- phpfpm
- portcheck
- postfix
- postgres
- powerdns
- puppet
- rabbitmq
- redis
- rethinkdbs
- retroshare
- sensors
- spigotmc
- springboot
- squid
- smartd_log
- tomcat
- traefik
- unbound
- varnish
- w1sensor
- web_log
Node.js Modules
BASH Modules
Active BASH Modules
Obsolete BASH Modules
- apache
- cpufreq
- cpu_apps
- exim
- hddtemp
- load_average
- mem_apps
- mysql
- nginx
- phpfpm
- postfix
- sensors
- squid
- tomcat
API Documentation
Web Dashboards
-
Learn how to create dashboards with charts from one or more netdata servers!
Running behind another web server
Package Maintainers
Donations
Blog
-
December, 2016
Linux console tools, fail to report per process CPU usage properly
-
April, 2016
You should install QoS on all your servers (Linux QoS for humans)
Monitor application bandwidth with Linux QoS (Good to do it, anyway)
Monitoring SYNPROXY (Linux TCP Anti-DDoS)
-
March, 2016
Article: Introducing netdata (the design principles of netdata)