Cutlery/caddy
1
0
Fork 0
mirror of https://github.com/caddyserver/caddy.git synced 2025-07-31 15:08:42 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

Clarify log performance

Matt Holt 2019-10-28 15:32:02 -06:00
parent 3d28dcbc68
commit 1d236eba5e
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
v2:-Documentation.md

@ -862,7 +862,9 @@ Configures Caddy logs. By default, all logs at INFO level and higher are written
By default, all logs accept all log entries, but you can filter by level and module/logger names. A logger's name is the same as the module's name, but a module may append to logger names for more specificity. For example, you can filter only logs emitted by HTTP handlers using the name `"http.handlers"`, because all HTTP handler module names start with that.
There is also a "sink" where all unstructured logs emitted from Go's standard library logger are written. These logs are common in dependencies that are not designed specifically for use in Caddy. Because they are unstructured and global, the sink lacks most advanced features and customizations.
There is also a "sink" where all unstructured logs emitted from Go's standard library logger are written. These logs are common in dependencies that are not designed specifically for use in Caddy. Because they are global and unstructured, the sink lacks most advanced features and customizations.
Caddy logs (except the sink) are mostly zero-allocation, so they are very high-performing in terms of memory and CPU time. Enabling sampling can further increase throughput on extremely high-load servers.
```json
{