From ffe8b9ec58067776ea3b9ea492bd2b80baabd5fd Mon Sep 17 00:00:00 2001 From: micah Date: Wed, 13 Nov 2024 07:16:43 -0800 Subject: [PATCH] Typo fix in logging spec, max document length environment var (#1728) --- source/logging/logging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/logging/logging.md b/source/logging/logging.md index fda1f78428..8971dbcde7 100644 --- a/source/logging/logging.md +++ b/source/logging/logging.md @@ -113,7 +113,7 @@ naively by simply truncating the output at the required length; i.e. do not atte the output is still valid JSON. Truncated extended JSON MUST have a trailing ellipsis `...` appended to indicate to the user that truncation occurred. The ellipsis MUST NOT count toward the max length. -> **Fallback Implementation method**: Environment variable `MONGOB_LOG_MAX_DOCUMENT_LENGTH`. When unspecified, any +> **Fallback Implementation method**: Environment variable `MONGODB_LOG_MAX_DOCUMENT_LENGTH`. When unspecified, any > extended JSON representation of a document which is longer than the default max length MUST be truncated to that > length. When set to an integer value, any extended JSON document longer than that value MUST be truncated to that > length. If a variable is set to an invalid value, it MUST be treated as if it were not specified at all, and the