Diagnose uWSGI failure modes using Netdata signals via MCP queries.
npx skills add https://github.com/netdata/skills --skill troubleshoot-uwsgi
Please help me install this Agent Skill. Skill: troubleshoot-uwsgi Source: https://github.com/netdata/skills/tree/main/skills/troubleshoot-uwsgi Command: npx skills add https://github.com/netdata/skills --skill troubleshoot-uwsgi
This skill solves the problem of quickly triaging uWSGI incidents—such as worker exhaustion, harakiri storms, memory creep, stuck workers, and reload failures—using the same Netdata operator playbook logic but driven through MCP queries.
Use cases: On-call incident response for a misbehaving uWSGI service, debugging elevated errors/latency/saturation, and investigating unexpected restarts or reload-related failures after deployments.
Use the troubleshoot-uwsgi skill when you ask: "My uWSGI workers are failing—can you diagnose the root cause using Netdata and MCP and tell me what remediation to try."
High-intent search queries and answers about installing and using this skill.
To troubleshoot uWSGI worker exhaustion with Netdata metrics, query MCP for node discovery and retrieve context-scoped uwsgi.* signals to identify anomalous worker saturation during incident triage.
uWSGI harakiri storms occur when workers are forcefully killed for exceeding timeouts. Diagnose them by querying Netdata MCP for anomaly ranking across uwsgi.* contexts to pinpoint which workers are consistently timing out.
Verify a uWSGI memory creep fix by re-querying Netdata MCP to retrieve uwsgi.* metrics and comparing before and after anomaly rankings to confirm the remediation holds under load.
Yes, you can diagnose stuck uWSGI workers and reload failures through MCP queries by applying an 8-domain triage flow that maps symptoms to rule files and retrieves load-bearing uwsgi.* contexts for verification.
This uWSGI incident triage method requires Netdata metrics to be available and reachable via MCP for the specific host, enabling context-scoped metric retrieval and anomaly ranking during diagnosis.
uWSGI workers failing after a deployment often stem from reload failures or memory creep. Find the root cause by using MCP to query Netdata for anomaly ranking across uwsgi.* contexts and applying the operator playbook diagnostic tree.
netdataDiagnose Docker Engine incidents via Netdata MCP queries and operator playbook triage.
netdataTroubleshoot NVMe health by querying Netdata via MCP and mapping anomalies to playbook domains.
netdataDiagnose ProxySQL incidents by mapping symptoms to Netdata signal domains.
netdataDiagnose VMware vSphere incidents using Netdata signals via MCP.
