You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by wk...@apache.org on 2021/11/10 18:04:39 UTC
[trafficserver] branch master updated: Add skipped log entries to
troubleshooting FAQ in docs. (#8507)
This is an automated email from the ASF dual-hosted git repository.
wkaras pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/trafficserver.git
The following commit(s) were added to refs/heads/master by this push:
new 984d8cb Add skipped log entries to troubleshooting FAQ in docs. (#8507)
984d8cb is described below
commit 984d8cb944750e12a04bb0ee3e9723bb66c95dd6
Author: Walt Karas <wk...@verizonmedia.com>
AuthorDate: Wed Nov 10 12:04:31 2021 -0600
Add skipped log entries to troubleshooting FAQ in docs. (#8507)
---
doc/appendices/faq.en.rst | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/doc/appendices/faq.en.rst b/doc/appendices/faq.en.rst
index 900bedf..1cca514 100644
--- a/doc/appendices/faq.en.rst
+++ b/doc/appendices/faq.en.rst
@@ -513,3 +513,20 @@ origin servers. If you cannot avoid such timeouts by otherwise addressing the
performance on your origin servers, you may adjust the origin connection timeout
in Traffic Server by changing :ts:cv:`proxy.config.http.connect_attempts_timeout`
in :file:`records.config` to a larger value.
+
+Log entries for some transactions are skipped
+---------------------------------------------
+
+You will see lines like this in the diags log file::
+
+ NOTE: Skipping the current log entry for ...
+
+This happens when a log entry is too big to fit in a log buffer. This is often causeed by very long
+URLs in the entry. You can truncate long URLs using the slice syntax for the URL log field in the log
+format, for example::
+
+ %<cquc[:1000]>
+
+You can also increase the value of :ts:cv:`proxy.config.log.log_buffer_size`, but this can have impacts
+on performance and memory usage. Very large values may trigger software bugs. Some production proxies
+have run successfully using 26624 as the value for this configuration variable.