問題を報告するこのページは、まだ日本語ではご利用いただけません。翻訳中です。
旧バージョンのドキュメントを参照しています。 最新のドキュメントはこちらをご参照ください。
Logging Reference
Log Levels
Log levels are set in Kong’s configuration. Following are the log levels in increasing order of their severity: debug, info,
notice, warn, error and crit.
-
debug: It provides debug information about the plugin’s run loop and each individual plugin or other components. This should only be used during debugging, thedebugoption, if left on for extended periods of time, can result in excess disk space consumption. -
info/notice: Kong does not make a big difference between both these levels. Provides information about normal behavior most of which can be ignored. -
warn: To log any abnormal behavior that doesn’t result in dropped transactions but requires further investigation,warnlevel should be used. -
error: Used for logging errors that result in a request being dropped (for example getting an HTTP 500 error). The rate of such logs need to be monitored. -
crit: This level is used when Kong is working under critical conditions and not working properly thereby affecting several clients. Nginx also providesalertandemerglevels but currently Kong doesn’t make use of these levels makingcritthe highest severity log level.
notice is the default and recommended log level. However if the logs turn out to be too chatty, they can be bumped up to a higher level like warn.
