Access log configuration in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this nginx access log format?

Given the following nginx access log format configuration, what will be the exact log output for a request with client IP 192.168.1.10, method GET, URI /home, status 200, and response time 0.123 seconds?

Nginx

log_format custom '$remote_addr - $remote_user [$time_local] "$request" '
                '$status $body_bytes_sent "$http_referer" '
                '"$http_user_agent" $request_time';
access_log /var/log/nginx/access.log custom;

A 192.168.1.10 - - [27/Apr/2024:12:00:00 +0000] "POST /home HTTP/1.1" 200 0 "-" "Mozilla/5.0" 0.123

B 192.168.1.10 - - [27/Apr/2024:12:00:00 +0000] "GET /home HTTP/1.1" 404 0 "-" "Mozilla/5.0" 0.123

C 192.168.1.10 - - [27/Apr/2024:12:00:00 +0000] "GET /home HTTP/1.1" 200 0 "-" "Mozilla/5.0" 0.123

D 192.168.1.10 - - [27/Apr/2024:12:00:00 +0000] "GET /home HTTP/1.1" 200 512 "-" "Mozilla/5.0" 0.123

💡 Hint

Focus on the variables used in the log_format and the request details given.

The log format uses variables like $remote_addr for client IP, $request for method and URI, $status for HTTP status, and $request_time for response time. The example request is GET /home with status 200 and response time 0.123 seconds, so option C matches exactly.

❓ Configuration

intermediate

Which configuration disables access logging for a specific location?

You want to disable access logging only for requests to the /healthcheck location in nginx. Which configuration snippet achieves this?

A

location /healthcheck {
    error_log off;
}

B

location /healthcheck {
    access_log off;
}

C

location /healthcheck {
    access_log /dev/null;
}

D

location /healthcheck {
    access_log /var/log/nginx/health.log off;
}

💡 Hint

Look for the directive that explicitly disables access logging.

The directive access_log off; disables access logging for the specified location. Option B correctly uses this syntax. Option B is invalid because off cannot be used with a file path. Option B sends logs to /dev/null but does not disable logging. Option B disables error logging, not access logging.

❓ Troubleshoot

advanced

Why are no access logs generated despite configuration?

An nginx server has this configuration: access_log /var/log/nginx/access.log combined; location /api { access_log off; } However, no logs are generated at all, even for requests outside /api. What is the most likely cause?

A Nginx needs to be restarted after changing access_log directives to enable logging.

B The combined log format is invalid and prevents logging.

C The main access_log directive is overridden by the location block with access_log off, disabling logging globally.

D The /var/log/nginx/access.log file has incorrect permissions preventing writing logs.

💡 Hint

Consider file system permissions and how nginx writes logs.

If the log file cannot be written due to permission issues, no logs will appear. The location block disables logging only for /api, so other requests should still log. The combined format is standard and valid. Nginx reload or restart is needed only after config changes, but the question implies config is active.

🔀 Workflow

advanced

Order the steps to enable custom access logging in nginx

Put these steps in the correct order to enable a custom access log format and activate it in nginx.

A 4,1,3,2

B 1,4,3,2

C 1,4,2,3

D 4,3,1,2

💡 Hint

Think about editing config first, then defining format, then enabling it, then reloading.

First, edit the config file (4), then define the log_format (1), then set access_log with that format (3), finally reload nginx (2) to apply.

✅ Best Practice

expert

Which is the best practice for managing access logs in a high-traffic nginx server?

For a high-traffic nginx server, which approach is best to manage access logs efficiently and avoid performance issues?

A Use asynchronous logging with a dedicated log processor and rotate logs frequently.

B Disable access logs completely to save disk space and CPU.

C Write access logs to a single large file without rotation to simplify management.

D Log only error messages and ignore access logs to reduce overhead.

💡 Hint

Consider performance and log management best practices for busy servers.

Disabling logs (B) loses valuable data. Writing to a single large file (C) risks disk space and slowdowns. Logging only errors (D) misses access info. Using asynchronous logging with a log processor and rotating logs (A) balances performance and data retention.