mirror of
				https://github.com/go-gitea/gitea.git
				synced 2025-10-31 21:28:11 +09:00 
			
		
		
		
	Allow log.xxx.default to set logging settings for the default logger only (#11292)
* Allow log.xxx.default to set logging settings for the default logger only Signed-off-by: Andrew Thornton <art27@cantab.net> * Update modules/setting/log.go * as per @silverwind add some documentation Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: techknowlogick <techknowlogick@gitea.io>
This commit is contained in:
		| @@ -48,8 +48,10 @@ Calls to `log.Info`, `log.Debug`, `log.Error` etc. from the `code.gitea.io/gitea | ||||
| You can configure the outputs of this logger by setting the `MODE` | ||||
| value in the `[log]` section of the configuration. | ||||
|  | ||||
| Each output sublogger is configured in a separate `[log.sublogger]` | ||||
| section, but there are certain default values. These will not be inherited from the `[log]` section: | ||||
| Each output sublogger is configured in a separate `[log.sublogger.default]` | ||||
| which inherits from the sublogger `[log.sublogger]` section and from the  | ||||
| generic `[log]` section, but there are certain default values. These will | ||||
| not be inherited from the `[log]` section: | ||||
|  | ||||
| * `FLAGS` is `stdflags` (Equal to | ||||
| `date,time,medfile,shortfuncname,levelinitial`) | ||||
| @@ -70,6 +72,9 @@ section which you can configure the outputs of by setting the `MACARON` | ||||
| value in the `[log]` section of the configuration. `MACARON` defaults | ||||
| to `file` if unset. | ||||
|  | ||||
| Please note, the macaron logger will log at `INFO` level, setting the | ||||
| `LEVEL` of this logger to `WARN` or above will result in no macaron logs. | ||||
|  | ||||
| Each output sublogger for this logger is configured in | ||||
| `[log.sublogger.macaron]` sections. There are certain default values | ||||
| which will not be inherited from the `[log]` or relevant | ||||
| @@ -98,6 +103,9 @@ Router logs the same data as the Macaron log but has slightly different | ||||
| coloring. It logs at the `Info` level by default, but this can be | ||||
| changed if desired by setting the `ROUTER_LOG_LEVEL` value. | ||||
|  | ||||
| Please note, setting the `LEVEL` of this logger to a level above | ||||
| `ROUTER_LOG_LEVEL` will result in no router logs. | ||||
|  | ||||
| Each output sublogger for this logger is configured in | ||||
| `[log.sublogger.router]` sections. There are certain default values | ||||
| which will not be inherited from the `[log]` or relevant | ||||
| @@ -136,6 +144,9 @@ which will not be inherited from the `[log]` or relevant | ||||
| If desired the format of the Access logger can be changed by changing | ||||
| the value of the `ACCESS_LOG_TEMPLATE`. | ||||
|  | ||||
| Please note, the access logger will log at `INFO` level, setting the | ||||
| `LEVEL` of this logger to `WARN` or above will result in no access logs. | ||||
|  | ||||
| NB: You can redirect the access logger to send its events to the Gitea | ||||
| log using the value: `ACCESS = ,` | ||||
|  | ||||
|   | ||||
		Reference in New Issue
	
	Block a user