From 21fbff97d4c3f03df0e66505bb72c787dde31f44 Mon Sep 17 00:00:00 2001
From: salonichf5 <146118978+salonichf5@users.noreply.github.com>
Date: Thu, 28 May 2026 17:49:10 -0600
Subject: [PATCH] add information about error log json format

---
 content/ngf/how-to/data-plane-configuration.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/content/ngf/how-to/data-plane-configuration.md b/content/ngf/how-to/data-plane-configuration.md
index 74b6ac64f..6416bce74 100644
--- a/content/ngf/how-to/data-plane-configuration.md
+++ b/content/ngf/how-to/data-plane-configuration.md
@@ -272,7 +272,8 @@ To view the full list of supported log levels, see the `NginxProxy spec` in the
 
 {{< call-out "note" >}}For `debug` logging to work, NGINX needs to be built with `--with-debug` or "in debug mode". NGINX Gateway Fabric can easily
 be [run with NGINX in debug mode](#run-nginx-gateway-fabric-with-nginx-in-debug-mode) upon startup through the addition
-of a few arguments. {{< /call-out >}}
+of a few arguments. 
+JSON error log format is not supported in debug mode. {{< /call-out >}}
 
 ---
 
@@ -310,6 +311,8 @@ spec:
 EOF
 ```
 
+NGINX Gateway Fabric supports errorLog in JSON format for NGINX Plus users. When  `errorLogFormat` is set to `json` and no custom access log format is defined, the access log also defaults to JSON format.
+
 {{< call-out "note" >}} File destinations in `logging.accessLog` are not currently supported it is always set to `/dev/stdout`. {{< /call-out >}}
 
 ---