Skip to content

Add skipped log entries to troubleshooting FAQ in docs. #8507

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ywkaras merged 1 commit into from
Nov 10, 2021
+17 −0
Merged

Add skipped log entries to troubleshooting FAQ in docs. #8507

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions doc/appendices/faq.en.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.