troubleshoot-envoy

Diagnose Envoy proxy failures by mapping Netdata signals to failure archetypes.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/netdata/skills --skill troubleshoot-envoy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshoot-envoy
Source: https://github.com/netdata/skills/tree/main/skills/troubleshoot-envoy
Command: npx skills add https://github.com/netdata/skills --skill troubleshoot-envoy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps diagnose why an Envoy proxy is misbehaving by mapping real-time Netdata observations to specific Envoy failure archetypes and guiding remediation-oriented troubleshooting.

Core Features & Use Cases

  • Envoy failure archetype triage: Targets connection pool exhaustion cascades, memory pressure spirals, xDS control plane disconnects, retry amplification, and stats cardinality explosions.
  • Netdata-backed evidence via MCP: Queries Envoy-related Netdata chart contexts through an MCP surface to validate the current incident state.
  • Operator playbook diagnostic tree: Applies the same domain decomposition (Availability, Throughput, Latency, Errors, Saturation, Internal State, Configuration State) to structure analysis and next actions.
  • Use case: When on-call engineers receive alerts or users report elevated errors/latency/saturation, this skill helps select the right signal domain, pull the relevant time windows, and recommend remediation steps aligned to the playbook.

Quick Start

Ask an AI agent: "Troubleshoot my Envoy using Netdata via MCP and identify the most likely failure archetype, then recommend remediation based on the operator playbook."

Frequently Asked Questions about troubleshoot-envoy

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

FAQPage Schema
How do I troubleshoot Envoy proxy incidents using Netdata metrics?

You can troubleshoot Envoy proxy incidents by querying Netdata chart contexts via MCP to identify failure archetypes like connection pool exhaustion or xDS disconnects, then applying an operator diagnostic tree to recommend remediation steps.

What causes Envoy connection pool exhaustion and memory pressure spirals?

Envoy connection pool exhaustion and memory pressure spirals are specific failure archetypes identified by querying Netdata signal domains to rank anomalies and validate the current incident state against real-time metric observations.

How do I diagnose Envoy xDS control plane disconnects during an incident?

Diagnose Envoy xDS control plane disconnects by selecting the internal state and configuration state signal domains, pulling relevant metric time windows through Netdata MCP, and matching the symptoms to the operator playbook.

Can I use this Netdata MCP approach to triage Envoy retry amplification and stats cardinality explosions?

Yes, this Netdata MCP approach triages Envoy retry amplification and stats cardinality explosions by mapping real-time anomaly rankings to specific failure archetypes and providing structured remediation recommendations.

What is the best way to structure on-call triage for Envoy failures?

The best way to structure on-call triage for Envoy failures is to decompose the analysis into availability, throughput, latency, errors, saturation, and configuration state domains to select the right Netdata signals and next actions.

Why is my Envoy proxy misbehaving despite no obvious configuration errors?

Your Envoy proxy may be misbehaving due to saturation failures like retry amplification or stats cardinality explosions, which you can validate by querying Netdata signal domains to identify the underlying failure archetype.