Log Files - hilbix/netdata GitHub Wiki
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.