From 1d236eba5e62470ed063a58c27d763a67ddcc566 Mon Sep 17 00:00:00 2001 From: Matt Holt Date: Mon, 28 Oct 2019 15:32:02 -0600 Subject: [PATCH] Clarify log performance --- v2:-Documentation.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/v2:-Documentation.md b/v2:-Documentation.md index be4e625..8b13453 100644 --- a/v2:-Documentation.md +++ b/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 {