Skip to content

Commit 1f0bb88

Browse files
salonichf5sjberman
andauthored
Update site/content/how-to/monitoring/troubleshooting.md
Co-authored-by: Saylor Berman <s.berman@f5.com>
1 parent f5cb599 commit 1f0bb88

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

site/content/how-to/monitoring/troubleshooting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ kubectl logs -n nginx-gateway ngf-nginx-gateway-fabric-bb8598998-jwk2m -c nginx
134134
2024/06/13 20:04:17 [emerg] 27#27: too long parameter, probably missing terminating """ character in /etc/nginx/conf.d/http.conf:78
135135
```
136136

137-
1. NGINX access logs are files that record all requests processed by the NGINX server. These logs provide detailed information about each request, which can be useful for troubleshooting, and analyzing web traffic.
137+
1. NGINX access logs record all requests processed by the NGINX server. These logs provide detailed information about each request, which can be useful for troubleshooting and analyzing web traffic.
138138
To view the access logs, get shell access to your NGINX container using the [steps](#get-shell-access-to-nginx-container). The access logs are located in the file `/var/log/nginx/access.log` in the NGINX container.
139139
Another method to check access logs is by reviewing the container logs for _nginx_ using:
140140

0 commit comments

Comments
 (0)