skills.rest
netdata
netdataOFFICIAL
Explore all skills by this author →
WebsiteGitHub

troubleshoot-nginx

Diagnose nginx incidents by mapping symptoms to Netdata signal domains and failure archetypes.

1|Updated Apr 17, 2026
Search Tags:#performance#troubleshooting#mcp#observability#nginx#ssl-tls#netdata
One-click install
npx skills add https://github.com/netdata/skills --skill troubleshoot-nginx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: troubleshoot-nginx
Source: https://github.com/netdata/skills/tree/main/skills/troubleshoot-nginx
Command: npx skills add https://github.com/netdata/skills --skill troubleshoot-nginx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you rapidly triage common nginx incident patterns by turning ambiguous symptoms into a structured diagnosis backed by Netdata measurements queried via MCP.

Core Features & Use Cases

  • Signal-driven nginx triage: Guides an agent through Availability, Throughput, Latency, Errors, Saturation & Resource Utilization, Upstream Health, SSL/TLS, and related domains using the Netdata operator playbook’s diagnostic tree.
  • MCP-based verification: Queries worker counts, stub status availability, request rate, active connections, and processing time, then recommends targeted remediation paths.
  • Archetype-focused troubleshooting: Detects and routes toward dominant failure modes like connection exhaustion, file descriptor exhaustion, backend cascade failure, buffer spill to disk, SSL CPU saturation, and DNS resolution failures.
  • Post-fix validation loop: Re-runs the same MCP queries to confirm signals return to expected ranges, reducing the chance of “fix didn’t hold” outcomes.

Quick Start

Use troubleshoot-nginx when investigating nginx behaving abnormally (connection drops, errors, rising latency, resource saturation, or unexpected restarts) and ask the agent to query Netdata via MCP to determine the most likely failure archetype and remediation.

Frequently Asked Questions about troubleshoot-nginx

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

FAQPage Schema
How do I troubleshoot nginx connection exhaustion and backend cascade failures?▼

Troubleshooting nginx connection exhaustion involves querying Netdata via MCP to check active connections, worker counts, and upstream health. The skill maps these signals to failure archetypes like connection exhaustion or backend cascade failure to determine targeted remediation paths.

What causes SSL CPU saturation in nginx and how is it diagnosed?▼

SSL CPU saturation in nginx is diagnosed by querying Netdata MCP to correlate SSL/TLS processing metrics with CPU utilization. Mapping these signals to the SSL CPU saturation archetype confirms the root cause and validates post-fix performance normalization.

How can I check if my nginx fix actually resolved the operational incident?▼

Validating an nginx fix requires a post-fix validation loop that re-runs the same MCP queries over load-bearing chart contexts. This confirms that availability, throughput, latency, and saturation signals have returned to their expected baseline ranges.

Does nginx troubleshooting with Netdata require stub status configured?▼

Yes, diagnosing nginx failures with Netdata relies on stub status availability to query active connections and request rates via MCP. The operator playbook diagnostic tree requires these metrics to rank anomalies and route the dominant failure archetype.

Why does nginx buffer spill to disk and how do I detect it?▼

Nginx buffer spill to disk happens when proxy buffers exceed configured limits. Detecting it requires querying Netdata saturation and resource utilization signals via MCP, mapping disk I/O spikes and buffer metrics to the buffer spill-to-disk failure archetype.

Related Skills

Explore More Software Engineering Skills→
netdatanetdata
1

troubleshoot-uwsgi

Diagnose uWSGI failure modes using Netdata signals via MCP queries.

Official
Intermediate
netdatanetdata
1

troubleshoot-coredns

Diagnose CoreDNS failure archetypes using Netdata MCP health signals.

Official
Intermediate
netdatanetdata
1

troubleshoot-docker-engine

Diagnose Docker Engine incidents via Netdata MCP queries and operator playbook triage.

Official
Advanced
slantviewslantview
1

network-engineer

Diagnose network connectivity issues and configure load balancers, SSL/TLS, and CDNs.

Community
Advanced