-
Notifications
You must be signed in to change notification settings - Fork 0
Log Files
There are 3 kinds of log files:
- error.log
- access.log
- debug.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 is also enabled.
The error.log is the stderr of the netdata daemon and all plugins run by netdata.
So if any process in the netdata process tree writes anything to its standard error, it will appear in the error.log.
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
Running Netdata
Alarms
Netdata Registry
Monitoring Info
Netdata Badges
Data Collection
Binary Modules
Python Modules
- How to write new module
- apache
- apache_cache
- cpufreq
- dovecot
- exim
- hddtemp
- ipfs
- memcached
- mysql
- nginx
- nginx_log
- phpfpm
- postfix
- redis
- sensors
- squid
- tomcat
Node.js Modules
BASH Modules
- General Info - charts.d
- ap.chart.sh
- apache.chart.sh
- cpufreq.chart.sh
- example.chart.sh
- mysql.chart.sh
- nginx.chart.sh
- nut.chart.sh
- opensips.chart.sh
- phpfpm.chart.sh
- postfix.chart.sh
- sensors.chart.sh
- squid.chart.sh
- tomcat.chart.sh
API Documentation
Web Dashboards
-
Learn how to create dashboards with charts from one or more netdata servers!
Running behind another web server
Advanced configurations
- netdata for IoT (configure netdata to lower its resources)
- high performance netdata (running netdata public to the internet)
Donations
Blog
-
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)