From 2cb7755a8b2f6b0e79c02c0a906f0e10ca595db7 Mon Sep 17 00:00:00 2001 From: Philipp Hofmann Date: Fri, 13 Dec 2024 10:56:20 +0100 Subject: [PATCH] code review --- develop-docs/sdk/expected-features/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/develop-docs/sdk/expected-features/index.mdx b/develop-docs/sdk/expected-features/index.mdx index 2e8773ed96503..6e289961777ab 100644 --- a/develop-docs/sdk/expected-features/index.mdx +++ b/develop-docs/sdk/expected-features/index.mdx @@ -84,7 +84,7 @@ Every SDK must implement a debug mode, which is disabled by default. Users can e 1. It helps users identify and fix SDK problems, such as misconfigurations or something going wrong with sending data to Sentry. 2. It can help Sentry SDK engineers investigate issues in Sentry SDKs, which can be done while developing or by asking a user to enable the debug mode and share the debug logs. -As the log output can add unnecessary overhead, we advise users to refrain from enabling this in production. When using debug mode extensively for the second use case, we recommend adding the diagnostic level because users could easily miss error or fatal log messages. +As the log output can add unnecessary overhead, we advise users to refrain from enabling the debug mode in production. Still, SDKs may log fatal error messages even when the debug mode is disabled. When using debug mode extensively for the second use case, we recommend adding the diagnostic level because users could easily miss error or fatal log messages. ### Diagnostic Level