nginx-request-logging

Configures Nginx web servers with custom access logging, rate limiting, and static content serving.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Zurybr/lefarma-skills --skill nginx-request-logging-zurybr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nginx-request-logging
Source: https://github.com/Zurybr/lefarma-skills/tree/main/letta/benchmarks/trajectory-only/nginx-request-logging
Command: npx skills add https://github.com/Zurybr/lefarma-skills --skill nginx-request-logging-zurybr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides clear, step-by-step guidance to configure Nginx web servers for enhanced request logging, robust rate limiting, and efficient static content serving, ensuring better performance and security.

Core Features & Use Cases

  • Custom Log Formats: Define and implement specific log formats to capture detailed request information.
  • Rate Limiting: Set up request rate limiting to protect your server from abuse and ensure stability.
  • Static Content Serving: Configure Nginx to efficiently serve static files.
  • Use Case: You need to set up a new Nginx server block to serve a static website, log requests using a custom format that includes the user agent and status code, and limit requests to 100 per minute to prevent overload.

Quick Start

Use the nginx-request-logging skill to configure a new server block on port 8080 with custom logging and rate limiting.

Frequently Asked Questions about nginx-request-logging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Nginx custom access logging to capture user agent and status code?

To set up Nginx rate limiting, use the limit_req_zone directive in the http block to define memory zones and request thresholds, then apply limit_req in your server or location block to restrict allowed request rates.

What is the best way to serve static content with Nginx and prevent overload?

The best way to serve static content with Nginx while preventing overload is to use the try_files directive for efficient file serving and implement limit_req_zone rate limiting to protect the server from abusive traffic.

Do I need to understand specific Nginx directives to configure rate limiting and logging?

Yes, you need an understanding of Nginx directives for http, server, and location blocks, specifically including log_format, limit_req_zone, and try_files, to properly configure custom logging and rate limiting for production-ready setups.

Why does my Nginx rate limiting configuration fail to handle production traffic correctly?

Nginx rate limiting fails in production often due to misconfigured limit_req_zone directives or improper placement within http, server, and location blocks, requiring verification of common configuration patterns and potential pitfalls.